SQL Server – Transactional Replication Between SQL Server 2019 and 2016

I believe it is possible to restore with same old answer that subject to condition you are not using any "enterprise specific" features. This you can get from

select * from sys.dm_db_persisted_sku_features.

If you are using any such feature you would have to stop using it, take fresh backup and then restore. I know its hard to tell because starting from SQL Server 2016 Sp1 standard provides far more features support. So at the last the answer would be you need to restore and test.

Good news is SQL Server 2017 RTM Evaluation Edition is released so you have the Eval edition for your testing.

The short answer is Yes.

If you can do it in an AG, and you can do it in SQL Server standard - you should be able to do it in a Basic Availability Group. The only gotcha was the distributor which wasn't able to be on an AG - the Replication couldn't work with the listener right - until the releases described in your links.

So you would basically have three AGs. Each with one DB. The distributor would be in one. The Subscriber in another. The Publisher in another.

You have to have your distributor on a separate SQL Server instance. So this would be mean two instances participating in a Basic Availability Group for the distributor, and then two for the Publisher and, most likely, two for the subscriber. Because of the limitations in the Basic Availability Group.

You could have more than on AG on an instance and have one DB in each and that would be good. but your limit here is 1.) You are doing replication, likely for a reason so your publisher and subscriber would likely be on different instances. 2.) The distributor has to be separate from publisher and subscriber.