Description: I am a senior database administrator who sometime enjoy writing about the situations, issues and problems that I have experienced, or at least thought about. Both because the SQL Server Community is so good at sharing information and I would like to participate, but I would also try to make an effort so I actually remember some of these things.
Sometimes you want to find the database object dependency within a database or instance, and luckily this is something Microsoft has thought of in the form of a view called sys.sql_expression_dependencies
Microsoft also tells us a fair bit about this magnificent view :
“(This view) Contains one row for each by-name dependency on a user-defined entity in the current database. This includes dependences between natively compiled, scalar user-defined functions and other SQL Server modules. A dependency between two entities is created when one entity, called the referenced entity, appears by name in a persisted SQL expression of another entity, called the referencing entity. For example, when a table is referenced in the definition of a view, the view, as the referencing entit