https://www.sqlserver70.com/tags/refactoring/Recent content in Refactoring on SQL Server ScriptsHugo -- gohugo.ioenSQLServer70.comSat, 23 May 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-object-dependencies-script/Sat, 23 May 2026 00:00:00 +0000https://www.sqlserver70.com/post/sql-server-object-dependencies-script/ <p>Before renaming a column, retiring a view, or dropping a stored procedure, every DBA needs the answer to one question: what else depends on this object? This T-SQL script reads <code>sys.sql_expression_dependencies</code> and reports every referencing-and-referenced pair in the current database, with optional filtering to a single object name — the safe-refactoring impact analysis report.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:inline-block;width:728px;height:90px" data-ad-client="ca-pub-1012089347386563" data-ad-slot="8593449130"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p>SQL Server tracks expression-level dependencies between user objects in the catalog view <code>sys.sql_expression_dependencies</code>. Every reference from a stored procedure, function, view, trigger, default, computed column, or check constraint to another object — table, view, function, procedure, type, or column — produces a row. The view supersedes the legacy <code>sys.sql_dependencies</code> view (deprecated in SQL Server 2008) and the older <code>sp_depends</code> stored procedure (which has always been unreliable for cross-database and late-bound references). Modern dependency tracking is metadata-only, schema-bound-aware, and accurate across cross-database name resolutions.</p>