Assume that there are 1000 stored procedures available in your SQL Server database. At some point, you’ll need to drop some columns from the table definitions due to enhancement needs.
If any of your stored procedure definitions used the columns you dropped out, you’re going to have a rough time figuring out which ones.
Here’s an easy way to do this:
- Run “Generate SQL Script” for all stored procedures.
- In SQL Query Analyzer, run the generated SQL script file.
This returns a list of the names of the stored procedures that errored out while compiling. These errors are due to usage of dropout columns in their definitions.
