Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
  • with the new SQL Server host instance name
  • .
  • 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
  3. each of
  4. the SQLsecure Collector Job and the SQLsecure Groom Job.
  5. Create a SQL script for each
  6. of these jobs
  7. job using the native tools.

On the new SQL Server,

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

    Code Block
    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.

  6. Perform a Full Install of SQL Secure from the installation kit.

  7. Select
  8. In the installation wizard, select the option to use

  9. the
  10. an existing repository

  11. when prompted in the installation wizard
  12. .

  13.  E
  14. E-mail licensing@idera.com with

  15. the name of
  16. 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.

Info
Please note that SQL Secure will automatically generate generates a 14-day trial key that allows allowing the migrated installation to function functions exactly as the previous SQLsecure installation didone.
Note
titleFor 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.