First thanks for the scripts, they will surely help me on some occasions. (the one that get the dependencies instead of viewing them in the tiny box in the enterprise manager)

What I would like to bring is when testing them out I used a database that I was very comfortable with and found that the information that I gathered was not very helpful for someone who would need to get a quick overview of that database type in particular.

Not because the scripts does not work well but because the database work differently than the intended proposed solution and this is a scenario that could happen to others as well. I would like to propose you an additional approach.

I believe, when the database has run a bit, is to get the statistics on index scan / seek etc as the primary way to get information about usefulness of a table instead of the table size / rows.

In my case the most worthy tables only contains a few tenth of rows and looking at them from the index scan / seek reveal that information.

What do you think of this additional approach?