![]() |
VOOZH | about |
CData Sync is a standalone application designed to support a variety of replication scenarios, such as replicating both sandbox and production instances into your database. It includes a web-based interface that simplifies the management of multiple Google Search connections. In this article, we demonstrate how to use the web app to replicate multiple Google Search accounts into a single database.
Using CData Sync, you can replicate data from Google Search to any number of databases, both cloud-based and on-premises. In this example, we use SQLite as the replication destination to demonstrate the process. To add it as a destination, navigate to the Connections tab.
For each destination database:
You are now connected to SQLite and can use it as both a source and a destination.
NOTE: You can use the Label feature to add a label for a source or a destination.
π Add a label.You can configure a connection to Google Search from the Connections tab. To add a connection to your Google Search account, navigate to the Connections tab.
To search with a Google custom search engine, you need to set the CustomSearchId and ApiKey connection properties.
To obtain the CustomSearchId property, sign into Google Custom Search Engine and create a new search engine.
To obtain the ApiKey property, you must enable the Custom Search API in the Google API Console.
π Configuring a Source connection (Salesforce is shown).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.To replicate an entire table, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Google Search tables you wish to replicate into SQLite, and click Add Tasks again.
π Choose the account table to replicate (Salesforce is shown).The statement below caches and incrementally updates a table of Google Search results:
REPLICATE VideoSearch;
You can specify a file containing the replication queries you want to use to update a particular database. Separate the replication statements with semicolons. The following options are useful when replicating multiple Google Search accounts into the same database:
Use a different table prefix in the REPLICATE SELECT statement:
REPLICATE PROD_VideoSearch SELECT * FROM VideoSearch;
Alternatively, use a different schema:
REPLICATE PROD.VideoSearch SELECT * FROM VideoSearch;
Select the Overview tab in the Job, and click Configure under Schedule. You can schedule a job to run automatically by configuring it to run at 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 Google Search results to disparate on-premises, cloud-based, and other databases.
Once all the required configurations are made for the job, select the Google Search table you wish to replicate and click Run. After the replication completes successfully, a notification appears, showing the time taken to run the job and the number of rows replicated.
π Run the job.Now that you've seen how to replicate and configure multiple jobs to manage the replication of your Google Search results to various on-premises, cloud-based, and other databases, visit our CData Sync page to learn more and download a free 30-day trial. Start consolidating your enterprise data today!
As always, our world-class Support Team is ready to answer any questions you may have.
Learn more or sign up for a free trial:
CData Sync