Hi,

I'm new to replication and I would like to know on failover, how to bring the standby server to primary server. I also heard that it would be wise to choose replication only when i want to use it as a reporting server/Decison support system because the replication doesnt have capability to replicate all objects from the primary.
I think, should opt for choosing the log shipping for the disaster recovery scenario because replication has partial data in the standby server.

Basically I want to get clear on two things.
1. Steps for bring the standby server to Primary
2. What are the objects/articles available for replication

Am i talking in the right sense?. Please help me.

Thanks,
Chandra

__________________
Thanks,
Chandra

It is good to use replication on a reporting server cause then you don't have the load of running reports on a production server. Some large reports can really tie up resources.

When you use log shipping you will have to manually bring the secondary server online.

With database mirroring, no human intervention is required especially if you are using a .NET application since you can specify the mirror servers in .NET so that if it can't find data from the primary it will try the secondary database connections. A drawback with mirroring is that you need to set up a 3rd instance of SQL to monitor the mirroring.

I have set up replication in the past for four office locations and each separate location using the replicated databases. It's good if you don't need to change the schema of the database because it can become quite complicated to make changes to the database itself since those changes aren't going to replicate.