Before you perform an operation, which deletes a database object or deletes a column from a table, you might want to know, which impact this operation will have to the rest of your backend application.
For example, when you delete a table from a database, some stored procedures might stop functioning properly, or you might lose a number of views and triggers, which depend on this table, or referential integrity of the database can be compromised. If your database has hundreds of schema objects and also there are other databases, which might use this table then to find manually all dependencies becomes a very complicated and time-consuming task.
The Dependencies Analyzer streamlines this operation by providing direct access to Referred By report during object delete operations or table columns delete operations. You can also invoke the same check operations even before you attempt to drop the object using Search for References popup menu on any selected object in Object Explorer.
To check dependencies for the object, which you want to drop in the Object Explorer:
To check dependencies for the table column, select the required column under a table node in the Object Explorer and choose Search for References popup menu.
To check dependencies for the table column, when you attempt to delete this column in the Table Editor: