March 14, 2003 at 11:24 am
I am replicating data from production server to other servers (transactional repl) with dedicated distributor. During
maintenance period, run out of transaction log (60 GB).
I remember in SQL 7.0 you have to stop log reader agent then backup and truncate transaction log, back up the
distribution database, then restart the log reader.
But how do you do it in SQL 2000.
What is the command to start or stop the log reader
through command prompt?
Is this recommended method in SQL 2000 or there are other
suggestions.
March 15, 2003 at 5:47 am
I've found the easiest way to stop the logreader is to find the name of the job and use sp_stop_job. I cheat and don't worry about being able to recover both db and distribution db, I run backups of each of course, but it's (to me) far less hassle to just resnapshot if we get out of sync because I have about 200 db's replicating. Have you read "Strategies for Backing Up and Restoring Transactional Replication" in BOL?
Andy
March 28, 2003 at 6:54 am
To avoind stoping and then restarting the log reader to keep sincronization, sql has the option 'sync with backup' , that you can specify it with the sp sp_replicationdboption.
This option keep sincronized the two db, and you can backup both db, the published and the distribution, with risk of loosing sincro.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply