Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jpotucek
Constraint Violating Yak Guru
273 Posts |
 Posted - 2008-03-27 : 09:45:36
|
| We have Transactional replication running from ONE DB on our sql server 2000 box to a SQL Server off our network. While DR testing is going on, the Tunnel to the subscriber server will be down (FOR A COUPLE OF DAYS) What is the best way to pause replication so I don't have a problem with logs filling up etc...I stopped the log reader on the publisher... but I don't know if that was the right thing to do????? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-27 : 16:21:29
|
| Disabling the job will just queue up the data in the publisher's tlog. So you'll need to drop replication to avoid this.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
jpotucek
Constraint Violating Yak Guru
273 Posts |
Posted - 2008-03-31 : 11:09:30
|
| understood. so what would you go in the case where the tunnel to the subscriber server is down for 3 days? Someone told me to disable the distribution agents and the distribution cleanup job and let the distribution DB on the publisher queue everything until the tunnel is back up and the subscriber DB is available again.. Is that the wrong thing to do? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-31 : 12:51:05
|
| If you've got enough disk space on the drive where the publisher's tlog is located, then it would probably be fine. But who knows how much space it is going to need over 3 days.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
Pausing Traqnsactional Replication