Replication from SQL Server 2014 (publisher) -> SQL Server for Linux 2019 Preview (subscriber)

[mateodelnorte]

Hi all,

I'm trying to get a transactional pull replication subscription going from SQL-Server 2014 on Windows Server (publisher) -> SQL Server for Linux 2019 Preview on Linux (subscriber), but running into some issues.

SSMS is giving an error when creating the distributor, which says that sql version in your 2019 cant create distribution objects. We're also getting an error saying the subscriber version is higher than publisher so we cant not subscribe 2019 to the 2014 server.

This all seems like it should be possible. Where can I go to ask questions for help on this?

Thanks.

[vin-yu]

To use the replication wizards with SQL Server 2019, you'll need the latest SSMS. that should address tour first screenshot.

Update 3/11/2020
A 2014 publisher and 2019 subscriber is not a supported configuration see:
https://docs.microsoft.com/en-us/sql/relational-databases/replication/replication-backward-compatibility?view=sql-server-ver15

What version of SQL Server is your distributor on?

also, for a SQL Server in Container demo. check this out:
https://github.com/Microsoft/sql-server-samples/tree/master/samples/containers/replication

[mateodelnorte]

We're actually super close to getting this to work now. The distributor is on the 2014. I've got the agent running on 2019. I now just need to figure out how to get an SSL connection set up between the two over the internet. Matt

…

On Tue, Oct 2, 2018 at 8:10 PM Vin Yu ***@***.***> wrote: To use the replication wizards with SQL Server 2019, you'll need the latest SSMS. that should address tour first screenshot. It should be possible to have a 2014 publisher and 2019 subscriber.... i'll check. https://blogs.msdn.microsoft.com/sql_server_team/upgrading-a-replication-topology-to-sql-server-2016/ What version of SQL Server is your distributor on? https://github.com/Microsoft/sql-server-samples/tree/master/samples/containers/replication — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#368 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAh3XyWId367NY87APGd7TT2iFwOqG3cks5uhA54gaJpZM4XCYHz> .

[jhchilds]

Hi Matt,

I'm attempting something quite similar and wondering if you had any advice. I'm trying to implement peer to peer replication between SQL-Server 2017 on Windows 10<- -> SQL Server for Linux 2019 Preview on Linux . I'm running into some issues and have some questions:

1. I am getting multiple errors when attempting to configure the distributor on Linux.
2. Is this why you mentioned using SSL connection between the two? (how did you implement this?)

It has been quite some time since this thread was active but I'd appreciate any information you may have to offer.

Josh

[banerjeeamit]

What are the errors that you are seeing? And are you attempting to set this up using Replication T-SQL scripts or using Management Studio?

[kaysauter]

I am wondering if this is still believed to be possible even though this https://docs.microsoft.com/en-us/sql/relational-databases/replication/tutorial-preparing-the-server-for-replication?view=sql-server-ver15 states clearly that instances can't be 2 versions apart. However, what it does not say is how the case is for 2019 because it only refers to 2016. And I am not referring to Linux or container versions, but the "normal" SQL Server versions. Apologies if I'm too OT with this.

[vin-yu]

Hi Everyone, I made an edit on my original comment. At the moment, this is not a supported configuration (2014 publisher, 2019 subscriber)

https://docs.microsoft.com/en-us/sql/relational-databases/replication/replication-backward-compatibility?view=sql-server-ver15