Database Structure

The format of the SICS database has been designed to be as flexible as possible. Its structure has only been enforced where necessary, allowing for multiple configuration possibilities. The configuration at your site should be determined in advance by your DBA, based on your requirements and the specification of your Database Management System (DBMS).

Note: Terminology in this chapter relates to Oracle. SQL Server does not have the concept of Instances, but the following text still applies. The Instance in this case will relate exclusively to a particular SQL Server Database (not the same concept as a SICS database).

Configuration Overview #

Each SICS database consists of a number of tables, having indexes and constraints. Together, these make up a Schema. This is also called a ‘[SICS] Environment’. The terms ‘SICS database’, ‘[SICS] Environment’ and ‘[SICS] schema’ are used interchangeably. RDBMS Instance contains one or more SICS databases/environments/schemas. The diagram below shows the relationships between these objects.

Figure 2 - SICS Database Configuration

SICS Databases #

Each DBMS Instance above may contain one or many SICS databases/environments/schemas. In a test & production setup, if may be preferable to create the SICS database for test in one DBMS Instance and the SICS database for production in another DBMS Instance. These instances would be accessed through separate JDBC definitions.

SICS Environment Table #

As mentioned, each DBMS Instance may contain multiple SICS databases/environments/schemas. There can be as many different SICS environments in the instance as required. The environments may relate to a mix of SICS P&C and Life installations. For easy user access to any of these environments, one can create a special table CNU_ENVIRONMENT. Each row in this table will describe one particular SICS environment. Typically, one will create the CNU_ENVIRONMENT table in its own schema.

SICS Tables #

Each SICS environment will contain the relevant SICS tables. These tables may define a P&C or a Life database. Each environment handles its own security, so you may be able to connect to SICS P&C in Instance 1 but not SICS Life in the same instance, if required.

Supported Databases #

Access to the database is through JDBC, which allows for multiple DBMS support. For information about which databases SICS supports, and which JDBC drivers to use, please see Hardware and Software Requirements.

For short, these databases are sometimes in this document referred to as ‘Oracle’, ‘SQL Server’ and ‘PostgreSQL’.