March 9, 2009 at 2:23 pm
I am looking to Replicatie tables from my production server to a remote server . Production is running sql 2000 and remote is running 2005. Replication monitor and publisher are configured on sql 2000 and I would like to push a subscription to 2005 holding my static tables. Everything is working but my connection to the 2005 box. It keeps failing when trying to register it. Can any help or point me to some good documentation. That would be great this is kind of critical. Thanks
March 9, 2009 at 9:23 pm
You cannot connect to a SQL 2005 instance using Enterprise Manager.
Normally, I would have the distributor as the server with the highest edition/Service pack level. This means that in your environment, the distributor would need to be the other server.
I haven't needed to replicate from SQL 2000 to SQL 2005 but it is possible. I would start again but with everything configured using Management Studio instead.
March 10, 2009 at 8:50 am
The 2005 machine has nothing on it we wanted to push our production to it. So I can conntect to 2000 from 2005 then? Do you have any good references ?
March 11, 2009 at 2:46 am
Read this article about "Using Multiple Versions of SQL Server in a Replication Topology":
http://msdn.microsoft.com/en-us/library/ms143241(SQL.90).aspx
There are scenarios where it works but it will not work for merge replication.
I made this experience myself!:crying:
Anyway, for your scenario (static tables --> Snapshot) you should be able to setup the replication. As you experienced yourself, you cannot register the 2K5 instance with Enterprise Manager but you don't need to. Just add your 2K5 server as a subscriber to the database you like to replicate and you are done.
Hope this helps!
Cheers Rene
March 11, 2009 at 10:33 am
The 2005 machine is a remote server I have created the subscription and it keeps failing. It acts like it is not seeing the 2005 machine. Do I create the subscription on the 2000 abd push it to the 2005 or create it on the 2005 and pull it. I created a failed registration on my 2000 box per an artical from this site and it still cannont see the 2005. I created the database I want to push to on the 2005. How do I get my 2000 sever to see the 2005 , this appears to be my snag...
I have also read that you may be able to load 2005 on my current 2000 server and try and register my remote server that way.? This issue is getting tiresome... thanks for your hlep.
March 11, 2009 at 12:08 pm
Is there any error message you can post? Can you see any message on the remote server? Check the event log. Is the distribution agent allowed to access the 2K5 server?
Do I create the subscription on the 2000 abd push it to the 2005 or create it on the 2005 and pull it.
Well, you have different possibilities:
1. You can use the 2K0 server as distributer and push the data to 2K5 (replication agent running on 2K0 server)
2. You can use the 2K0 server as distributer and pull the data from 2K5 (replication agent running on 2K5 server)
Have you used the SQL Server Management Studio or did you try it with the Enterprise Manager?
Configure the replication with SSMS!
Keep up!
Cheers René;)
March 11, 2009 at 4:20 pm
I currently have distribution , and publisher setup on my 2000 machine.
I tried creating a push subscription vio 2000 EPM and the 2005 Studio
I currently trying to run everything through the 2005 SMS with the distributor and publisher running on the 2000 server.
In creating the substription do I want to ran all agents at Distributor 2000 or run at each agent its subscriber pull ? Eather way when I try and add the report server holding 2005 I getr the following error
Sql server replication requires the actual server name to make a connection to the server. In the SMS I used temp.testing.com and it conntected.
what all do I have to have running on my 2005 machine. My hope was to only have it be a subscriber.
March 12, 2009 at 2:22 am
Sql server replication requires the actual server name to make a connection to the server.
You can run everything on the 2K0 server and 2K5 is just a subscriber. This is absolutely no problem. I think the problem is really the connection between the two servers.
Have you checked the message with Google?
Check this link. Do you have a similar setup (server outside your network)?
:unsure:
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply