Changing objects and managing privileges for a DB2 for Linux, UNIX, and Windows database is similar to a changing a database that is not a DB2 for Linux, UNIX, and Windows database. You use the Administration Explorer, Object List, or Data Source Explorer to create objects and to find the objects that you want to alter or drop. For new or altered objects, you use the Properties view to set or alter the attributes of the object.
However, change plans are used to manage the changes for DB2 for Linux, UNIX, and Windows databases. Each change that you define for a database is included in a change plan, which makes it possible to make more complex database changes that include changing multiple objects at one time. You generate the commands to run on the database from the change plan. The generated change commands are displayed in the Review and Deploy dialog, where you can then run the commands against the database.
From the change plan, you can also analyze the impact that your changes might have on other database objects. When possible, IBM® Data Studio generates commands to alter the impacted objects. For example, if you change the data type of a primary key, the generated commands include DDL that changes the data type of any related foreign keys.
When IBM Data Studio cannot automatically include statements for impacted objects, you can add the changes to the change plan for the impacted objects. For example, if you change the name of a table, statements are not automatically included for impacted objects, such as views, stored procedures, user-defined functions, and materialized query tables. You must explicitly change these objects.
When you make database objects changes, check the Problems view, which highlights the impacted objects that you might need to explicitly change.