Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


The Trifacta® platform uses multiple SQL databases to manage platform metadata. This section describes how to install and initialize these databases.

DB Installation Pre-requisites

  • You must install a supported database distribution. For more information on the supported database versions, see System Requirements.
    • You must also acquire the database dependencies associated with the operating system distribution where the database is to be installed. Please see the database vendor for more information.
  • Please verify that the ports used by the database are opened on the Trifacta node
    • For more information on default ports, see System Ports.
    • If you need to use different ports, additional configuration is required. More instructions are provided later. 
  • Installation and configuration of the database cannot be completed until the Trifacta software has been installed. You should install the software on the Trifacta node  first.

Other pre-requisites specific to the database distribution may be listed in the appropriate section below.  

If you are concerned about durability and disaster recovery of your , your enterprise backup procedures should include the Trifacta databases. See Backup and Recovery.

List of Databases

The Trifacta® platform requires access to the following databases.

  • Main database: storage of users and metadata about your datasets, including completed jobs.
  • Jobs database: storage of job tracking information. Jobs are purged upon completion or job timeout. Failed jobs are purged periodically. 
  • Configuration Service database: storage of parameter settings at the workspace level.
  • Artifact Storage Service database: storage for feature-specific usage data such value mappings.

  • Job Metadata Service database: storage of metadata on job execution.

The scheduling feature is enabled by default. If it's enabled, the following databases are also required:

  • Scheduling database: Storage of schedules, including datasets to execute
  • Time-based Trigger database: Storage of triggering information.
  • For more information, see Configure Automator.



  • No labels

This page has no comments.