Automated Continuous AlloyDB Replication to Google BigQuery

Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live AlloyDB data into your Google BigQuery instance, allowing you to consolidate all of your data into a single location for archiving, reporting, analytics, machine learning, artificial intelligence and more.

Configure Google BigQuery as a Replication Destination

Using CData Sync, you can replicate AlloyDB data to Google BigQuery. To add a replication destination, navigate to the Connections tab.

1. Click Add Connection.
2. Select Google BigQuery as a destination.

3. Enter the necessary connection properties. To connect to Google BigQuery, use OAuth authentication:

   Authenticate with a User Account

   In this OAuth flow, you can connect without setting any connection properties for your user credentials.

   1. Click Connect, and CData Sync opens the Google BigQuery OAuth endpoint.
   2. Log in and grant permissions to CData Sync.
   3. CData Sync then completes the OAuth process.

   Authenticate with a Service Account

   Service accounts have silent authentication, without user authentication in the browser. You can also use a service account to delegate enterprise-wide access scopes to CData Sync.

   You need to create an OAuth application in this flow. See Creating a Custom OAuth App in the Getting Started section to create and authorize an app. You can then connect to Google BigQuery data that the service account has permission to access.

   After setting the following connection properties, you are ready to connect:

   • OAuthClientId: Set this to the Client ID in your app settings.
   • OAuthClientSecret: Set this to the Client Secret in your app settings.
   • OAuthJWTCertType: Set this to "PEMKEY_FILE".
   • OAuthJWTCert: Set this to the path to the .pem file you generated.
   • OAuthJWTCertPassword: Set this to the password of the .pem file.
   • OAuthJWTCertSubject: Set this to "*" to pick the first certificate in the certificate store.
   • OAuthJWTSubject: Set this to the email address of the user for whom the application is requesting delegate access. Note that delegate access must be granted by an administrator.
   • DatasetId: Set this to the ID of the dataset you want to connect to.
   • ProjectId: Set this to the ID of the project you want to connect to.
   When you connect, CData Sync completes the OAuth flow for a service account.

4. Click Test Connection to ensure that the connection is configured properly.
5. Click Save Changes.

Configure the AlloyDB Connection

You can configure a connection to AlloyDB from the Connections tab. To add a connection to your AlloyDB account, navigate to the Connections tab.

1. Click Add Connection.
2. Select a source (AlloyDB).
3. Configure the connection properties.
   
   

   The following connection properties are usually required in order to connect to AlloyDB.

   • Server: The host name or IP of the server hosting the AlloyDB database.
   • User: The user which will be used to authenticate with the AlloyDB server.
   • Password: The password which will be used to authenticate with the AlloyDB server.

   You can also optionally set the following:

   • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
   • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

   Authenticating with Standard Authentication

   Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

   No further action is required to leverage Standard Authentication to connect.

   Authenticating with pg_hba.conf Auth Schemes

   There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

   Find instructions about authentication setup on the AlloyDB Server here.

   Authenticating with MD5 Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

   Authenticating with SASL Authentication

   This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

   Authenticating with Kerberos

   The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.

4. Click Connect to ensure that the connection is configured properly.
5. Click Save Changes.

Configure Replication Queries

CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.

Replicate Entire Tables

To replicate an entire table, click Add Tables in the Tables section, choose the table(s) you wish to replicate, and click Add Selected Tables.

Customize Your Replication

You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication.

Schedule Your Replication

In the Schedule section, you can schedule a job to run automatically, configuring the job to run after specified intervals ranging from once every 10 minutes to once every month.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your AlloyDB data to Google BigQuery.