log shipping error with replication | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

log shipping error with replication

I have a production server set up with log shipping to warm spare and it worked for years. Now I need set up transactional replication to a seperate server. The log shipping stops working properly. I either got (loading) database status on warm spare even after the log restored or the transaction won’t be restored on warm spare. I tried to set up logshippng on top of replication and replication on top of logshipping. Here is what I have done for logshipping on top of replication. 1. set up replicaton.
2. use sp_replicatoindboption to set synch with backup option
3. set up logshipping Is there anything I missed? Thanks for your advice.
By default when you restore a database all replication is removed from the db. So normally under log shipping you have to set it up again. There is a way around this with MS log shipping, however you have to rename the standby server to the same name as the old primary when you failover – this usually isn’t possible (and is a nightmare for testing). To find out more about this look in books online under Log Shipping | Transactional Replication. Simon
http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1109150,00.html too fyi. Satya SKJ
Contributing Editor & Forums Moderator
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.