Scenario: Synchronizing test and production systems

You can synchronize multiple copies of a database by using the DB2® to avoid having to keep meticulous records of all table changes in each database.

Consider a scenario in which the manager of a DB2 application development group must track multiple development teams in an environment that consists of a copy of the production database and several duplicate databases in a test environment. While working on any release cycle, each application coding team is assigned their own test database and requests changes to individual tables for their development work.

Because each team works independently, the database tables in each database soon become quite different from one another. In addition, different stages of change integration result in additional table modifications. You might have ten different databases and table structures in your test environment.

To synchronize these changes with each other, the database administrator can use DB2 Object Comparison Tool to compare the original production schema with each test database and create a baseline from which to create the new production system.

After all of the schema changes are migrated to QA and then to production, you then use the production environment as the new master database to synchronize all of the tables in the test environment.

To synchronize the test database with the database in the production database, use DB2 Object Comparison Tool to compare the database within the test environment and the database within the production database.

Using DB2 Object Comparison Tool you can keep multiple database schemas synchronized.