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

Enabling CDC on each table causes SQL Server to read the transaction log and record all DML changes (inserts, updates, deletes) into dedicated change tables. This provides a reliable, low-overhead audit trail of exactly what changed and when, making it ideal for incremental ETL loads from a financial database.

SQL Server database mirroring is a high-availability feature that replicates an entire database to a secondary server; it does not expose or capture row-level change data for consumption.

A full extract copies all rows every time and cannot distinguish changed rows from unchanged rows, making incremental change identification impossible.

Log shipping copies transaction log backups to a secondary server for disaster recovery and does not provide a queryable change data feed.

AlwaysOn Availability Groups synchronize entire databases for high availability and readable secondaries; they do not track or surface individual row changes for ETL processing.