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?

  1. create database snapshot temporary use.
  2. get change tracking current version of production database.
  3. compare previous successful run version.
  4. extract database snapshot instead of production database.
  5. after successful load, drop database snapshot.

we're using 2008 r2 enterprise edition. there downside this? missing something?


Comments

Popular posts from this blog

php - Submit Form Data without Reloading page -

linux - Rails running on virtual machine in Windows -

php - $params->set Array between square bracket -