|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Tuesday, April 02, 2013 1:48 AM
Points: 1,252,
Visits: 3,367
|
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Thursday, February 28, 2013 1:54 AM
Points: 1,325,
Visits: 1,376
|
|
Hello,
Thanks for the script.
An interesting experiment, but unless there were hundreds of Views in a DB, I think I would prefer using a straight select e.g. Select * From INFORMATION_SCHEMA.VIEW_TABLE_USAGE Order By TABLE_NAME, VIEW_NAME
Regards,
John Marsh
www.sql.lu SQL Server Luxembourg User Group
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Monday, August 23, 2010 8:30 AM
Points: 229,
Visits: 146
|
|
Hi,
At first I thought the query was really good - it would need a tweak to make it a bit better where you have nested views - so something like this:
with Table_analysis (View_Name , level ) as ( select view_name, 0 as level from information_schema.view_table_usage where table_name = @Table_Name union all select vtu.view_name, level + 1 as level from information_schema.view_table_usage vtu inner join Table_analysis ta on ta.View_Name = vtu.table_name ) select * from Table_analysis order by view_name go
unfortunately the results of this don't match up with the Red Gate Dependency checker which found an additional 10 or so views for one of our tables within the same database. After manually checking the differences I found that the nested views should have been included in both lists but sadly the view_table_usage didn't contain all the information it should.
A bit disappointing really - this could have been a really good technique to get view information - instead we have to use Red Gate dependency checker to work out what views access a certain table when we are making DDL changes to tables
Sorry for sounding like a salesman of Red Gate - but using this view_table_usage data doesn't work for us.
Tony
|
|
|
|