You can use a Data Design Project to track the life cycle of
a database. The project can be shared by using the Eclipse team functionality
so that several database administrators (DBAs) can collaborate on a change.
Once a change is deployed, the resources will usually be committed to library
control and tagged or labeled. The tag or label can be used to get back to
the save point. For example, to undo or audit the change.
In more complex databases, a Data Design Project can be used
to mange the life cycle of a particular database application. In some shops,
tables or schemas are broken up and managed by particular DBAs or DBA teams.
Data Design Projects can be adapted to match these environments. In this way,
a single database can be broken up and managed by several Data Design Projects.
A single Data Design Project can be used to manage
multiple databases if those databases are essentially copies of a primary
database. This is referred to as multiple provisioning which means
that the change is first constructed for a single database and is then deployed
to multiple databases.