Question : Replicating SQL 2005 Database

Hi Experts,

I would like to think through what is involved in Replicating a database in SQL 2005 SP2 from one server to another in an AD environment. The reason for the move would be to use the replicated database for Reporting purposes as well as running large queries on a non-production environment with almost real time data. The machines will be on the same subnet in the same location. Questions that I have are:

1. Will hardware need to be identical? We plan on getting a beefier box for the replicated environment
2. What kind of accounts are needed for the replication in the publisher and subscriber? AD or SQL based?
3. We do not plan on using a distributor since there is just one publisher and one subscriber, is there anything wrong with this?
4. What kind of networking issues should I be looking out for? Congestion? QoS?
5. We plan on replicating the environment nightly, if we were planning to replicate it more than once are there any other changes to the job that I will need to make?
6. What are some of the other issues you Experts have run into regarding SQL 2005 Replication?

Thanks,

Abhi

Answer : Replicating SQL 2005 Database

1. Will hardware need to be identical? We plan on getting a beefier box for the replicated environment
No...its not like a cluster.  Pick the hardware necessary to meet your reporting needs.

2. What kind of accounts are needed for the replication in the publisher and subscriber? AD or SQL based?
I would impersonate the SQL service accounts..which is likely an AD account.  Make sure the accounts are on both systems.  It is how I do it and it works great...although I am not sure MS recommends it.  Otherwise, you can just use a SQL account.  Either should work fine as long as they have the necessary permissions on both systems.

3. We do not plan on using a distributor since there is just one publisher and one subscriber, is there anything wrong with this?  You have to use a distributor (the database)...its required.  You can, however, just put it on one of the machines you already have.

4. What kind of networking issues should I be looking out for? Congestion? QoS?  You're going to have a little more data going over the pipe...consider having a dedicated fiber between your production server and your reporting server.

5. We plan on replicating the environment nightly, if we were planning to replicate it more than once are there any other changes to the job that I will need to make?  Its just a SQL Agent job, so you can schedule it has you'd like.

6. What are some of the other issues you Experts have run into regarding SQL 2005 Replication? 2000 replication was finicky, but it seems 2005 is much much better.  Just make sure your subscriptions dont' expire on you...and make sure you always have a good script of the publications in case you need to port them.  Make sure you test them out.  Also, the replication monitor in 2005 is a GREAT tool...make sure you use the tracer tokens to your advantage.