Intended Data Manager process

The Data Manager helps the overall process for initial database creation. At a high level, that process includes the following three main steps:

  1. Create the database, tablespaces, and so on.
  2. Use the Data Manager to create tables and complete initial data loading.
  3. Data Base Administration (DBA) tasks to complete database creation, such as handcrafting scripts to tune the tables (ALTER) and set constraints.

The aim of the Data Manager is to help establish a skeletal database. Subsequently, a DBA can then write handcrafted scripts to complete the database by modifying tables and settings, such as LOCKSIZE or BUFFERPOOL.

Note: The SQL generated by the Data Manager is not intended to replace the role of a DBA. It is expected that there would be site-specific tweaking that is required to achieve production readiness.

A DBA would not be expected to manipulate the Cúram model to define extra entity options, such as LOCKSIZE, BUFFERPOOL, and similar commands, in order for the wanted SQL to be generated. This behavior is due to a number of factors. The modeling tools are unaware of the final deployment environment, and DBAs would not be expected to have the skill-sets for using the modeling environment.

The Data Manager is not intended to be used to upgrade an existing database. It exists only to reset the database to a known state.