October 11, 2003 at 1:44 am
I have been using merge replication with 1 distributor and some pubs and subs.
the merge agent runs every 15 mins
In this scenario the agent ran @ 10.00 and
@ 10.05 col1 of row1 was updated
@ 10.10 col2 of row1 was updated.
when the agent runs @10.15 these two transactions come to the distributor as one transaction with col1 of row1 and col2 of row1 updated.
Is there a way to configure merge agent so that it treats all the updates separately.
October 14, 2003 at 8:00 am
This was removed by the editor as SPAM
October 16, 2003 at 6:37 pm
I don't know of anyway to do that. Why do you need it to be separated?
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
Gary Johnson
Microsoft Natural Language Group
DBA, Sr. DB Engineer
This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed in this post are my own and may not reflect that of my employer.
October 17, 2003 at 1:22 am
I have multiple subscribers and maintain the history with triggers at the distributor. to avoid unnecessary history trigger load on the production servers.
In this scenario, i am not getting all the history within 1 replication batch.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply