Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Automated Continuous Sage 300 Replication to Google BigQuery
Use CData Sync for automated, continuous, customizable Sage 300 replication to Google BigQuery.
Always-on applications rely on automatic failover capabilities and real-time data access. CData Sync integrates live Sage 300 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 Sage 300 data to Google BigQuery. To add a replication destination, navigate to the Connections tab.
- Click Add Connection.
- Select the Destinations tab and locate the Google BigQuery connector.
- Click the Configure Connection icon at the end of that row to open the New Connection page. If the Configure Connection icon is not available, click the Download Connector icon to install the Google BigQuery connector. For more information about installing new connectors, see Connections in the Help documentation.
- After the connected is added, enter the necessary connection properties. To connect to Google BigQuery, use OAuth authentication::
- Connection Name: Enter a connection name of your choice.
- Auth Scheme: Select OAuth. Sync supports the OAuth, OAuthJWT, GCPInstanceAccount, and AWSWorkloadIdentity authentication methods.
- ProjectId: Enter the ID of the project you want to connect to.
- DatasetId: Enter the ID of the dataset you want to connect to.
- Insert Mode: Set it to Upload. The different Insert Modes available in Sync are Streaming, DML, Upload, and GCSStaging.
- Click Connect to Google BigQuery. Log in using your Gmail credentials to grant permissions to CData Sync. CData Sync completes the OAuth process and connects successfully to Google BigQuery.
- Once connected, click Save & Test to save the connection.

You are now connected to Google BigQuery 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.

In this article, we will demonstrate how to load Sage 300 data into Google BigQuery and utilize it as a destination.
Configure the Sage 300 Connection
You can configure a connection to Sage 300 from the Connections tab. To add a connection to your Sage 300 account, navigate to the Connections tab.
- Click Add Connection.
- Select a source (Sage 300).
- Configure the connection properties.
Sage 300 requires some initial setup in order to communicate over the Sage 300 Web API.
- Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the
option under Security Groups (per each module required). - Edit both web.config files in the /Online/Web and /Online/WebApi folders; change the key AllowWebApiAccessForAdmin to true. Restart the webAPI app-pool for the settings to take.
- Once the user access is configured, click https://server/Sage300WebApi/ to ensure access to the web API.
Authenticate to Sage 300 using Basic authentication.
Connect Using Basic Authentication
You must provide values for the following properties to successfully authenticate to Sage 300. Note that the provider reuses the session opened by Sage 300 using cookies. This means that your credentials are used only on the first request to open the session. After that, cookies returned from Sage 300 are used for authentication.
- Url: Set this to the url of the server hosting Sage 300. Construct a URL for the Sage 300 Web API as follows: {protocol}://{host-application-path}/v{version}/{tenant}/ For example, http://localhost/Sage300WebApi/v1.0/-/.
- User: Set this to the username of your account.
- Password: Set this to the password of your account.
- Set up the security groups for the Sage 300 user. Give the Sage 300 user access to the
- Click Connect to Sage 300 to ensure that the connection is configured properly.
- Click Save & Test to save the 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, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Sage 300 tables you wish to replicate into Google BigQuery, and click Add Tasks again.

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 with the help of SQL queries.
Schedule Your Replication
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.

Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Sage 300 data to Google BigQuery.
Run the Replication Job
Once all the required configurations are made for the job, select the Sage 300 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.

Free Trial & More Information
Now that you have seen how to replicate Sage 300 data into Google BigQuery, visit our CData Sync page to explore more about CData Sync 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.