SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Replication Statement Delivery Options - Part 2


Replication Statement Delivery Options - Part 2

Author
Message
msuarez
msuarez
SSC-Enthusiastic
SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)SSC-Enthusiastic (102 reputation)

Group: General Forum Members
Points: 102 Visits: 70
Even though this was more or less out of curiousity, I finally got my answer last week at the SQL Pass Conference in Seattle.

I sat down with an actual developer of Transactional Replication at the "Meet the Experts Lounge". I had a list of questions for him and this was one of them.

As Simon points out, these stored procedures are meant to assist the snapshot process in transactional replication. Basically, while a snapshot of the database is being taken, new transactions are also occuring. While the snapshot is being captured, some transactions may make it into the snapshot and some may not. Therefore, all of the new transactions that occur from the beginning of the snapshot to the end are applied using these procedures. So the insert proc updates the row if it already exists, or it inserts it. The delete proc issues the delete without concern as to whether any rows were affected. The ccs stands for concurrent snapshot.

Simon is correct that these are supposed to be temporary. Mine stick around for some reason. The developer wasnt sure why. But needless to say, my curiousity has been satisfied.

-Mike
kahar
kahar
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 25
Can anyone tell me whether Statement delivery option can be set for Transactional Replication with Updatable Subscription? In our case, we don't want to take any action if there is any Update to one of our tables.

Thanks,
Irina
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search