A migration strategy moves the Collection Server components to another SQL Server instance, thereby replacing the original Collection Server. You can use a migration strategy to respond to an immediate maintenance need. Use the following procedures and guidelines to implement a new migration strategy or modify an existing migration strategy.

Verify the configuration of the target SQL Server

When identifying the new SQL Server instance that will host the Collection Server, ensure this instance meets or exceeds the product hardware, software, and permissions, as well as these specific requirements:

  • The target instance is running the same version or higher of the SQL Server software that is currently running on the existing Collection Server computer
  • The current Collection Service account can access the target instance and has the correct permissions on the target instance

Back up the Repository databases

Use a tool such as IDERA SQL Safe to perform a full backup of the Repository databases, including transaction logs. You can back up event and archive databases separately from the SQLcompliance databases. However, for best results during a disaster recovery, fully restore all Repository databases at the same time.

SQL Compliance Manager monitor, audit and alert on SQL user activity and data changes.
IDERA | Products | Purchase | Support | Community | Resources | About Us | Legal

  • No labels