SQL Server Team-based Development - Red Gate Software

269
Chapter 9: Searching DDL and Build Scripts
UNION ALL
SELECT Specific_Catalog + '.' + Specific_Schema + '.' + Specific_Name
+ '(' + Parameter_name + ')' ,
'routine parameter'
FROM information_schema.parameters
WHERE parameter_name ''
AND parameter_name LIKE @SearchString
UNION ALL
SELECT Table_Catalog + '.' + Table_Schema + '.' + Table_Name + '.'
+ Column_Name ,
'column Name'
FROM INFORMATION_SCHEMA.COLUMNS
WHERE column_name LIKE @SearchString
UNION ALL
SELECT Table_Catalog + '.' + Table_Schema + '.' + Table_Name + '.'
+ Column_Name + '.default' ,
'default constraint text'
FROM INFORMATION_SCHEMA.COLUMNS
WHERE column_default LIKE @SearchString
Listing 9-1: Searching your database using INFORMATION_SCHEMA views.
Learning patience: using SMO
You can get a huge range of database and server objects with SMO, as long as you don't
mind waiting, and if you like coding in a .NET language. The problems come when
you try to tackle a large database. You are soon in trouble if you have a lot of tables and
columns, because you have to walk the hierarchy of SMO objects, rather than do a setoriented
operation. SMO provides a logical and consistent interface into a database,
but it does not represent the reality of the way that this information is actually stored
in the database.
SMO comes into its own as a way of quickly finding out how to access a "difficult" database
object. If you use SMO, and run Profiler at the same time, to see what SQL is being
executed as a result of running an SMO job, you can quickly achieve SQL MegaStar status
in your development team.