Idera SQL Change Manager

If we expand this second section, we see that this is the single table I’ve created in my dev database. This demonstrates SQL change manager’s capability to perform a simple task. I’ll show more complex comparison processes later.

At this point, the comparison process is finished. You can now review each difference found by Idera SQL change manager and decide which differences should be included in the synchronization script. It is not mandatory that each difference between source and target be synchronized. You may include or exclude any difference in the synchronization script, giving you complete control over the synchronization process.

If you are ready to start the actual synchronization process you click on “Synchronize”->”Run synchronization”.

This will bring up the “Synchronization Scripts” dialog box. Here you may review the final script that is about to be executed. At this point you may also change the direction of the synchronization.

Once the synchronization process has successfully finished, source and target schema are in synch with each other.



No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |