Troubleshooting replication issues

Troubleshooting replication issues

The Case

You found out that your scheduled replication for some reason has failed. The state of your subscriber databases is unknown to you. You need to identify the updates that need to be made to your subscriber databases, and implement them in the shortest possible time.

Main goals to be achieved

• To find out the changes that need to be made.
• To implement those updates to subscriber databases.
• To keep an audit trail of the managed changes.

Our solution is

Use Cross-Database Comparator Pro or Cross-Database Studio to compare the publisher database with the subscriber database for selected tables.

1. View the results, and create a report of the differences if required.
2. Select the records that you want to update.
3. Save the generated synchronization script.
4. Backup up the subscriber database.
5. Run the synchronization script to update the subscriber database.

Advantage of our solution

• Automates the tedious procedures of identifying the differences between the databases.
• Scripts can be used on any number of subscriber databases.
• Provides an audit trail of the changes that have been made.
• Provides easier troubleshooting than from within Database Server: more feedback, faster implementation.