Good Morning/Afternoon,
We have a database with merge replication set up for approx 500 subscribers, who each sync via a pull, perhaps 2 or 3 times a day, so approx 1-1.5k syncs per day.
We have a separate requirement to capture changes to feed to a couple of other systems , and CT is being considered.
Has anyone any experience of using CT concurrently with merge replication ? My concerns are that whilst CT is (apparently) a 'lightweight' option, would it contribute to more blocking in the DB during the sync.
Merge rep does seem prone to being 'a bit blocky' when it gets busy, and I am loathe to add another point of contention into the mix.
I have seen it suggested that the changes could be just as easily picked out of the metadata tables (msmerge_contents ...) and I'm curious if anyone is successfully doing that. It does presuppose that you are replicating the tables of interest.
So in summary - does CT sit well with merge replication in terms of transaction overhead and lock contention; is the use of merge metadata tables such as msmerge_contents a viable alternative, or does it have pitfalls I should be aware of.
Thank you all for any advice and experience you can offer.