I have just run the following: SELECT feature_name FROM sys.dm_db_persisted_sku_features Īnd found that for the db with 5 partitions functions/schemes, Partitioning is listed as a version specific feature. SQL Server 2012 Editions SQL Server 2012 is offered in three main editions to accommodate the unique feature, performance and price requirements of organizations and individuals: Enterprise Edition is ideal for mission critical applications and large scale data warehousing. When I next came to backup and restore to prod, this time the database activated ok without error - even though there were partition functions and schemes. I then went through a time consuming process to remove the partitions functions and schemes, and could successfully restore the database on the Standard edition.Īfter a while I backed up the DB (with no PFs or PSs), transferred it to my dev env, restored it (on SQL Enterprise), and after some time I found that a single partition function and scheme had been created. Almost all of the available programmability features of the SQL Server 2016 Enterprise edition are available in the Standard edition with the exception of advanced R integration and R server (standalone).
When I dug deeper, I found that it appeared that FTS or some other function had automatically created 5 partition functions and schemes. SQL Server 2016 Standard and Enterprise editions provide the exact same development tools which is a strong benefit either way. However when I restored the DB it failed to activate, and in the Event Log, I found a message indicating the database couldn't be activated because it contained features not supported by the version. I didn't think it should be a problem, as I hadn't implemented any enterprise specific features. I have been developing against SQL Server 2012 Enterprise, and came to migrate to production, where I found our hosting provider had installed Standard.
0 kommentar(er)
