Database Requirements
Cadenza requires a relational database backend to store its configuration, repository metadata, and optionally to manage data. The following database systems are supported for Cadenza’s internal database schemas:
Required Database Schemas
| Database Schema | Oracle | PostgreSQL/EDB | MSSQL |
|---|---|---|---|
System database (systemdb) |
✅ |
✅ |
– |
Repository database (databaserepository) |
✅ |
✅ |
– |
Cadenza Data Store (CDS) |
✅ |
✅ |
✅ |
| While technically optional, CDS schemas are required for the full functionality of Cadenza. |
Additional Requirements for PostgreSQL
When using PostgreSQL as your database backend, the following additional requirement must be met:
PostGIS Extension: The PostGIS extension must be installed on the PostgreSQL server before creating Cadenza Data Store (CDS) schemas. PostGIS provides spatial data types and functions required by Cadenza.
The SQL scripts for PostgreSQL schema creation include the command CREATE EXTENSION postgis; to activate the extension - this command will fail if PostGIS is not already installed on your PostgreSQL server.
Optional Database Schemas
| Database Schema | Oracle | PostgreSQL/EDB | MSSQL |
|---|---|---|---|
Audit logging |
✅ |
✅ |
– |
Moratorium (for Data Protection Contexts) |
✅ |
✅ |
– |
Performance logging |
✅ |
– |
– |
For detailed setup instructions, see Preparing the Database.