Configuring MySQL workspace data connections

During workspace creation, under Connection Type, click MySQL.

Connecting to the source database

In the Source Settings section, you provide the connection information for the source database.

Providing the connection details

To provide the connection details for the source database:

1. In the Server field, specify the server where the source database is located.

2. By default, Tonic Structural uses all of the databases on the source server. To instead identify specific databases, add them to the Databases field. To add a database, type the database name, then press Enter. To remove a database from the list, click its delete icon.

3. In the Port field, provide the port to use to connect to the source data.

4. In the Username field, provide the username to use to connect to the source data.

5. For Password, you can either specify the password manually or, if secrets managers are available, you can select a secret name from a secrets manager.

6. To test the connection to the source data, click Test Source Connection. If the connection test is successful, then Structural also tests and reports on the connection speed.

Connection security settings

For the source connection, you can also:

• Use SSL/TLS to encrypt authentication.

• Use a connection tunneling option (SSH or Tailscale).

Connecting to the intermediate database for upsert

MySQL supports the upsert process. When you enable upsert for the workspace, the data generation process initially writes the transformed data to an intermediate database.

After the initial data generation is complete, the upsert job writes new records to the destination database, and updates existing records in the destination database. It does not touch any other records that are in the destination database.

In the Upsert section, when you enable upsert, you are prompted to configure the upsert processing and to provide connection information for the intermediate database.

Providing the connection details

To provide the connection details for the intermediate database:

1. In the Server field, specify the server where the intermediate database is located. For each database selected from the source, Structural generates data into a database that uses the same name as the corresponding destination database. To prevent conflicts, the server for the intermediate database must be different from the server for the source database and the destination database.

2. In the Port field, provide the port to use to connect to the intermediate database.

3. In the Username field, provide the username to use to connect to the intermediate database.

4. For Password, you can either specify the password manually or, if secrets managers are available, you can select a secret name from a secrets manager.

5. To test the connection to the intermediate database, click Test Intermediate Connection. If the connection test is successful, then Structural also tests and reports on the connection speed.

Connection security settings

For the intermediate database connection, you can also:

• Use SSL/TLS to encrypt authentication.

• Use a connection tunneling option (SSH or Tailscale).

Connecting to the destination database

For a MySQL workspace, you can write the destination data to either:

• A destination database server.

• A container repository. For more information, go to Writing output to a container repository.

Under Destination Settings, to write the transformed data to a database server, click Database Server.

By default, the destination database uses the same databases as the source database.

Providing the connection details

To provide the connection details for the destination database:

1. In the Server field, specify the server where the destination database is located. For each database selected from the source, Structural generates data into a database of the same name. To prevent a conflict, the server for the destination database must be different from the server for the source database and the intermediate database.

2. By default, the destination database names match the source database names. You can optionally provide different database names for the destination. Note that in the following cases, you cannot rename the destination databases:

   • You do not specify the source databases to include.

   • You provide the database schema.

   To enable custom destination database names, toggle Custom database names to the on position. When you enable custom destination database names, the source databases are listed under Original Database Name. The New Database Name column contains the corresponding destination database names, which by default match the source names. To provide a different database name, in the New Database Name field, enter the new name.

3. In the Port field, provide the port to use to connect to the destination data.

4. In the Username field, provide the username to use to connect to the destination data.

5. For Password, you can either specify the password manually or, if secrets managers are available, you can select a secret name from a secrets manager.

6. To test the connection to the destination database, click Test Destination Connection. If the connection test is successful, then Structural also tests and reports on the connection speed.

Connection security settings

For the destination connection, you can also:

• Use SSL/TLS to encrypt authentication.

• Use a connection tunneling option (SSH or Tailscale).