Will log shipping work between different editions? Primary is SQL Server 2016 SE and Secondary is SQL Server 2016 EE. If not, how else can I set up high availability for this combination of servers?

  • Yes it does. But you cant use secondary as standby. Because upgrading database to higher version or edition require RESTORE WITH RECOVERY. Jul 9 '19 at 11:52
  • 2
    Check with your MS rep, but you typically get one warm standby of any edition. So you could have another SE that you only use for receiving the log ships (no reporting, no developing, no other use). Jul 9 '19 at 12:13
  • 1
    Different editions do not have any relevance/dependency for the RECOVERY/NORECOVERY/STANDBY option. Restoring from a lower to EE might not be possible if any storage level functionality that requires EE was used for the database. Jul 9 '19 at 12:43
  • so it's means no issue with different editions.
    – jega
    Jul 9 '19 at 14:43

There is no functional blocker in log shipping from Standard to Enterprise on the same version, however, you may want to confirm your licensing position in this scenario with your licensing reseller. Depending on how you're licensing SQL Server, you may not be covered for this additional server, even as a warm standby.

Also, you should note that Log Shipping is not a high availability technology, it is a Disaster Recovery technology. If you want high availability, you should look at implementing Availability Groups (Basic AGs are available in Standard but you can't use SE/EE together in a Basic AG architecture) or a Failover Cluster Instance.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.