Planning the SQL Catalogue (CONNX CDD)
In CONNX, the SQL Catalog is called the CONNX CDD.
The CONNX CDD is the cornerstone of the CONNX product family. It contains the metadata that describes all of the organization's enterprise data.
Your installation can have multiple CDDs. For example, one CDD for the development environment databases, a second CDD that is an exact clone of the development CDD, and a third CDD containing an entirely different set of databases for your production environment. An organization usually has a collection of ad-hoc CDDs it uses for off-line development and testing, along with a master CDD for use in production.
The CONNX Client determines the view of the CDD. The current CONNX Client connection contains the current view of the CDD. If the CDD is modified while the connection is running, the CONNX Client will not recognize the changes until a new connection is spawned.
Keep the production and development CDDs that you consider project resources in a controlled access environment, under a revision control system such as a source repository.
The CDD is CONNX's sole point of entry to data. Only the CONNX CDD Manager can create the initial database connection which is required for data access. Determining where to install the CDD Manager is as important, as deciding where to keep the CDDs.
When you enable connection pooling (instead of reusing an existing connection), CONNX creates a fresh connection for any altered CDD. In this case, only the current CDD version is the metadata repository connection.
CONNX CDDs can be linked together in a parent/child relationship.