Zurück
-
Titel
Disaster recovery and creation of a new Sync History database -
Beschreibung
A scenario might arise where the existing Quick Connect or Active Roles Synchronization Service Synchronization History database (also known as the Execution database) cannot be used for some reason: this may be due to data consistency issues, exceptional data bloat, etc.
It might be necessary for the stability or usability of the solution to archive the existing Synchronization History database and start fresh with a new one. This can be done without reinstalling the product and with minimal downtime. -
Lösung
- In the top right of the Quick Connect Console, click on the Gear icon.
- Click "Export Configuration" | "Browse" and save the current configuration.
- Click on the Gear icon again and then click "Configure Sync Engine...".
- Choose "Create a new configuration" | "Next"
- Specify the SQL Server and a new SQL database name.
- Check the box labeled "Store sync data in a separate database" and specify the new Synchronization database name.
- Specify an account with the permissions necessary to create databases on the target SQL server and click "Next".
- Save the new configuration profile file under a different file name and click "Finish"
- Close the Quick Connect Console, restart the Quick Connect service, and reopen the console.
- Click on the Gear icon and then click "Import Configuration..."
- Select the relevant Quick Connect version and DO NOT check the box labeled "Import sync history"
- Click "Next" | "Browse" and select the configuration file created in Step 2 above.
- Click "Next" | "Start Import" | "Finish"
- Close the Quick Connect Console, restart the Quick Connect service, and reopen the console.
- Confirm functionality by running a test Workflow.