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 , your enterprise backup procedures should include the . See Backup and Recovery in the Admin Guide.
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|
|Storage of schedules, including datasets to execute.||Release 4.1|
|Time-based Trigger database||Storage of triggering information.||Release 4.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|
|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.
|Optimizer Service database||Storage of SQL queries to optimize logical and physical performance during job execution.||Release 7.6|
|Secure Token Service database||Storage of access tokens for managing integrations with external datasource such as OAuth2 connections.||Release 7.10|
|Connector Configuration Service database||Storage of metadata and overrides on connector types.||Release 8.1|