It’s a very good practice that you check the dependencies of the other objects when you change an object. Many developers just don't do it, even when the change(s) is tiny it could withdraw change(s) in other objects.
The example below is given for a stored procedure. I made a change for stored procedure spGeneralReportDWH_ModifiedOn and then I usually check depending objects as well as the objects the stored procedure depends from.
It's very simple as on this capture
Figure 1 shows the objects that are depending on the modified stored procedures.
Figure 1. Objects that depend on spGeneralReportDWH_ModifiedOn
Second Figure 2 shows the objects that are used in the stored procedure.
Figure 2. Objects from which spGeneralReportDWH_ModifiedOn depends from
This is a very good option offered in SSMS and it seems to be not used regularly, at least among the colleagues I’ve been working with in the past several years. I noticed that so that I’d like to share it.
Thanks
