MySQL

This section explains how to set up a MySQL source in a data task. Before you start the data task, make sure that you have fulfilled the Prerequisites, set up the Required permissions, and familiarized yourself with the Limitations and considerations.

You need to configure connectivity to MySQL when landing data from any of the following databases:

• On-premises:

  • MySQL

  • Percona

    Information note

    When using Percona as a source, the CDC prerequisites described in Capturing changes from a customer-installed MySQL database are not relevant.

  • MariaDB

• Cloud-based:

  • Amazon Aurora

  • Amazon RDS for MySQL

  • Amazon RDS for MariaDB

  • Google Cloud SQL for MySQL

  • Microsoft Azure Database for MySQL

Setting connection properties

This section describes the available connection properties. All properties are required unless otherwise indicated.

Data source

• Data gateway: The name of the Data Movement gateway to use to access your data.

• Cloud provider: If your MySQL database is located in the cloud, select the provider:

  • None (default)

  • Amazon Aurora

  • Amazon RDS

  • Google Cloud

  • Microsoft Azure

• Server: The host name or IP address of the computer on which the MySQL database is installed.

• Port: The port through which Qlik Cloud services will access the MySQL database. The default is 3306.

Account properties

User Name and Password: The user name and password of a user authorized to access the MySQL database.

SSL options

You can configure Qlik Data Gateway - Data Movement to connect to the data source using SSL.

• SSL Mode: Select one of the following:
  • None - Connect with a surname and password only.
  • Preferred - Establishes an encrypted connection if the server supports encrypted connections, falling back to an unencrypted connection if an encrypted connection cannot be established.
  • Required - Establishes an encrypted connection if the server supports encrypted connections. The connection attempt fails if an encrypted connection cannot be established.
  • Verify CA - Similar to Required, but also verifies the server Certificate Authority (CA) certificate against the configured CA certificates. The connection attempt fails if no valid matching CA certificates are found.
  • Verify Full - Similar to Verify CA, but also performs host name identity verification by checking the host name the client (i.e. Qlik Data Gateway - Data Movement) uses for connecting to the server against the identity in the certificate that the server sends to the client. The client checks whether the host name that it uses for connecting matches the Common Name value in the server certificate. The connection fails if there is a mismatch.
• Trusted certificate: The Certificate Authority (CA) that issued the client certificate file in PEM format.
• Client certificate: The client certificate requested by the server.
• Client certificate key: The client private key file in PEM format.

Database properties

Database timezone: The timezone where the source database is located.

CDC properties

Check binary log for changes every - How often to check the binary log for changes when the database is idle (i.e. when no changes are done to the source tables). The default is five seconds. Usually there is no reason to change the interval. However, to reduce the load on the system, you might want to increase the interval in the following scenarios:

• The database is updated infrequently
• Polling the system for changes slows down the system
• Changes are not required in real time

Internal properties

Internal properties are for special use cases and are therefore not exposed in the dialog. You should only use them if instructed by Qlik Support.

Use the and buttons to the right of the fields to add or remove properties as needed.

Name

The display name for the source connection.