July 11, 2012 at 12:35 pm
I have a client who has several SQL Server 2000 servers running merge replication. According to the following article from MS. A merge subscriber may be any version at or below the publisher
Here’s the MSDN page that talks about version compatibility:
http://msdn.microsoft.com/en-us/library/ms143699
Here are the rules (from that page):
• A Distributor can be any version as long as it is greater than or equal to the Publisher version (in many cases the Distributor is the same instance as the Publisher).
• A Publisher can be any version as long as it less than or equal to the Distributor version.
• Subscriber version depends on the type of publication:
• A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2005 Publisher running can have SQL Server 2012 Subscribers; and a SQL Server 2012 Publisher can have SQL Server 2005 Subscribers.
• A Subscriber to a merge publication can be any version less than or equal to the Publisher version.
Has anyone been able to accomplish this task during testing.
July 11, 2012 at 2:26 pm
A Subscriber to a transactional publication can be any version within two versions of the Publisher version.
2000 is three versions away from 2012.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 11, 2012 at 2:43 pm
Yes, transactional replication is stated in the article as being supported only 2 versions back. However, merge replication is stated as being supported for any version less than or equal to the Publisher/Distributor.
July 11, 2012 at 2:50 pm
Right, transactional replication is not possible from 2012 to 2000. I have seen people add a shim (not official technical term) database in between to facilitate replication between incompatible platforms, but that topology is a mousetrap when replication has issues.
Sorry for misreading...I see now you are only interested in merge. It would not take too terribly long to setup a basic subscription, just to see. Have you tried it and are having an issue? Or are you just exploring?
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
July 11, 2012 at 2:57 pm
I am just exploring as to whether this is actually possible. I have not been able to get it to work. When you setup the subscriber types so that the publisher knows which compatibility to use for which subscriber there is no support for 2000. It was my understanding from Microsoft that all support for SQL Server 2000 was completely removed from all of the tools. This is what I am seeing at least. Thanks for your quick response.
July 11, 2012 at 3:00 pm
Officially MS only supports 2 previous versions in terms of the compat level, i.e. database compat mode 80 is no longer available as of SQL 2012. I would not be surprised if that stance was implied in the blanket statement "any version less than or equal to the Publisher version", and all other tooling, as you mentioned.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply