THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » metadata » catalog views   (RSS)
  • T-SQL Tuesday #24 : Dude, where's the rest of my procedure?

    This month's T-SQL Tuesday is being hosted by Brad Schulz (blog) and the topic is one that should attract a lot of submissions: Procedures and Functions. Last week, I talked about the case against INFORMATION_SCHEMA views - I provided several examples where I feel the INFORMATION_SCHEMA views fall short of the catalog views, and expressed my ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on November 8, 2011
  • The case against INFORMATION_SCHEMA views

    In SQL Server 2000, INFORMATION_SCHEMA was the way I derived all of my metadata information - table names, procedure names, column names and data types, relationships... the list goes on and on. I used the system tables like sysindexes from time to time, but I tried to stay away from them when I could. In SQL Server 2005, this all changed with ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on November 3, 2011
  • Finding keyless tables across multiple servers

    Christina Leo (@christinaleo) asked this question on twitter today: So, if I ever needed a POSH script, today is the day. Having to inventory all prod databases to find tables missing primary keys.I have a query that returns what I need, but I need a report for each of 60+ databases across 3 servers I haven't joined the ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on October 20, 2011
  • Using the catalog views : clearing out a "botched" schema

    A user on StackOverflow had populated a custom schema with a bunch of tables, and needed to replace them with a new set of tables due to various changes. But he couldn't just drop them all in any arbitrary order, because there were foreign keys in place. His workaround was to just run a ''drop all tables'' script multiple times until there were no ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on July 7, 2011
Privacy Statement