Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

sys.dm_db_objects_disabled_on_compatibility_level_change (Transact-SQL)

Applies To: SQL Server 2014, SQL Server 2016 Preview

Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).

Lists the indexes and constraints that will be disabled as a result of changing compatibility level in SQL Server. Indexes and constraints that contain persisted computed columns whose expressions use spatial UDTs will be disabled after upgrading or changing compatibility level. Use this dynamic management function to determine the impact of a change in compatibility level.

Applies to: SQL Server (SQL Server 2012 through current version, SQL Database V12.

Topic link icon Transact-SQL Syntax Conventions

sys.dm_db_objects_disabled_on_compatibility_level_change ( compatibility_level ) 


int that identifies the compatibility level that you plan to set.

Column name

Data type




1 = constraints

7 = indexes and heaps



OBJECT or COLUMN for constraints

INDEX for indexes and heaps



OBJECT ID of constraints

OBJECT ID of table that contains indexes and heaps



NULL for constraints

Index_id for indexes and heaps



Description of the dependency that is causing the constraint or index to be disabled. The same values are also used in the warnings that are raised during upgrade. Examples include the following:

  • "space" for an intrinsic

  • "geometry" for a system UDT

  • "geography::Parse" for a method of a system UDT

Persisted computed columns that use some intrinsic functions are disabled when the compatibility level is changed. Also, persisted computed columns that use any Geometry or Geography method are disabled when a database is upgraded.

Which functions cause persisted computed columns to be disabled?

When the following functions are used in the expression of a persisted computed column, they cause indexes and constraints that reference those columns to be disabled when the compatibility level is changed from 80 to 90:

  • IsNumeric

When the following functions are used in the expression of a persisted computed column, they cause indexes and constraints that reference those columns to be disabled when the compatibility level is changed from 100 to 110 or higher:

  • Soundex

  • Geography:: GeomFromGML

  • Geography:: STGeomFromText

  • Geography:: STLineFromText

  • Geography:: STPolyFromText

  • Geography:: STMPointFromText

  • Geography:: STMLineFromText

  • Geography:: STMPolyFromText

  • Geography:: STGeomCollFromText

  • Geography:: STGeomFromWKB

  • Geography:: STLineFromWKB

  • Geography:: STPolyFromWKB

  • Geography:: STMPointFromWKB

  • Geography:: STMLineFromWKB

  • Geography:: STMPolyFromWKB

  • Geography:: STUnion

  • Geography:: STIntersection

  • Geography:: STDifference

  • Geography:: STSymDifference

  • Geography:: STBuffer

  • Geography:: BufferWithTolerance

  • Geography:: Parse

  • Geography:: Reduce

Behavior of the disabled objects


If the clustered index is disabled, or if a non-clustered index is forced, the following error is raised: "The query processor is unable to produce a plan because the index '%.*ls' on table or view '%.*ls' is disabled." To re-enable these objects, rebuild the indexes after upgrade by calling ALTER INDEX ON … REBUILD.


If a table with a disabled heap is used, the following error is raised. To re-enable these objects, rebuild after upgrade by calling ALTER INDEX ALL ON … REBUILD.

// ErrorNumber: 8674
// ErrorSeverity: EX_USER
// ErrorFormat: The query processor is unable to produce a plan because the table or view '%.*ls' is disabled.
// ErrorCause: The table has a disabled heap. 
// ErrorCorrectiveAction: Rebuild the disabled heap to enable it. 
// ErrorInserts: table or view name 
// ErrorOwner: mtintor 
// ErrorFirstProduct: SQL11

If you try to rebuild the heap during an online operation, the following error is raised:

// ErrorNumber: TBD 
// ErrorSeverity: EX_USER 
// ErrorFormat: Cannot rebuild table '%.*ls' online because it is disabled. 
// ErrorInserts: table name 
// ErrorCause: Table cannot be rebuilt online if it is disabled. 
// ErrorCorrectiveAction: Rebuild the disabled table offline. 
// ErrorExecImpact: TRANSACTION_ABORT 
// ErrorBlameComponent: User 
// ErrorProbability: Low 
// ErrorStateBefore: ONLINE 
// ErrorStateAfter: ONLINE 
// ErrorFirstProduct: SQL11 

Check Constraints and Foreign Keys

Disabled check constraints and foreign keys do not raise an error. However, the constraints are not enforced when rows are modified. To re-enable these objects, check the constraints after upgrading by calling ALTER TABLE … CHECK CONSTRAINT.

Persisted Computed Columns

Since it is not possible to disable a single column, the entire table is disabled by disabling the clustered index or heap.


Requires the VIEW DATABASE STATE permission.

The following example shows a query on sys.dm_db_objects_disabled_on_compatibility_level_change to find the objects impacted by changing the compatibility level to 120.

SELECT * FROM sys.dm_db_objects_disabled_on_compatibility_level_change(120);

Community Additions

© 2015 Microsoft