Share via

How to: View SQL Dependencies (SQL Server Management Studio)

This topic describes how to view dependencies on SQL objects. User-defined database objects can have dependencies upon other user-defined database objects. For example, views and stored procedures depend upon the existence of tables that contain the data returned by the view or procedure. Before modifying or moving a database object, it is important to identify the objects that depend upon that object as well as the database objects that must be present for the object to function properly.

To view database object dependencies

  1. In Object Explorer, connect to an instance of the Database Engine and then expand that instance.

  2. Expand Databases, expand the database in which the object exists, and then expand the folder in which the object belongs. For example, if the object is a stored procedure, expand Programmability and then expand Stored Procedures.

  3. Right-click the object, and then click View Dependencies.

  4. To display a hierarchical view of objects that depend on the selected object, select Objects that depend on <selected object>. To display a hierarchical view of objects on which the selected object depends, select Objects on which <selected object> depends.

    For each object displayed, the object name and type are shown as well as the type of dependency between the objects. The dependency type value can be one of the following:

    • Schema-bound dependency

      A 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

      A non-schema-bound dependency is a relationship between two objects that does not prevent the referenced object from being dropped or modified.

    • Not available

      "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.