Configuration Database Overview

GENESIS relies on Microsoft SQL Server to store and manage configuration database information. A database comprises of a set of schemes (also known as a catalog in SQL Server terms) within associated tables and data.

Two types of database configurations are created by default with each installation.

• Server configurations: Contain configuration elements related to each point manager and GENESIS component.
• Project configurations: Contain information specific to the Workbench project, such as the project title, and link all server configurations to the project instance. By default, this database is named IcoSetup.

An application can have all server (component) configurations stored in a single unified database, by default IcoUnifiedConfig, or it can store each server configuration in a separate database, or combine the two options.

Using separate databases for each server configuration is not applicable in the following cases:

• For Data Historian integration with Assets, it is required that Assets, Data Historian, and Data Historian Asset Integration share the same database.

• For Alarm Server integration with Assets, it is required that Assets, Alarm Server, and Alarm Server Asset Integration share the same database.

Configuration databases can be distributed across multiple SQL Server instances, either local or remote.

You can configure the databases in the stand-alone Configure System application, especially after installation. Learn more

Use the database management options in Workbench to edit the configuration or upgrade, back up, restore, or delete a database. Learn more