Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Non-Continous Replicaton and The LogReader Expand / Collapse
Author
Message
Posted Monday, March 25, 2002 12:00 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Yesterday @ 11:35 AM
Points: 7,003, Visits: 2,408
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

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #3225
Posted Thursday, March 28, 2002 9:58 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 9:51 AM
Points: 3,122, Visits: 2,367
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.






LinkedIn Profile

Newbie on www.simple-talk.com
Post #30535
Posted Thursday, March 28, 2002 12:32 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Yesterday @ 11:35 AM
Points: 7,003, Visits: 2,408
Interesting! I will take a look at that, could be useful.


Andy


Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #30536
Posted Thursday, December 11, 2003 9:26 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 3:25 AM
Points: 1,222, Visits: 118
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




Post #30537
Posted Thursday, December 11, 2003 1:14 PM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: Moderators
Last Login: Yesterday @ 11:35 AM
Points: 7,003, Visits: 2,408
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
http://www.sqlservercentral.com/columnists/awarren/




Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter
Post #30538
Posted Thursday, November 19, 2015 5:42 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Monday, February 1, 2016 8:09 AM
Points: 34, Visits: 255
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.


  Post Attachments 
logread_manual_run.jpg (1 view, 131.41 KB)
Post #1738130
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse