March 25, 2002 at 12:00 am
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/awarren/noncontinousreplicatonandthelogreader.asp>http://www.sqlservercentral.com/columnists/awarren/noncontinousreplicatonandthelogreader.asp
March 28, 2002 at 9:58 am
Years ago I was told that Microsoft set up a Publisher on one side of the Atlantic and the Distributor/Subscriber at the other.
When they got their first phone bill it was rather high because the only communication you could control was between the distributor and the subscriber.
I have found that occassionaly I have to stop replication (back ups, busy periods etc).
sp_replicationdboption '<<dbname>>','sync with backup' true.
stops the publisher sending any transactions to the distributor unless they have been backed up.
For back up purposes I back up the Distributor, then the publishing database.
Then issue the
sp_replicationdboption '<<dbname>>','sync with backup' false.
to let normal service resume.
March 28, 2002 at 12:32 pm
Interesting! I will take a look at that, could be useful.
Andy
December 11, 2003 at 9:26 am
Interesting.. This is more of a question than comment (I am not that good to comment). How about writing my own log reader? That would give me more control. Is there any advice you would be able to provide? Thanks
December 11, 2003 at 1:14 pm
Pretty tough I think, it contains a fair bit of code. You'd have to be able to read the transaction log, figure out which subscriptions existed and what changes should be captured based on those (plus any filters).
Andy
November 19, 2015 at 5:42 am
thanks for idea, Andy!
I have the almost same task to set Transactional replication non continuous.
It turned out that logread.exe doesn't require Ctrl+C command at least in SQL2008R2.
So, I've just removed "-Countinuous" from "Run agent." job step and changed its schedule.
Regards,
Andrey.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply