liveBook · Manning

Enterprise-only feature

As explained in 100 SQL Server Mistakes and How to Avoid Them

An enterprise-only feature is a SQL Server capability restricted to Enterprise edition.

An enterprise-only feature is a SQL Server capability restricted to Enterprise edition. Choosing Enterprise merely because an application might need one is costly and avoidable: inspect the database for actual dependencies first. section 8.5

Mistake: assuming SSIS requires Enterprise

SSIS runs on Standard edition, although some scale-out, control-flow, transformation, and advanced-source or destination capabilities are restricted. A database using table partitioning, however, does require Enterprise edition. section 8.5

Listing 8.3 Creating a database that requires Enterprise edition
CREATE DATABASE EnterpriseDatabase ;
GO

USE EnterpriseDatabase ;
GO

CREATE PARTITION FUNCTION PartFunc (INT)
   AS RANGE LEFT FOR VALUES (100, 200, 300) ;

CREATE PARTITION SCHEME PartScheme
   AS PARTITION PartFunc
   ALL TO ('PRIMARY') ;


CREATE TABLE VeryLargeTable (
   KeyColumn      INT    PRIMARY KEY    IDENTITY,
   OtherColumn    VARCHAR(50)
) ON PartScheme(KeyColumn) ;

Create a partitioned database and table to produce a concrete Enterprise-edition dependency. section 8.5

Listing 8.4 Discovering Enterprise-only features
USE EnterpriseDatabase ;
GO

SELECT feature_name 
FROM sys.dm_db_persisted_sku_features ;

Query sys.dm_db_persisted_sku_features; an empty result indicates no persisted Enterprise-only database features. section 8.5

Apply these safer edition-selection rules:

  • Check persisted SKU features before upgrading a brownfield application. section 8.5
  • Reserve Enterprise for required Enterprise-only capabilities; use Developer edition for development and never production. section 8.5

How 100 SQL Server Mistakes and How to Avoid Them covers it

How deep it goes
Explains edition restrictions, demonstrates partitioning, and provides a DMV check rather than surveying every Enterprise feature.
Examples
Uses SSIS restrictions, a partitioned table, and sys.dm_db_persisted_sku_features as concrete examples.
What it assumes
Assumes basic SQL Server edition awareness and teaches how to verify database-level Enterprise dependencies.
What you can do after
Diagnose with sys.dm_db_persisted_sku_features and select Enterprise only when persisted requirements justify it.
How it connects
Connects SQL Server editions with SSIS, table partitioning, change data capture, and Developer edition.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of 100 SQL Server Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.