Page tree

Release 9.2


Our documentation site is moving!

For up-to-date documentation of release 9.2 of Self Managed Designer Cloud, please visit us at


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

DB Installation Prerequisites

  • You must install a supported database distribution. For more information on the supported database versions, see System Requirements in the Planning Guide.
    • 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 Alteryx node
    • For more information on default ports, see System Ports in the Planning Guide.
    • 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 Alteryx software has been installed. You should install the software on the Alteryx node  first.
  • You must install the appropriate database client for your software distribution. Instructions are provided later.

Other prerequisites specific to the database distribution may be listed in the appropriate section below.  

If you are concerned about durability and disaster recovery of your Alteryx metadata, your enterprise backup procedures should include the Alteryx databases. See Backup and Recovery in the Admin Guide.

List of Databases

The Designer Cloud Powered by Trifacta® platform requires access to the following databases. Below, you can review database names, descriptions and release in which it was introduced:

Database NameDescriptionFirst Release

Alteryx database (Main)

Storage of users and metadata about your datasets, including completed jobs.Release 1.0
Jobs databaseStorage of job tracking information. Jobs are purged upon completion or job timeout. Failed jobs are purged periodically. Release 3.2

Scheduling database

Storage of schedules, including datasets to execute.Release 4.1
Time-based Trigger databaseStorage of triggering information.Release 4.1
Configuration Service databaseStorage of system-, tier-, and user-level configuration settings.Release 6.0
Artifact Storage Service databaseStorage for feature-specific usage data such value mappings.Release 6.0
Job Metadata Service databaseStorage of metadata on job execution.Release 6.4
Authorization Service databaseStorage 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
Optimizer Service databaseStorage of SQL queries to optimize logical and physical performance during job execution.Release 7.6
Secure Token Service databaseStorage of access tokens for managing integrations with external datasource such as OAuth2 connections.Release 7.10
Connector Configuration Service databaseStorage of metadata and overrides on connector types.Release 8.1


This page has no comments.