November 26, 2009 at 3:48 am
Hello all,
We have an sql 2000 instance which is our main production server.
We are wanting to upgrade to 2005. Which has been installed onto a new server.
What I want to do is replicate from 2000 to 2005 between the servers. We can then start to point peoples apps at the 2005 instance. Once all have been done we can lose the 2000 insatance, but any changes made on either instance need to be replicated real time to ensure integrity.
Is this possible?
I'm a complete noob to this and any direction would be much appreciated.
Many Thanks
November 26, 2009 at 6:05 am
Merge should be possible in your scenario. Check in Books Online for Merge replication.
-Roy
November 26, 2009 at 6:41 am
Roy Ernest (11/26/2009)
Merge should be possible in your scenario. Check in Books Online for Merge replication.
I didn't think Merge replication was possible in realtime... is it?
If you have your SQL 2005 instance already built, why don't you want to switch everything in one go... switching is (almost) as simple as detaching the database from your SQL 2000 machine, copying the files to the 2005 machine and then attaching them.
November 26, 2009 at 8:15 am
Ian, I am not sure about it. Merge replication is my weakest point in Replication. I have never done it. You have a good point
-Roy
November 26, 2009 at 10:10 am
Ian has a good point.
The problem the OP is trying to solve is an upgrade from SQL 2000 to 2005. The OP has a concern that the data has to be in sync when the new servers are ready to go.
The solution for this depends on the upgrade plan.
Once the application and other data dependent components are tested, the data can be brought from SQL 2000 to using attach/detach, backup/recovery, copy database etc.
The OP was thinking replication might to solve the problem. When there is an upgrade performed, there is a planned downtime during which you can move the data using Ian's suggestion or other ways as desired.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
November 26, 2009 at 11:41 am
Actually I like the idea of replication. But instead of an updatable replication topology, it could be a Non updatable transactional replication. Once it is time to pull the plug, reset the identity seed and then pull the plug.
The other way is to take Back up and restore.(Or make 2005 a warm standby by using transaction log shipping) Both will have a higher down time than the replication method.
-Roy
November 26, 2009 at 8:47 pm
FYI : Merge Replication is not real time. From memory, it is every 2 minutes. You can change this if you need.
The architecture of Merge Replication is quite different to transactional replication. I would not recommend changes the time between syncronisation without some testing since it may have impact on the performance of each server.
November 27, 2009 at 2:20 am
Hi all,
I have the same problem with replication. I have one server is using SQL server 2000 (S1) and the other is using SQL server 2005 (S2). Both of them are running and I want to replication from S1 to S2. But I always have problem when do replication, I do not know why. Can you help me?
Thanks so much!
November 27, 2009 at 5:44 am
hoanguyen268 (11/27/2009)
Hi all,I have the same problem with replication. I have one server is using SQL server 2000 (S1) and the other is using SQL server 2005 (S2). Both of them are running and I want to replication from S1 to S2. But I always have problem when do replication, I do not know why. Can you help me?
Thanks so much!
What are the errors you get? With out which it is difficult to guess.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply