Skip to main content
Artie reads changes from SQL Server in one of three ways. Pick one per pipeline in Source > Replication method.

Capture instances

Reads SQL Server CDC change tables. The default method.

Change tracking

Reads SQL Server change tracking, then the current row.

Transaction log backups

Reads your .trn log backup files instead of the database.

​
Compare the methods

​
Which method to use

  • Use capture instances when every change matters, for example financial or audit data. It captures each insert, update and delete with before and after values, through an interface Microsoft supports.
  • Use transaction log backups when you can’t add load to the production database. You already take log backups for recovery, and Artie reads those files. This method is in early access.
  • Use change tracking only when you can’t enable CDC. It tells Artie which rows changed, not how they changed. If a row is updated three times between polls, the destination gets only the last version.
All three methods deliver changes at least once and never skip a change because Artie restarted. See Delivery guarantees. For Always On availability groups, see High availability and failover.

​
Advanced

Artie can unify tables across multiple databases into a single destination table to support single tenant databases.
  1. In the Source tab, click Enable unifying tables across databases and select the databases to unify.
  2. In the Tables tab, select the tables to unify.
  3. If your primary key isn’t globally unique, you can include the full source table name (dbName.schemaName.tableName) in the primary key.