7 Comments

1. John Galt says:

   September 18, 2011 at 8:12 am

   Hello Derek,

   Thank you for your offering. However, this query throws an un-captured error when no columns are detected. I received this when I applied it to one of my databases. It needs more seasoning.

   Msg 2020, Level 16, State 1, Line 5
   The dependencies reported for entity “dbo.rpt_Ca____” do not include references to columns. This is either because the entity references an object that does not exist or because of an error in one or more statements in the entity. Before rerunning the query, ensure that there are no errors in the entity and that all objects referenced by the entity exist.

   Reply to this comment
   • Derek Dieter says:

     September 19, 2011 at 10:03 pm

     Hi John,

     Yes, I believe it is a bug. If you look, I bet that procedure references an object that does not exist. Instead of SQL Server bypassing it, it raises an error.

     Reply to this comment
2. Rathnam says:

   August 9, 2011 at 10:04 pm

   Hi,

   if i am using the above script i am getting the below error.

   Msg 2020, Level 16, State 1, Line 7
   The dependencies reported for entity “dbo.xxxx” do not include references to columns. This is either because the entity references an object that does not exist or because of an error in one or more statements in the entity. Before rerunning the query, ensure that there are no errors in the entity and that all objects referenced by the entity exist.

   Thanks & Regards,
   Rathnam

   Reply to this comment
   • Derek Dieter says:

     August 10, 2011 at 6:40 am

     Hi Rathnam,

     I believe that is a SQL 2008 bug. I’m not sure but think it may be fixed in R2. The only workaround is likely to drop the object.

     Best of Luck,
     Derek

     Reply to this comment
     • Rathnam says:

       August 11, 2011 at 3:21 am

       Hi Derek,

       I am using below version

       Microsoft SQL Server 2008 R2 (RTM) – 10.50.1600.1 (Intel X86) Apr 2 2010 15:53:02 Copyright (c) Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

       Thanks & Regards,
       Rathnam

       Reply to this comment
       • Derek Dieter says:

         August 12, 2011 at 10:11 pm

         Hi Rathnam,

         After looking into this error, it seems as if SQL 2008 does not allow procedures that have orphaned references to procedures, tables, or columns that do not exist. It seems as if this procedure would be able to overlook this issue, however they do not. In my opinion, it would be a great enhancement to overlook this issue.

         Thanks,
         Derek

         Reply to this comment
3. SQL Server 2005 vs SQL Server 2008 says:

   June 25, 2009 at 8:45 am

   [...] New DMV shows all object dependencies [...]

   Reply to this comment