The management of CCH Tagetik databases
Introduction¶
Every CCH Tagetik installation contains a centralised database (Repository) and one or more application databases.
Repository management functions¶
A list of the main functions is provided below:
| Function | Description |
|---|---|
| General Settings | Sets the general characteristics of the entire application, manages user authentication and the execution settings for all data processing performed by CCH Tagetik. |
| Users & Roles | Defines users and roles, sets rights, limits the field of action and associates accessible databases. |
| Database | Displays the linked databases and indicates whether they are accessible. |
| Data Processing | Defines how CCH Tagetik processes data. |
| Import/Export | Exports and imports tables from the various databases. |
| Monitor | Monitors the current data processing , log tracking and server status. |
| Scheduling | Sets the scheduled data processing and creates processing groups. |
| Master Data Management | Updates settings and metadata and transfers them from one environment to another (typically from a test environment to a production environment). |
| Audit | Allows consultation of application logs. |
System tables¶
The CCH Tagetik database contains the following system tables:
| Table node | Description |
|---|---|
| Setup | Tables for setting the metadata, rules and calculation logics |
| Data | Tables with numerical values |
| Users | Tables related to user rights over metadata |
| Deployed | Tables generated by the deployment of CCH Tagetik |
| Offline data & setup | Tables with data stored offline |
| Logs | Tables with log information |
These tables are displayed by group on the Import Tool, Export Tool and Master Data Management pages to facilitate the administrator’s job.
Other tables¶
The CCH Tagetik database also contains the following tables:
| Table node | Description |
|---|---|
| Service | Table used by the system but not necessary for standard exporting and importing |
| Custom | Tables created by the user |
Characteristics of exported files¶
The compressed files generated via exporting from the database contain:
- an encrypted file for every exported table containing the table itself
- a log file with information on the performance of the export (rows exported, time taken etc.)
- a file with the metadata of all the tables
The files are exported in compressed format (.zip) and are encrypted.
Example of an exported file
The name of an exported file is structured as follows:
| Element | Description | Example |
|---|---|---|
| Prefix | Software that generated the code | tcpm |
| User | Code of the user who requested the export | USER |
| Data Processing | Data process that generated the file | EXP |
| Type | Type of database exported: ORA = Oracle SQL = MS SQL Server | SQL |
| Code | Code of the exported database | TCPM_D0000 |
| Version | Database version number | 3.1006 |
| Patch | Database patch number | 0 |
| Date | Day and month in which the file was created | 2610 |
| Time | Time (hours and minutes) when the file was created | 1225 |
| Number | Reason number | 64781 |
| Part | Files generated by the export as a portion of total files | part_1_of_2 |
As in this example:
tcpm_USER_EXP_SQL_TCPM_D0000_3.1006_0_2610_1225_64781_part_1_of_2.zip
Location of files to be imported¶
CCH Tagetik allows files to be imported from several locations:
| Location | Description |
|---|---|
| Client | The files are stored locally on a machine accessible by the user. |
| Remote files | The files are loaded onto the application server in the predefined folder for file uploads. |
| Application server | The files are loaded onto the application server in any folder. In this case, the file path of the folder must be specified. |
| Endpoint / Tagetik Agent | The files are uploaded to the location specified as the Endpoint/Tagetik Agent. |
Import and export of analytical workspaces and analytical dimensions¶
Analytical workspaces and dimensions are imported and exported by means of the dummy table ANALYTICAL_WORKSPACE_TABLES.
Analytical workspaces and analytical dimensions can be imported under the following conditions:
- the write mode must be “Deletion/Insertion”
- all workspaces and datasets in the environment must be online
The import process comprises the following phases:
| Phase | Description |
|---|---|
| 1 | The analytical workspaces are placed offline. |
| 2 | The data is imported into the analytical workspace and analytical dimensions tables. |
| 3 | New tables will be created and the old ones removed. |
| 4 | The new analytical workspaces will be placed online again. |
In detail, the outcome of the import is as follows:
- The existing settings tables will be overwritten for both the analytical workspaces and the analytical dimensions.
- The existing partitions will be maintained and updated according to the imported settings.
- The list and physical tables of the partitions will not be imported.
- No partitions related to datasets not found in the source environment will be removed. These partitions must be removed manually in the destination database.
Query analyzer¶
The Query Analyzer function makes it possible to launch script on the database tables. Users for whom this function has been enabled can interact at the basic level with the data present in the database, with the exclusion of data in the audit tables. Specifically, the user can:
- in particular cases, directly control the data
- carry out complex maintenance and restructuring activities on the CCH Tagetik database
- use queries in advanced mode
If the user has the Query Analyzer function enabled in read-only mode, they can only use the select function in the query. If editing is also enabled, they can use all the functions (select, insert, delete, update).
Note: the system can only run one query at a time: the first one it finds on the list. The query will be run on the current DB connection.