May 22, 2012 at 8:04 am
Is it possible to automate an occassional copy of database tables with a datestamp against each row, then perhaps a week later to add any changed rows with a new datestamp against it? So over time a single database with the same tables as the original will also contain dated changes.
The idea is to keep a record of changes with as little overheads as possible, and that current reports could use the new database with minimal changes.
I have read up on CDC and snapshots but not sure how to achieve a single database with minimal overhead.
[Follow up] Sorry to push this up again, but if there is any more information needed please let me know. I'm not looking for a complete solution - just some pointers in the right direction.
May 23, 2012 at 11:27 am
You could check out Replication or Snapshots or just INSERT the data from one db to the other (and add the date to the SELECT list).
Or you could look at SSIS & Slowly Changing Dimensions.
The possibilities are endless with SQL Server. It just depends on how you want to get it done. As far as low overhead, that depends on your setup.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply