Quantcast
Channel: SQL Server Database Engine forum
Viewing all articles
Browse latest Browse all 12963

Change Tracking many tables

$
0
0

Hi,

I have a number of tables that are all related in some way or another. Lets say there are 20 tables in total here. I need to track changes as they all ultimately will need their changes sending to some other remote database.

Is it ok for me to use just a single change version, obtained at the beginning of my synchronisation code, within a SNAPSHOT transaction for every table I'm concerned about?

I would also need to validate the change version used before getting changes for each table using CHANGE_TRACKING_MIN_VALID_VERSION wouldn't I?

Once I have obtained all the changes for the 20 tables, then I would commit my transaction.

Regards


Viewing all articles
Browse latest Browse all 12963

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>