![[Note]](../common/images/note.png) | Note |
|---|---|
Please read the Supported Operating Environments document on the CoreMedia DXP 8 documentation page in order to get the actually supported databases. |
The configuration of the database is done using the sql.properties file and the database dependent
<DBName>.properties files. The Content Server
connects with the database using JDBC. The JDBC driver JAR files must be installed in the
lib directory of the CoreMedia CMS installation.
| Note |
|---|---|
Note: The required JDBC drivers are not part of the CoreMedia CMS distribution; they must be obtained from the corresponding database manufacturer. |
The database must be accessible over the network and should be enabled for the Unicode character set. Each Content Server requires a different database user account. The database users must be able to create and delete tables and indexes in their schemas. (For Oracle, see Example 3.2, “Oracle: create DB User” and Example 3.4, “Oracle: delete DB User”)
Manual creation of tables is not necessary. A Content Server automatically creates tables, the first time it is started. The standard settings of the database or the standard values defined for the database user are used as default for the tables and indexes created, such as the initial reserved memory.
| Note |
|---|---|
Important: To guarantee high performance of the whole system, correct installation and regular database maintenance is necessary. In particular, the statistics data for tables and indexes must be updated daily according to the manufacturer's instructions. |
 |  |  |
 |