Applying another deployment script to the target model of a database
allows you to make the same changes to the database that were made to another
database. For example, assume that two developers each have their own development
database for an application. You want to move the changes that each developer
made to the test database for the application. If you have the deployment
scripts that the developers used to change their databases, you can apply
those deployment scripts to a model of the test database, and then eventually
deploy the consolidated changes to the test database.
Restriction: The
Apply Deployment Script action, on the Data Models tab of the Deployment Script
Editor, might not always leave the target model in a valid state. When the
base models of the two databases are different, you might have to resolve errors that DB2® Change Management Expert will flag to account for
missing objects. However, invalid models might result if there are extensive
differences, especially in the unchanged parts of the models that have dependencies
on the objects that were changed. Take care to thoroughly understand the changes
to the target model before generating your change commands. Otherwise the
commands might be invalid. When you are managing changes between databases
with different base models, you should merge the changes by using the Comparison
Editor. Always check your target model for errors before generating change
commands and deploying those changes.
To apply another deployment
script to a target model, complete the following steps: