October 5, 2017 at 8:49 am
Howdy all.
I am attempting to set up transactional replication between on prem SQL 2014 SP1 to AWS SQL server 2016. After getting a VPN tunnel and DNS entries all worked out so they can see each other I got this error when setting up the AWS SQL instance as a Subscriber:
The selected Subscriber does not satisfy the minimum versioncompatibility level of the selected publication. (New Subscription Wizard)
Is there a workaround for this, or do I need to set up the AWS SQL server as 2014?
October 5, 2017 at 9:05 am
Looks like you are setting up subscription(s) using SSMS. Try using T-SQL script(s) or create subscriber(s) using SSMS 2016 or higher.
October 5, 2017 at 9:10 am
The publication server is 2014 and our Prod server so I can't really just upgrade that on the fly. I am thinking the solution is to downgrade the AWS Instance to match my on prem version. Just wondering if there was another way to do it.
October 5, 2017 at 9:16 am
Well, You don't have to either upgrade your 2014 publisher(Prod) or downgrade 2016 subscriber(your AWS Instance). All you need is SSMS 2016 or higher(Just client tool). FYI you can download latest SSMS 2017 as standalone package and install(This has nothing to do with actual database Engine). So, basically you would need to connect to your 2014 PROD SQL Server from SSMS 2016 or above and try setting up replication from GUI or use T-SQL Script to setup subscriber.
October 5, 2017 at 9:18 am
Kind of.
My topology is Publisher 2014 -> Distributor 2014 -> Subscriber 2016
I currently have replication set up but have added a new publication and am attempting to replicate it to a different server.
These are supported:
Not supported:
October 5, 2017 at 9:26 am
chris.munsell - Thursday, October 5, 2017 9:18 AMKind of.
My topology is Publisher 2014 -> Distributor 2014 -> Subscriber 2016
I currently have replication set up but have added a new publication and am attempting to replicate it to a different server.These are supported:
- Publisher (2008/R2) -> Distributor (2016) -> Subscriber (2012)
- Publisher (2014) -> Distributor (2016) -> Subscriber (2008/R2)
- Publisher (2016) -> Distributor (2016) -> Subscriber (2012)
Not supported:
- Publisher (2016) -> Distributor (2016) -> Subscriber (2008/R2)
- Publisher (2008/R2) -> Distributor (2016) -> Subscriber (2016)
Your topology is supported...A Distributor can be any version as long as it is greater than or equal to the Publisher version.
To reiterate, when configuring subscriber, Try using SSMS version matching(or higher) with your subscriber(2016 in your case) or T-SQL script. The issue which you are running into is just SSMS thing, nothing to do with engine compatibility AFAIK.
October 6, 2017 at 3:13 am
As already been said. you option at this point is use TSQL. Also u can use SSMS from 2016 that have access to Publisher, Distributor and Subscriber. SSMS for 2016 dont need to be installed on Publisher. It just need to have access to these servers.
BartL
Replication Blog
October 9, 2017 at 9:43 am
chris.munsell - Thursday, October 5, 2017 8:49 AMHowdy all.I am attempting to set up transactional replication between on prem SQL 2014 SP1 to AWS SQL server 2016. After getting a VPN tunnel and DNS entries all worked out so they can see each other I got this error when setting up the AWS SQL instance as a Subscriber:
The selected Subscriber does not satisfy the minimum versioncompatibility level of the selected publication. (New Subscription Wizard)
Is there a workaround for this, or do I need to set up the AWS SQL server as 2014?
We're using this exact scenario. All you have to do is set up distribution on the 2016 subscriber instead of the 2014 publisher. You don't even have to use TSQL -- not that there's anything wrong with that -- the Subscription Wizard will work.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply