Analyzing Impact of DELETE operation

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 manually identifing all the above dependencies becomes a very complicated and time-consuming task.

The Dependencies Analyzer streamlines this operation by offering you to check dependencies of the object before you drop it from a database.

To check dependencies for the object, which you want to drop in the Object Explorer:

1. Select the object or mutiple objects in the Object Explorer and choose Delete from a popup menu.
2. Select the object from the list in the Confirm Drop dialog box
3. Press Show Dependencies button

To check dependencies for the table column, when you attempt to delete this column in the Table Editor:

• Press Show Dependencies button in the Confirmation message.