About data connectors

Each Tonic workspace has a source database, which contains the original data, and a destination database, where Tonic writes the data after it runs a data generation job and applies the table mode, generator, and subsetting configuration.
Tonic provides a set of available data connectors. Each connector is associated with a specific application database, data warehouse, or Spark product. When you create a workspace, you choose the connector to use based on how your source data is stored.
Each data connector can have specific configuration requirements. A data connector also might not support all of the Tonic features.
For an overview list of the available data connectors, see Data connector summary.

License tier requirements for data connectors

An instance with a Basic license can use one data connector, which must be either MySQL or PostgreSQL.
An instance with a Professional license can use two data connectors, which can be any data connector other than Oracle.
The Enterprise license has no limits on the number of data connectors, and can use Oracle.

Types of data connectors

Data connectors fall into one of the following general categories. Tonic connects and writes to the data slightly differently for each type.

Application database

For an application database, Tonic connects to both the source and destination databases as an SQL client.
It reads data, transforms the data, and then writes the data directly to the destination database. The transformation occurs on the Tonic server.

Data warehouse

For a data warehouse, with the exception of Google BigQuery, Tonic uses a temporary file store in S3 and AWS Lambda functions to process the data. It then writes the data to the destination database.


For Spark data connectors, Tonic uses a metastore or data catalog to get the file format. It then uses Spark to process the source files and write to the destination files.

General rules for data connectors

Same data connector for source and destination

The source and destination databases use the same connector. For example, you cannot take data from a MySQL source database and then have Tonic generate an Oracle destination database.

Same version for source and destination

The source and destination databases also should use the same database version. At the very least, the version used by the destination database cannot be older than the version used by the source database. For example, if the source database uses PostgreSQL 12.8, then the destination database cannot use a lower version such as PostgreSQL 12.4.

Allowlisting Tonic static IP addresses

If you use a hosted Tonic instance, and your database only allows connections from allowlisted IP addresses, then you need to allowlist Tonic static IP addresses.
For the United States-based instance (, the static IP addresses are:
For the Europe-based instance (, the static IP addresses are: