September 24, 2017 at 10:15 am
Hello All,
We currently are using Change Tracking for our current customers. It is working well. However, we are about to take on another EHR application that has a compatibility level of SQL 2000. How can we capture incremental changes without using Change Tracking. We had discussed custom tables and using triggers to capture the changes, but our dev team is concerned about overhead to the customers system.
Is there other options for tracking changes ?
Thanks in advance,
Thomas
***SQL born on date Spring 2013:-)
September 25, 2017 at 8:37 am
Hi Thomas
An approach I've taken to this in the past is to detect changes by comparing staged warehouse data against full source tables at every extract, with updates only written to staging if a difference between source and staging is found. This still requires all source records to be inspected every time, but flagging changed records in staging allows downstream processing to continue on a changes-only basis.
We got away with this because we were in the specific situation of integrating data from lots of small source systems rather than a few very large ones -- so the cost of an individual table compare was acceptable and many different sources were staged in parallel. If this is your situation then this approach might be of use (but I'm aware that it's an unusual scenario!).
Richard
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply