Delta-snapshot replication from SQL Server #
Delta-snapshot is a recurring snapshot replication. In delta-snapshot, Replicant replicates the delta (difference) of the records that have been inserted or updated since the previous delta-snapshot iteration. Replicant uses the delta-snapshot key column and the recovery table to identify the set of delta records that have changed since the previous delta-snapshot iteration. The change can result from insert, update, or delete operations.
You can enable delta-snapshot replication by running Replicant with the
delta-snapshot option. For more information, see Replicant delta-snapshot mode.
Follow the steps in the following sections to set up SQL Server for
delta-snapshot mode replication. In these steps,
$REPLICANT_HOME refers to your Arcion Self-hosted CLI download directory.
I. Required Permissions #
To allow replication, you need to first verify that the necessary permissions are in place on source SQL Server. For more information, see SQL Server User Permissions.
II. Set up connection configuration #
Specify the connection details of your SQL Server instance to Replicant in one of the following ways:
Using a connection configuration file. #
The connection configuration fild holds the connection details and login credentials.
You can find a sample connection configuration file
sqlserver.yaml in the
$REPLICANT_HOME/conf/conn directory. The following configuration parameters are available:
The connection type representing the database. In this case, it’s
The hostname of your SQL Server system.
The port number to connect to the
The username credential to access the SQL Server system.
The password associated with
The authentication protocol for the connection. The following protocols are supported:
Default authentication protocol is always
NATIVE if you don’t explicitly set the
In case of
NLTM protocol, provide the
DOMAIN\USER format—for example,
Optional parameter. If you’re hosting SQL Server on Azure, you must set this parameter to
The maximum number of connections Replicant uses to load data into the SQL Server system.
The following is a sample connection configuration:
Use a secrets management service #
You can store your connection credentials in a secrets management service and tell Replicant to retrieve the credentials. For more information, see Secrets management.
Use KeyStore for credentials #
Replicant supports consuming login credentials from a credentials store. Instead of specifying username and password in plain form, you can keep them in a KeyStore and provide the KeyStore details in the connection configuration file like below:
Replace the following:
PATH_TO_KEYSTORE_FILE: The path to your KeyStore file.
PREFIX_OF_THE_KEYSTORE_ENTRY: The prefix of your KeyStore entries. You can create entries in the credential store using a prefix that preceeds each credential alias. For example, you can create KeyStore entries with aliases
sqlserver_password. You can then set
KEYSTORE_PASSWORD: The KeyStore password. This parameter is optional. If you don’t want to specify the KeyStore password here, then you must use the UUID from your license file as the KeyStore password. Remember to keep your license file somewhere safe in order to keep the KeyStore password secure.
III. Set up Extractor configuration #
To configure snapshot replication according to your requirements, specify your configuration in the Extractor configuration file. You can find a sample Extractor configuration file
sqlserver.yaml in the
All configuration parameters for
delta-snapshot mode live under the
delta-snapshot section. The following is a sample configuration:
- catalog: tpch
row-identifier-key: [l_orderkey, l_linenumber]
For more information about the configuration parameters in
delta-snapshot mode, see Snapshot Mode.