Post reply

Ideas or Strategies for incremental data pull not using Change Tracking

  • March 28, 2017 at 11:53 am

    #401860

    Hello All,
    We currently use Change Tracking for our T-SQL customers, however we are now getting quotes for customers with Oracle, MySQL and T-SQL customers on compatibility level 80.

    What are some different strategies and techniques for pulling incremental data when Change Tracking is not available? Our team has had suggestions on everything from replication to another copy db on the source site and pulling from that, or creating custom tables to store changes using triggers. Just trying to see what others use.

    Thanks !

    ***SQL born on date Spring 2013:-)

  • March 28, 2017 at 11:59 am

    #1935350

    So, this would be a scenario where you need to merge from a source table to a target table, but the source database is non-SQL Server? On the source table, is there a column containing something like a date/time stamp or sequential GUID identifier that gets auto-updated whenever a new row is inserted or updated?

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • March 28, 2017 at 12:10 pm

    #1935356

    Eric M Russell - Tuesday, March 28, 2017 11:59 AM

    So, this would be a scenario where you need to merge from a source table to a target table, but the source database is non-SQL Server? On the source table, is there a column containing something like a date/time stamp or sequential GUID identifier that gets auto-updated whenever a new row is inserted or updated?

    The best we have is on some of the source tables we have PK's and Last Modified dates. But not always. We had a meeting about this and all of us were scratching our heads of a all in one solution. The issue with one of the customers is its a t-sql db but vendors system has a compatibility level of  80 even though they are using SQL Server 2012. So no change tracking.

    We are trying to find a solution that will work against all 3 scenarios but we may have to do something different for each one.

    ***SQL born on date Spring 2013:-)

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply