Load MySQL data into BigQuery

This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of theService Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see thelaunch stage descriptions.

You can load data from MySQL to BigQuery using theBigQuery Data Transfer Service for MySQL connector. It supportsMySQL instances that are hosted in your on-premises environment,inCloud SQL, and in other public cloud providerssuch as Amazon Web Services (AWS) and Microsoft Azure. With the BigQuery Data Transfer Service, you canschedule recurring transfer jobs that add your latest data fromMySQL to BigQuery.

Before you begin

• Create a userin the MySQL database.
• Verify that you have completed all the actions that are required toenable the BigQuery Data Transfer Service.
• Create a BigQuery datasetto store your data.
• Verify that you have therequired roles to complete the tasks inthis document.

Required roles

To get the permissions that you need to create a BigQuery Data Transfer Service data transfer, ask your administrator to grant you theBigQuery Admin (roles/bigquery.admin) IAM role on your project. For more information about granting roles, seeManage access to projects, folders, and organizations.

This predefined role contains the permissions required to create a BigQuery Data Transfer Service data transfer. To see the exact permissions that are required, expand theRequired permissions section:

You might also be able to get these permissions withcustom roles or otherpredefined roles.

For more information, seeGrantbigquery.admin access.

If you intend to set up transfer run notifications for Pub/Sub,ensure that you have thepubsub.topics.setIamPolicy Identity and Access Management (IAM)permission. Pub/Sub permissions are not required if you only set upemail notifications. For more information, seeBigQuery Data Transfer Service run notifications.

Network connections

If a public IP address is not available for the MySQLdatabase connection, you mustset up a network attachment.

For detailed instructions on the required network setup, refer to the followingdocuments:

• If you're transferring from Cloud SQL, seeConfigure Cloud SQL instance access.
• If you're transferring from AWS, seeSet up the AWS-Google Cloud VPN and network attachment.
• If you're transferring from Azure, seeSet up the Azure-Google Cloud VPN and network attachment.

Limitations

MySQL data transfers are subject to following limitations:

• The maximum number of simultaneous connections to a MySQLdatabase is determined by the MySQL configuration parametermax_connections. By default, this is set to 151 connections, but it can beconfigured to a higher limit as needed. As a result, the number of simultaneoustransfer runs to a single MySQL database is limited to thatmaximum amount. This limitation also means that the number of concurrent transferjobs should be limited to a value less than the maximum number of concurrentconnections supported by the MySQL database.
• A single transfer configuration can only support one data transfer run at a giventime. In the case where a second data transfer is scheduled to run before thefirst transfer is completed, then only the first data transfer completes whileany other data transfers that overlap with the first transfer is skipped.
  • To avoid skipped transfers within a single transfer configuration, werecommend that you increase the duration of time between large datatransfers by configuring theRepeat frequency.

Data ingestion options

The following sections provide information about the data ingestion optionswhen you set up a MySQL data transfer.

TLS configuration

The MySQL connector supports the configuration for transport levelsecurity (TLS) to encrypt your data transfers into BigQuery. TheMySQL connector supports the following TLS configurations:

• Encrypt data, and verify CA and hostname: This mode performs a fullvalidation of the server using TLS over the TCPS protocol. It encrypts alldata in transit and verifies that the database server's certificate is signedby a trusted Certificate Authority (CA). This mode also checks that thehostname you're connecting to exactly matches the Common Name (CN) or aSubject Alternative Name (SAN) on the server's certificate. This mode preventsattackers from using a valid certificate for a different domain to impersonateyour database server.
  • If your hostname does not match the certificate CN or SAN, the connectionfails. You must configure a DNS resolution to match the certificate or use adifferent security mode.
  • Use this mode for the most secure option to prevent person-in-the-middle(PITM) attacks.
• Encrypt data, and verify CA only: This mode encrypts all data using TLSover the TCPS protocol and verifies that the server's certificate is signed bya CA that the client trusts. However, this mode does not verify the server'shostname. This mode successfully connects as long as the certificate is validand issued by a trusted VA, regardless of whether the hostname in thecertificate matches the hostname you are connecting to.
  • Use this mode if you want to ensure that you are connecting to a serverwhose certificate is signed by a trusted CA, but the hostname is notverifiable or you don't have control over the hostname configuration.
• Encryption only: This mode encryptsall data transferred between the client and the server. It doesnot perform any certificate or hostname validation.
  • This mode provides some level of security by protecting data in transit, butit can be vulnerable to PITM attacks.
  • Use this mode if you need to ensure all data is encrypted but can't ordon't want to verify the server's identity. We recommend using this modewhen working with private VPCs.
• No encryption or verification: This mode does not encrypt any data anddoes not perform any certificate or hostname verification. All data is sent asplain text.
  • We don't recommend using this mode in an environment where sensitive data ishandled.
  • We only recommend using this mode for testing purposes on an isolatednetwork where security is not a concern.

Trusted Server Certificate (PEM)

If you are using either theEncrypt data, and verify CA and hostname mode ortheEncrypt data, and verify CA mode, then you can also provide one or morePEM-encoded certificates. These certificates are required in some scenarioswhere the BigQuery Data Transfer Service needs to verify the identity of yourdatabase server during the TLS connection:

• If you are using a certificate signed by a private CA within your organizationor a self-signed certificate, you must provide the full certificate chain orthe single self-signed certificate. This is required for certificates issuedby internal CAs of managed cloud provider services, such as the AmazonRelational Database Service (RDS).
• If your database server certificate is signed by a public CA (for example,Let's Encrypt, DigiCert, or GlobalSign), you don't need to provide acertificate. The root certificates for these public CAs are pre-installed andtrusted by the BigQuery Data Transfer Service.

You can provide PEM-encoded certificates in theTrusted PEM Certificatefield when you create a MySQL transfer configuration, with thefollowing requirements:

• The certificate must be a valid PEM-encoded certificate chain.
• The certificate must be entirely correct. Any missing certificates in thechain or incorrect content causes the TLS connection to fail.
• For a single certificate, you can provide single, self-signed certificatefrom the database server.
• For a full certificate chain issued by a private CA, you must provide thefull chain of trust. This includes the certificate from the database serverand any intermediate and root CA certificates.

Load MySQL data into BigQuery

Add MySQL data into BigQuery by setting up atransfer configuration using one of the following options:

bqmk--transfer_config--project_id=PROJECT_ID--data_source=DATA_SOURCE--display_name=DISPLAY_NAME--target_dataset=DATASET--params='PARAMETERS'

bqmk--transfer_config--target_dataset=mydataset--data_source=mysql--display_name='My Transfer'--params='{"assets":["DB1/DEPARTMENT","DB1/EMPLOYEES"],        "connector.authentication.username": "User1",        "connector.authentication.password":"ABC12345",        "connector.encryptionMode":"FULL",        "connector.database":"DB1",        "connector.endpoint.host":"54.74.220.23",        "connector.endpoint.port":3306        "connector.tls.mode": "ENCRYPT_VERIFY_CA_AND_HOST",        "connector.tls.trustedServerCertificate": "PEM-encoded certificate"}'

To manually run a data transfer outside of your regular schedule, you can startabackfill run.

Data type mapping

The following table maps MySQL data types to the correspondingBigQuery data types.

Troubleshoot

If you are having issues setting up your data transfer, seeMySQL transfer issues.

What's next

• For an overview of the BigQuery Data Transfer Service, seeWhat is BigQuery Data Transfer Service?.
• For information on using transfers, including getting information about atransfer configuration, listing transfer configurations, and viewing atransfer's run history, seeManage transfers.
• Learn how toload data with cross-cloud operations.