Object Dependencies (General Page)

Some database objects have dependencies upon other database objects. For example, views and stored procedures depend upon the existence of tables that contain the data returned by the view or procedure. The Object Dependencies (General Page) for the current object lists both the database objects that must be present for the object to function properly and the objects that depend upon the selected object. An object that references another object in its definition and that definition is stored in the system catalog is called a referencing entity. An object that is referred to by another object is called a referenced entity.

Use this dialog box to understand the dependencies before changing or deleting the selected object.

Objects that depend on <selected object>

Clicking this button displays a list of those objects that are dependency-tracked and that depend on the selected object.

Objects on which <selected object> depends

Clicking this button displays a list of those objects that are dependency-tracked, on which the selected object depends.

Dependencies

If Objects that depend on <selected object> is clicked, this displays an hierarchical view of objects that depend on the selected object. If Objects on which <selected object> depends is clicked, this displays an hierarchical view of objects on which the selected object depends.

Name

Displays the name of the object selected in the Dependencies tree view above.

Type

Displays the type of the object selected in the Dependencies tree view above.

Dependency type

Displays the type of dependency between two objects. Can be one of the following:

  • Schema-bound dependency

    Is a relationship between two objects that prevents the referenced object from being dropped or modified as long as the referencing object exists. A schema-bound dependency is created when a view or user-defined function is created by using the WITH SCHEMABINDING clause, or when a table references another object through a CHECK or DEFAULT constraint or in the definition of a computed column.

  • Non-schema-bound dependency

    Is a relationship between two objects that does not prevent the referenced object from being dropped or modified.

  • Not available

    Indicates the dependency type cannot be determined. This occurs only when the selected object is on an instance of SQL Server that is earlier than SQL Server 2008.

Community Additions

ADD
Show: