Exportera (0) Skriv ut
Visa allt
Expand Minimize
EN
Det här innehållet finns inte tillgängligt på ditt språk men här finns den engelska versionen,
0 av 2 bedömde detta vara till hjälp - Bedöm det här ämnet

sys.dm_db_objects_impacted_on_version_change (Azure SQL Database)

Updated: August 1, 2013

This topic is OBSOLETE. You can find the most current version in the SQL 14 Transact-SQL Reference.

ImportantImportant
This topic is not maintained. For the current version, see sys.dm_db_objects_impacted_on_version_change.

This database-scoped system view is designed to provide an early warning system to determine objects that will be impacted by a major release upgrade. You can use the view either before or after the upgrade to get a full enumeration of impacted objects. You will need to query this view in each database to get a full accounting across the entire server.

 

Column name Data Type Description

class

int NOT NULL

The class of the object which will be impacted:

1 = constraint

7 = Indexes and heaps

class_desc

nvarchar(60) NOT NULL

Description of the class:

OBJECT_OR_COLUMN

INDEX

major_id

int NOT NULL

object id of the constraint, or object id of table that contains index or heap.

minor_id

int NULL

NULL for constraints

Index_id for indexes and heaps

dependency

nvarchar(60) NOT NULL

Description of dependency that is causing a constraint or index to be impacted. The same value is also used for warnings generated during upgrade.

Examples:

space (for intrinsic)

geometry (for system UDT)

geography::Parse (for system UDT method)

Permissions

Requires the VIEW DATABASE STATE permission.

Example

The following example shows a query on sys.dm_db_objects_impacted_on_version_change to find the objects impacted by an upgrade to the next major server version

SELECT * FROM sys.dm_db_objects_disabled_on_version_change;
GO
class  class_desc        major_id    minor_id    dependency                     
------ ----------------- ----------- ----------- ---------- 
1      OBJECT_OR_COLUMN  181575685   NULL        geometry                      
7      INDEX             37575172    1           geometry                      
7      INDEX             2121058592  1           geometry                      
1      OBJECT_OR_COLUMN  101575400   NULL        geometry   

Remarks

For the upcoming June service release, persisted computed columns that include some intrinsic functions will be impacted.

SQL Database will support updates that include increased precision for Spatial Types. Types based on the Geography CLR data type will support objects larger than a hemisphere. Persisted computed columns that use Geometry or Geography methods may be impacted by the increased precision for spatial data types. Indexes or constraints defined in terms of the persisted computer column will also be impacted. Impacted indexes will remain enabled, but should be rebuilt to take advantage of the new precision. Constraints will be enabled, but untrusted. They will need to be rechecked.

The following list provides the intrinsic functions and methods in the upcoming June service release that will impact a persisted computed column.

  • IsNumeric

  • Soundex

  • Geography:: GeomFromGML

  • Geography:: STGeomFromText

  • 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:: Reduce

How to Update Impacted Objects

The following ordered steps describe the corrective action to take after the upcoming June service release upgrade.

 

Order Impacted Object Corrective Action

1

Indexes

Rebuild any index identified by sys.dm_db_objects_impacted_on_version_change

For example:

ALTER INDEX ALL ON <table> REBUILD

or

ALTER TABLE <table> REBUILD

2

Object

All constraints identified by sys.dm_db_objects_impacted_on_version_change must be revalidated after the geometry and geography data in the underlying table is recomputed. For constraints, revalidate using ALTER TABLE.

For example:

ALTER TABLE <tab> WITH CHECK CHECK CONSTRAINT <constraint name>

or

ALTER TABLE <tab> WITH CHECK CONSTRAINT ALL

See Also

Var detta till hjälp?
(1500 tecken kvar)
Tack för dina kommentarer

Gruppinnehåll

Lägg till
Visa:
© 2014 Microsoft. Med ensamrätt.