October 20, 2013 at 8:24 am
I've read on a few sites that SQL 2005 and SQL 2012 can replicate between each other, but when I attempt to setup SQL 2012 as a Distribution Server on SQL 2005 SP1 I'm getting the error:
This SQL Server version (11.0) is not supported. (Microsoft.SqlServer.ConnectionInfo)
Any suggestions on how to get past this? Or do I need to setup as SQL 2008 server as the Distribution?
Thanks.
October 21, 2013 at 4:24 am
You cannot replicate between SQL 2012 and SQL 2005. There is no known way round this that is supported by Microsoft.
SQL 2005 replication depends on the routine DATABASEPROPERTY which does not exist in SQL 2012. The DATABASEPROPERTYEX functions that SQL 2012 replication relies on do not exist on SQL 2005.
This implies you could write your own DATABASEPROPERTY routine for SQL 2012 and maybe get replication between SQL 2012 and SQL2005 working, but you would be outside of Microsoft support.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
October 21, 2013 at 9:36 am
I'm confused then because per this article it seems like it would work - http://msdn.microsoft.com/en-us/library/ms143699.aspx . It gives three rules for the replication topology between versions:
•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:
oA Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2005 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server 2012; and a SQL Server 2012 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server 2012.
oA Subscriber to a merge publication can be any version less than or equal to the Publisher version.
And if we are using SQL 2005 with SQL 2012 it appears all three rules would be satisfied. If we ran the Distributor on SQL 2012 and the Publisher on 2005 this seems like it would satisfy the first two rules given the Distributor version is greater than the Publisher version. Also SQL 2005 and SQL 2012 are two versions apart (9.x and 11.x) so I'd think this would satisfy the third requirement. Even in its example it mentions SQL 2005 and SQL 2012.
So am I misreading this article or missing something else?
Thanks
October 21, 2013 at 9:53 am
We were part of the SQL Server 2012 TAP program and hit this issue. It was raised as Connect item 652849.
The feedback from MS was that replication with SQL 2012 would be fixed for SQL 2008 upwards, but not for SQL 2005 as it had already gone out of support.
The link you reference appears to be only partially correct: it says replication is supported for the two older versions, and for SQL 2012 these are SQL 2008 R2 and SQL 2008. The reference to SQL 2005 appears to be wrong to me.
My advise is to raise this as a problem with Microsoft. Either they fixed SQL 2005 after it went out of support, or the documentation is wrong.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 29, 2014 at 12:42 am
Hi,
I also got the same error while configuring the replication from sql server 2012 (Publisher) to sql server 2005 as (subscriber).
But I was able to configure replication by connecting the sql server 2005 instance from sql server 2012 management studio.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply