VOOZH about

URL: https://www.cdata.com/kb/tech/salesforce-sync-googlecloudsql.rst

⇱ Automated Continuous Salesforce Replication to Google Cloud SQL

Automated Continuous Salesforce Replication to Google Cloud SQL

👁 Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Use CData Sync for automated, continuous, customizable Salesforce replication to Google Cloud SQL.

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

About Salesforce Data Integration

Accessing and integrating live data from Salesforce has never been easier with CData. Customers rely on CData connectivity to:

  • Access to custom entities and fields means Salesforce users get access to all of Salesforce.
  • Create atomic and batch update operations.
  • Read, write, update, and delete their Salesforce data.
  • Leverage the latest Salesforce features and functionalities with support for SOAP API versions 30.0.
  • See improved performance based on SOQL support to push complex queries down to Salesforce servers.
  • Use SQL stored procedures to perform actions like creating, retrieving, aborting, and deleting jobs, uploading and downloading attachments and documents, and more.

Users frequently integrate Salesforce data with:

  • other ERPs, marketing automation, HCMs, and more.
  • preferred data tools like Power BI, Tableau, Looker, and more.
  • databases and data warehouses.

For more information on how CData solutions work with Salesforce, check out our Salesforce integration page.


Getting Started


Configure Google Cloud SQL as a Replication Destination

Using CData Sync, you can replicate Salesforce data to Google Cloud SQL. To add a replication destination, navigate to the Connections tab. Then select the appropriate destination based on your Google Cloud SQL service (MySQL, PostgreSQL, or SQL Server).

MySQL

  1. Click Add Connection.
  2. Select MySQL as a destination. 👁 Configure a Destination connection to MySQL.
  3. Enter the necessary connection properties. To connect to MySQL, set the following:
    • Server: The IP address or domain name of the server you want to connect to.
    • Port: The port where the server is running.
    • User: The username of a user with read/write access to the database.
    • Password: The password of a user with read/write access to the database.
    • Database: The name of the database.
  4. Click Test Connection to ensure that the connection is configured properly. 👁 Configure a Destination connection.
  5. Click Save Changes.

Jump to configuring the Salesforce connection.

PostgreSQL

  1. Click Add Connection.
  2. Select PostgreSQL as a destination. 👁 Configure a Destination connection to PostgreSQL.
  3. Enter the necessary connection properties. To connect to PostgreSQL, set the following connection properties (CData Sync ships with the Npgsql ADO.NET Provider for PostgreSQL):
    • Server: The address of the server hosting the PostgreSQL database.
    • Port: The port used to connect to the server hosting the PostgreSQL database.
    • User: The user ID provided for authentication with the PostgreSQL database.
    • Password: The password provided for authentication with the PostgreSQL database.
    • Database: The name of the database.
  4. Click Test Connection to ensure that the connection is configured properly. 👁 Configure a Destination connection.
  5. Click Save Changes.

Jump to configuring the Salesforce connection.

SQL Server

  1. Click Add Connection.
  2. Select SQL Server as a destination. 👁 Configure a Destination connection to SQL Server.
  3. Enter the necessary connection properties. To connect to SQL Server, set the following:
    • Server: The name or network address of the computer running SQL Server.
    • User: The username provided for authentication with SQL Server, if using forms authentication.
    • Password: The password provided for authentication with SQL Server, if using forms authentication.
    • Database: The name of the SQL Server database.

    Java Edition

    The Java version requires the Microsoft SQL Server JDBC driver, which can be downloaded from the Microsoft Download Center. Copy the JDBC driver to the lib folder of your Java Web server to make a connection.

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

Jump to configuring the Salesforce connection.

Configure the Salesforce Connection

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

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

    There are several authentication methods available for connecting to Salesforce: OAuth, Login (or basic), and SSO. The Login method requires you to have the username, password, and security token of the user.

    OAuth Authentication (default)

    The default authentication mechanism (and the one preferred by Salesforce) is OAuth. To use OAuth with CData's embedded OAuth application, leave the connection properties blank. If you have configured your own custom OAuth application with Salesforce (see the Help documentation for more information), set OAuthClientId, OAuthClientSecret, and CallbackURL to the properties for you application. Set InitiateOAuth to the desired OAuth flow ("GETANDREFRESH" will have the connector manage the entire OAuth flow).

    Login (or Basic) Authentication

    If you do not wish do not wish to use OAuth authentication, you can use Login (or basic) authentication. Set AuthScheme to Basic, and set the User, Password, and SecurityToken properties. You can configure your security token in Salesforce.

    SSO (single sign-on) Authentication

    SSO (single sign-on) can be used by setting the SSOProperties, SSOLoginUrl, and SSOExchangeURL connection properties, which allow you to authenticate to an identity provider. See the "Getting Started" chapter in the Help documentation for more information.

    Multi-Factor Authentication (MFA)

    If your Salesforce org has MFA enforcement enabled, set MFACode to the time-based one-time passcode (TOTP) generated by your authenticator app (such as Salesforce Authenticator or Google Authenticator). MFACode applies to both OAuth and Login authentication flows.

    👁 Configuring a Source connection (Salesforce is shown).
  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.

👁 Select Source and Destination connections for the 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.

👁 Choose entire tables to replicate (Salesforce is shown).

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. 👁 Configure a replication Transform.

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.

👁 Schedule your job to run automatically.

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