The uses multiple SQL databases to manage platform metadata. This section describes how to install and initialize these databases.
If you are concerned about durability and disaster recovery of your |
The requires access to the following databases. Below, you can review database names, descriptions and release in which it was introduced:
Database Name | Description | First Release |
---|---|---|
| Storage of users and metadata about your datasets, including completed jobs. | Release 1.0 |
Jobs database | Storage of job tracking information. Jobs are purged upon completion or job timeout. Failed jobs are purged periodically. | Release 3.2 |
Authorization Service database | Storage of object permissions. | Release 7.1 |
Orchestration Service database | Storage of plan execution information. Information is purged upon completion or run timeout. Failed runs are purged periodically. | Release 7.1 |
Configuration Service database | Storage of system-, tier-, and user-level configuration settings. | Release 6.0 |
Artifact Storage Service database | Storage for feature-specific usage data such value mappings. | Release 6.0 |
Job Metadata Service database | Storage of metadata on job execution. | Release 6.4 |
Scheduling database | Storage of schedules, including datasets to execute. | Release 4.1 |
Time-based Trigger database | Storage of triggering information. | Release 4.1 |