SQL SERVER – Edition Downgrade with Supported Migration Checks

To Downgrade SQL Server editions, I plan a supported migration or reinstall. I test the application on the destination edition first.

A protected mechanism awaits fit checks beside two differently fitted instrument cases.

The client needed Enterprise to Standard after a vendor installed the wrong licensed edition. This wasn’t a newer-engine-to-older-engine move. The Setup matrix determines supported edition changes. Enterprise to Standard isn’t a general reverse Edition Upgrade.

SELECT SERVERPROPERTY('Edition') AS Edition,
       SERVERPROPERTY('ProductVersion') AS ProductVersion;
-- Run in each user database being assessed:
SELECT feature_name FROM sys.dm_db_persisted_sku_features;
  1. Inventory features and resource limits against the destination edition. Run the catalog query in every user database, but also assess instance features, availability groups, jobs and licensing. An empty result is not a complete compatibility certificate.
  2. Rehearse the move on the intended edition and exact engine build. Take tested backups and script logins with their SIDs, jobs, linked servers, credentials and other required instance settings. Preserve encryption keys and certificates needed for restore.
  3. Arrange a maintenance window and a rollback plan. For an unsupported Enterprise-to-Standard in-place change, Microsoft documents an uninstall and reinstall procedure. A separately prepared target instance can also make migration testing and rollback clearer.
  4. Restore and validate the user databases on the prepared target, with application, integrity and performance checks. Handle system database migration only through the documented procedure for the exact build and configuration. Don’t replace arbitrary database files on a running instance.

I keep backups and record the instance configuration first. Then I prove that the application works on the destination edition. Discovering a required Enterprise feature after uninstalling the only working instance would be too late.

Reference: Microsoft edition-change procedure.

Related reading

An edition downgrade is not a version downgrade, it is a migration between supported feature and licensing choices.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.


Discover more from SQL Authority with Pinal Dave

Subscribe to get the latest posts sent to your email.

SQL DMV, SQL Server
Previous Post
MySQL – Fix Error – WordPress Database Error Duplicate Entry for key PRIMARY for Query INSERT INTO wp_options
Next Post
SQL SERVER – Case of Different Default Collation on Two Servers

Related Posts

2 Comments. Leave new

  • that is sys.dm_db_persisted_sku_features; not dm_db_persisted_sku_fearures

    Reply
  • Are you saying backup of current databases (on sql 2016) and restore on down version (sql 2014)? Do you think it’s gonna work?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.