![]() |
VOOZH | about |
Always-on applications rely on automatic failover capabilities and real-time access to data. CData Sync for AlloyDB integrates live AlloyDB data into your mirrored databases, always-on cloud databases, and other databases such as your reporting server: Automatically synchronize with remote AlloyDB data from Windows or any machine running Java.
You can use Sync's command-line interface (CLI) to easily control almost all aspects of the replication. You can use the CLI to replicate AlloyDB data to one or many databases without any need to change your configuration.
You can save connection strings and other settings like email notifications in XML configuration files.
The following example shows how to replicate to SQLite.
<?xml version="1.0" encoding="UTF-8" ?> <CDataSync><DatabaseType>SQLite</DatabaseType> <DatabaseProvider>System.Data.SQLite</DatabaseProvider> <ConnectionString>User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432</ConnectionString> <ReplicateAll>False</ReplicateAll> <NotificationUserName></NotificationUserName> <DatabaseConnectionString>Data Source=C:\my.db</DatabaseConnectionString> <TaskSchedulerStartTime>09:51</TaskSchedulerStartTime> <TaskSchedulerInterval>Never</TaskSchedulerInterval> </CDataSync>
<?xml version="1.0" encoding="UTF-8" ?> <CDataSync><DatabaseType>SQLite</DatabaseType><DatabaseProvider>org.sqlite.JDBC</DatabaseProvider> <ConnectionString>User=alloydb;Password=admin;Database=alloydb;Server=127.0.0.1;Port=5432</ConnectionString> <ReplicateAll>False</ReplicateAll> <NotificationUserName></NotificationUserName> <DatabaseConnectionString>Data Source=C:\my.db</DatabaseConnectionString> </CDataSync>
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
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.
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.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
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.
Sync enables you to control replication with standard SQL. The REPLICATE statement is a high-level command that caches and maintains a table in your database. You can define any SELECT query supported by the AlloyDB API. The statement below caches and incrementally updates a table of AlloyDB data:
REPLICATE Orders;
You can specify a file containing the replication queries. This enables you to use the same replication queries to replicate to several databases.
After you have configured the connection strings and replication queries, you can run Sync with the following command-line options:
AlloyDBSync.exe -g MySQLiteConfig.xml -f AlloyDBSync.sql
java -Xbootclasspath/p:c:\sqlitejdbc.jar -jar AlloyDBSync.jar -g MySQLiteConfig.xml -f AlloyDBSync.sql
Learn more or sign up for a free trial:
CData Sync