Among IDERA SQL Secure's features, it allows migrating SQL Secure from one server to another.

For a successful SQL Secure migration, make sure to  

  • Move the repository to a new SQL Server host.
  • Copy the SQL Secure Collector Jobs into a script and restore them to a new SQL Server host.
  • Update the SQL Server host instance name in the collector jobs' CLI operations.
  • Install the SQL Secure components on the new SQL Server instance.

To copy SQL Secure settings to a new installation, follow the steps below

  1. Back up the SQL Secure repository database on the original server.
  2. Open the SQL Server Agent Manager on the repository server and find the SQLsecure Collector Job and the SQLsecure Groom Job.
  3. Create a SQL script for each job using the native tools.

On the new SQL Server,

  1. Restore the SQLsecure repository.
  2. Execute the collected SQL scripts to re-create the jobs.
  3. Each collection job contains a command-line operation similar to the following:

    C:\Program Files\Idera\SQLsecure\Bin\Idera.SQLsecure.Collector.exe" -TargetInstance "TARGETSERVER" -Repository "SERVER"
    Update the SERVER value to match the instance name of the new repository.
  4. Perform a Full Install of SQL Secure from the installation kit.

  5. In the installation wizard, select the option to use an existing repository.

  6. E-mail IDERA with the new SQL Server instance name that hosts the SQLsecure repository database. Then you will receive a new permanent key for the new SQLsecure installation.

SQL Secure automatically generates a 14-day trial key allowing the migrated installation functions exactly as the previous one.

For SQL Secure 2.5 UPGRADES on SQL Server 2000

This solution 'as is' addresses the requirement for migrating the existing SQLsecure installation from SQL Server 2000 to SQL Server 2005 before upgrading to SQL Secure 2.5 as referenced in the Release Notes.

IDERA | Products | Purchase | Support | Community | Resources | About Us | Legal
  • No labels