How do I find all stored procedures or views that use a specific table?3
October 26, 2012 by Kenneth Fisher
Many years ago when I was still working on SQL 2000 I occasionally needed to find all stored procedures and views that referenced a certain table. After some research I found the system table syscomments. This table has a column “text” that contains the “Actual text of the SQL definition statement.” Using the following statement I was able to find every piece of code in the database using the table ‘ABC’.
SELECT DISTINCT OBJECT_SCHEMA_NAME(id), OBJECT_NAME(id) FROM syscomments WHERE [text] LIKE '%ABC%'
This has a few problems. First ABC could be listed in the comments and not in any real code. Second a table ABC_DEF or a view vw_ABC, for example, will give false positives. Third if the stored procedure, view etc is encrypted then it won’t be included in the result set.
As of SQL 2005 the table syscomments became a system view and was depreciated. Microsoft added the system view sys.sql_modules to take its place. The code I used in SQL 2005 was as follows:
SELECT OBJECT_SCHEMA_NAME(object_id), OBJECT_NAME(object_id) FROM sys.sql_modules WHERE [definition] LIKE '%ABC%'
The size of the field that contains the SQL definition is the only major change that I’ve noticed between the two versions. The field sys.sql_modules.definition is a nvarchar(max) instead of the nvarchar(4000) for sys.syscomments.text. This means that SQL stores long pieces of code in a single row instead multiple. As a result the DISTINCT in the query is no longer needed.
In SQL 2008 the DMV (a Data Management Function really) sys.dm_sql_referencing_entities was added. This DMV returns any object that references the object you pass it.
SELECT * FROM sys.dm_sql_referencing_entities('dbo.ABC', 'OBJECT')
While either of the older two pieces of code will still work there is a big advantage to using the DMV. There are no longer false positives from comments, ‘ABC_DEF’ or ‘vw_ABC’ type entries. I believe the result set includes encrypted referencing objects as well, although I haven’t actually tested it. Also by requiring the schema the DMV enforces more precision in the search than the older versions. SchemaA.Table1 and SchemaB.Table1 are two different objects after all.
I don’t expect 2012 to add anything really new to this, but if it does I’ll be sure to add it here.
Of course in all cases if you only want a specific type of object (stored procedures for example) in your result set then you have to either write a function (see my previous post here for an example), use OBJECTPROPERTY(IsProcedure, IsView etc) (2000+), OBJECTPROPERTYEX(BaseType) (2005+), or join with sys.objects, sys.procedures, sys.views etc.
PS Also in 2008+ there is also a DMV sys.dm_sql_referenced_entities which is a handy way to see all objects referenced by the specified stored procedure, view, function etc passed into the DMV.
[…] The first step is to find any subqueries. Taking a look in the SP uspBigOleOops we don’t find any, but if there had been we would go on to step 2 (and come back once done). Next we need to look at any code that is referenced by the SP. Not a big deal in this example but in a multi page SP it could get a bit trickier. The easiest way to get a list of all of the code called by an object (or trigger) is to use the system SP sys.dm_sql_referenced_entities. Side note: there is also a system sp sys.dm_sql_referencing_entities that let’s you find any code that ca… […]
How do I find the columns used in particular stored procedures?
Unfortunately I think object level is as far as you can get. I haven’t seen a way to find what columns are referenced.