Search…
⌃K
Links

Configuring SQL Server workspace data connections

During workspace creation, under Connection Type, click SQL Server.

Connecting to the source database

In the Source Server section, provide the details about the source database.

Providing the source database connection details

To provide the connection details for the source database:
  1. 1.
    In the Server field, provide the server where the database is located.
  2. 2.
    In the Database field, provide the name of the database.
  3. 3.
    In the Port field, provide the port to use to connect to the database.
  4. 4.
    In the Username field, provide the username for the account to use to connect to the database.
  5. 5.
    In the Password field, provide the password for the specified username.
  6. 6.
    To test the connection to the source data, click Test Source Connection.

Providing SSL authentication settings

To configure SSL authentication for the source database:
  1. 1.
    By default, SSL is enabled, and Enable SSL/TLS is in the on position. We strongly recommend that you do not turn off SSL.
  2. 2.
    To use Kerberos or NTLM authentication:
    1. 1.
      Toggle Integrated Security to the on position.
    2. 2.
      For Kerberos authentication, in the Kerberos Domain field, provide the Kerberos domain. For NTLM authentication, leave the field empty.
  3. 3.
    To indicate that Tonic should trust the server certificate, toggle Trust Server Certificate to the on position.
  4. 4.
    To connect to an SSH bastion for additional security:
    1. 1.
      Toggle Enable SSH Tunnel to the on position.
    2. 2.
      In the SSH Host field, provide the host for the SSH bastion.
    3. 3.
      In the SSH Port field, provide the port for the SSH bastion.
    4. 4.
      In the SSH User field, provide the name of the user to use to connect to the SSH bastion.
    5. 5.
      If you do not use a private key, then in the SSH Passphrase field, provide the passphrase to use for authentication.
    6. 6.
      If you do use a private key, then in the SSH Private Key field, provide the private key. If the private key uses a passphrase, then in the SSH Passphrase field, provide the passphrase for the private key.

Blocking data generation on all schema changes

By default, data generation is not blocked as long as schema changes do not conflict with your workspace configuration.
To block data generation when there are any schema changes, regardless of whether they conflict with your workspace configuration, toggle Block data generation on schema changes to the on position.

Connecting to the destination database

In the Destination Server section, you specify the connection information for the destination database.

Copying source connection and authentication details

To copy the connection and authentication details from the source database:
  1. 1.
    Click Copy Settings from Source.
  2. 2.
    In the Password field, provide the password.
  3. 3.
    To test the connection to the destination database, click Test Destination Connection.

Providing destination database connection details

If you do not copy the source connection details, then to configure the connection to the destination database:
  1. 1.
    In the Server field, provide the server where the database is located.
  2. 2.
    In the Database field, provide the name of the database.
  3. 3.
    In the Port field, provide the port to use to connect to the database.
  4. 4.
    In the Username field, provide the username for the account to use to connect to the database.
  5. 5.
    In the Password field, provide the password for the specified username.
  6. 6.
    To test the connection to the destination data, click Test Destination Connection.

Providing SSL authentication settings

To configure the SSL authentication for the destination database:
  1. 1.
    By default, SSL is enabled, and Enable SSL/TLS is in the on position. We strongly recommend that you do not turn off SSL.
  2. 2.
    To use Kerberos or NTLM authentication:
    1. 1.
      Toggle Integrated Security to the on position.
    2. 2.
      For Kerberos authentication, in the Kerberos Domain field, provide the name of the Kerberos domain. For NTLM authentication, leave the field empty.
  3. 3.
    To indicate that Tonic should trust the server certificate, toggle Trust Server Certificate to the on position.
  4. 4.
    To connect to an SSH bastion for additional security:
    1. 1.
      Toggle Enable SSH Tunnel to the on position.
    2. 2.
      In the SSH Host field, provide the host for the SSH bastion.
    3. 3.
      In the SSH Port field, provide the port for the SSH bastion.
    4. 4.
      In the SSH User field, provide the name of the user to use to connect to the SSH bastion.
    5. 5.
      If you do not use a private key, then in the SSH Passphrase field, provide the passphrase to use for authentication.
    6. 6.
      If you do use a private key, then in the SSH Private Key field, provide the private key. If the private key uses a passphrase, then in the SSH Passphrase field, provide the passphrase for the private key.