sql server - SSIS, Change Tracking, and Snapshot Isolation -
i'm using sql server 2008 r2 change tracking (not change data capture) , ssis extract incremental changes several source databases.
until now, i'd been using restored backups didn't need worry snapshot isolation. however, need point these packages @ production databases.
i know setting snapshot isolation level on tracked databases recommended ensure consistency of etl extracts. i'm reluctant because of possible degradation in performance.
since i'm extracting late @ night, there reason can't use following process?
- create database snapshot temporary use.
- get change tracking current version of production database.
- compare previous successful run version.
- extract database snapshot instead of production database.
- after successful load, drop database snapshot.
we're using 2008 r2 enterprise edition. there downside this? missing something?
Comments
Post a Comment