You need to identify changes in the financial database. What should you do?

SQL Server replication is designed to distribute data to subscribers, not to identify or record row-level changes for auditing purposes.

Extracting data from the current partition only retrieves existing rows and cannot identify what has changed since the last extract.

A timestamp column can show when a row was last modified but cannot capture deletes or track which specific columns changed.

A full extract retrieves all data on every run and requires a separate comparison process to detect changes, making it inefficient and unreliable for change identification.

Enabling Change Data Capture on each table causes SQL Server to read the transaction log and record all DML changes (inserts, updates, deletes) into a corresponding change table. This provides a reliable, low-overhead mechanism to identify exactly what changed, when, and the before/after values - precisely what financial auditing requires.