Disaster Recovery - Failing over and back - Losing publications

Hello,
I am wondering what I am doing wrong or if what I am seeing is normal
behavior.
I have manual log shipping in place (via SQL LiteSpeed).
We have a replicated database log shipped to a DR server in another
location. When I fail over to the DR site, I can still see the publications
on both sites (however the DR site is not set up for replication). When I
fail back to the main site, I lose replication for the database and all of
my agents fail upon restarting them.
Has anyone run into this and come up with a solution?
We have to fail over to the DR site next weekend for building maintenance
and I don't want to have to rebuild replication.
Thanks so much.
~lb
You might want to restore your databases with the keep replication switch.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Lonnye Blake Bower" <lbower@.excellerx.com> wrote in message
news:eZclO86MFHA.4092@.tk2msftngp13.phx.gbl...
> Hello,
> I am wondering what I am doing wrong or if what I am seeing is normal
> behavior.
> I have manual log shipping in place (via SQL LiteSpeed).
> We have a replicated database log shipped to a DR server in another
> location. When I fail over to the DR site, I can still see the
publications
> on both sites (however the DR site is not set up for replication). When I
> fail back to the main site, I lose replication for the database and all of
> my agents fail upon restarting them.
> Has anyone run into this and come up with a solution?
> We have to fail over to the DR site next weekend for building maintenance
> and I don't want to have to rebuild replication.
> Thanks so much.
> ~lb
>

Disabling triggers not involved in replication in SQL 2000

I am experimenting with replication and recently set up a prototype
transactional replication with about a dozen publications and perhaps twice
as many articles. All has gone smoothly so far. One item that is causing
much gnashing of teeth is the fact that I cannot disable a pre-existing
trigger that has nothing to do with the replication.
Msg 4929, Level 16, State 2, Line 1
Cannot alter the table 'XXXXX' because it is being published for replication.
Any help greatly appreciated.
Craig
Craig,
you won't be able to do this sort of statement: "alter table suppliers
disable trigger all" but you can issue an alter trigger statement. If there
are only a few triggers this might be practical for you.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)