![]() |
VOOZH | about |
Always-on applications rely on automatic failover capabilities and real-time access to data. CData Sync integrates live GitLab data into your mirrored databases, always-on cloud databases, and other databases such as your reporting server: Automatically synchronize with remote GitLab data from Windows.
Using CData Sync, you can replicate data from GitLab 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 GitLab from the Connections tab. To add a connection to your GitLab account, navigate to the Connections tab.
Set the ProfileSettings connection property to the connection string for GitLab (see below).
Create a Personal Access Token in GitLab under User Settings > Access Tokens, selecting the required scopes (e.g.,
read_api,
api). π 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 GitLab 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 GitLab data:
REPLICATE AccessRequests;
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 GitLab accounts into the same database:
Use a different table prefix in the REPLICATE SELECT statement:
REPLICATE PROD_AccessRequests SELECT * FROM AccessRequests;
Alternatively, use a different schema:
REPLICATE PROD.AccessRequests SELECT * FROM AccessRequests;
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 GitLab data to disparate on-premises, cloud-based, and other databases.
Once all the required configurations are made for the job, select the GitLab 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 GitLab data 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