Data Sources
Cadenza data sources can be created and managed by Cadenza administrators as part of a repository in the Management Center (“repository data sources”). Alternatively, system administrators can define data sources via datasources Configuration (“cross-repository data sources”, since they are independent of a specific repository).
With cross-repository data sources, the system administration is responsible for both the physical data sources and the Cadenza data sources with all their properties. In the Management Center, authorized users can view the data sources and some of their properties. They also grant authorizations for the data sources. For RDBMS-based data sources authorizations are granted per database schema. So a single cross-repository data source can provide access to multiple schemas; there is no need to create a separate data source for each schema.
Unlike data in different data sources, data in different schemas within the same (RDBMS) data source can be linked by associations and then analyzed together, provided that the objecttypes are stored in the same repository (a restriction that will be removed in an upcoming Cadenza version).
Cadenza Data Stores (CDS)
One cross-repository RDBMS data source – the main data source - must be configured with a CDS schema: In this central CDS schema Cadenza stores all newly created self-service data of all repositories.
For other data sources a CDS schema is generally not required or even not allowed. An exception applies for RDBMS data sources when data that is already stored in the database needs to be enriched: Since new data is stored in the same schema as the enriched data, the data source must be configured with a CDS schema. Enrichment data will be stored there, other self-service data will still be stored in the central CDS schema.
Data Sources From Earlier Cadenza Versions
Repository data sources used as a CDS and repository data sources based on data source templates are no longer supported.
In the Management Center, Cadenza marks such data sources as invalid. If their objecttypes, layers and data are still needed, they must be migrated to cross-repository data sources as described in Migrating Repository Data Sources to Cross-Repository Data Sources.
When former CDS data sources are migrated, their database schema will not be used as a CDS anymore. In case a CDS is really needed (see exception above) it is possible to use and configure the schema also as a CDS (secondary) schema.
Recommendations
We recommend consolidating data as much as possible into one RDBMS database with different schemas (but the same database user).
We also recommend defining as few RDBMS data sources as possible. Ideally, the main data source even is only RDBMS data source (containing the only CDS schema).