Data Design Projects

A Data Design Project is a container for storing the resources that you use to plan, analyze, archive, and change your databases. Projects are displayed in the Data Project Explorer view, and they correspond to directories in the file system.

When the first change plan is created for a database, a Data Design Project is created automatically. The name of the project is database_connection-name Change Plans, where database_connection-name is the name of the database connection. For each change plan that is created for the database, the project contains the resources, including models and scripts, that are needed to make the database changes in that change plan.

When a project is created, these subfolders are displayed within the project to hold the following resources:
Data Diagrams folder
Holds files that are for the product's internal use only.
Data Models folder
Holds models that are for the product's internal use only. Models have a file extension of .dbm.
Other Files folder
Holds the files that do not belong in either the SQL Scripts or Data Models folders.
SQL Scripts folder
Holds the types of script files that are shown in the following table:
Table 1. Types of scripts in the SQL scripts folder
Type of script File extension Description
Do scripts sql Contains the set of commands and statements that were run against the database. The file is created when you click Run and then Finish in the Review and Deploy dialog.

The file name for a do script is: change_plan_name timestamp_Change

Undo scripts sql Contains the set of commands and statements that can be used to rollback the changes that were made by deploying the change plan. The file is created when you click Run and then Finish in the Review and Deploy dialog.

The file name for an undo script is: change_plan_name timestamp_Change_Undo

Important: IBM® Data Studio relies on the project and the resources it contains to ensure that the changes to your objects are managed properly. To ensure the integrity of the product's functionality, do not rename projects that are automatically created for managing object changes. Also, do not modify the resources within a project outside of the product; otherwise, unpredictable results can occur.

You can use the Team features of Eclipse to store and retrieve projects and project resources in a library control system so that multiple users can share the resources and use version control.


Feedback