September 13, 2006 at 2:20 am
Hello,
I am trying to set up a replication from a SQL server 7.0, Enterprise Edition, Service pack 4, which will act as publisher and distributor, to a SQL server 2005, Standard Edition subsciber. It just won't let me do it.
- When I try to register the 2005 server from the 7.0, it says "To connect to this server you must use SQL Server Management Studio".
- Instead I try to add a new subscription from the 2005 server. Now I get the message "This SQL Server version (7.0) is not supported"
I have read the article "Using Multiple Versions of SQL Server in a Replication Topology" in Books Online, and as far as I can see, setting up the replication this way should not be a problem. Am a missing something lika a compatibility setting?
Can anyone point me in the right direction please? Thanks a lot,
/John
September 14, 2006 at 7:51 am
it has something to do with the fact that SQL 7.0 doesn't know what the management studio is.
Look in that direction i would say.
Good luck
JV
September 14, 2006 at 7:53 am
September 18, 2006 at 2:07 am
Thank you. That's one of the articles I already read. Since the 7.0 server soon will be upgraded to SQL server 2000, I will use DTS for now and give it another try when the upgrade is done. However, another post on this forum tells me that there are a few issues to work around there too.
Thanks anyway!
September 18, 2006 at 3:59 am
yes u r correct indeed. There still some issues concerning dtsx packages. There is already a big difference if u r using x64 or x86.
The other issue is the secutiry issue that microsoft handles in dtsx. It is complicated.
Scheduling dtsx has the same security issue
Nevertheless good luck.
JV
September 18, 2006 at 7:36 am
I dont have a SQL 7 install to test with, but even without BOL I would expect it to work - the biggest change it makes to the subscriber is installing replication stored procs for each table/article, and the 7.0 syntax would work fine.
I'd suggest a call to MS rather than invest time in DTS. If it can be done you're ahead of the game and if not, you at least know that the investment in DTS is required.
September 25, 2006 at 7:04 am
Andy,
Setting up a DTS package on the 7.0 server which loads data onto the 2005 server didn't give me any problems at all. I have to live with this solution for now and try the replication approach again once the 7.0 server is upgraded to SQL server 2000.
Other threads on this forum tells me that setting up the replication using the IDE can be a problem there as well, but I read that people have managed to set up the replication between 2000 and 2005 using T-sql statements, so I'll try that instead.
Thanks for your help.
September 25, 2006 at 3:21 pm
Glad you got a solution in place. The upgrade to SQL2K is fairly painless and well worth doing. Compatability mode covers most of the issues you might run into.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply