Versions Compared

Key

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

...

  1. Back up the SQL Secure repository database on the original server.
  2. Open the SQL Server Agent manager 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.

...

  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:

    Code Block
    C:\Program Files\Idera\SQLsecure\Bin\Idera.SQLsecure.Collector.exe" -TargetInstance "TARGETSERVER" -Repository "SERVER"
    Note
    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.

...

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.
Scroll pdf ignore
Excerpt

Newtabfooter
aliasIDERA
urlhttp://www.idera.com
|
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
|
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
|
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
|
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
|
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
|
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
|
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse