We are not only migrating from SQL Server 2000 to SQL Server 2005 but we are also changing our database structure (changing column names, datatypes, table names, etc.). Thus our one developer who has about 100 stored procedures to change is attempting to find a way to change his procedures without having to go through line by line. What he would do is copy the procedure from SQL Server 2000 to SQL Server 2005 and hit the execute button and let the compile tell him what was wrong; such as table does not exist, column doesn't exist, etc. We have tested in SQL Server 2000 and when we rename a column to a bad name, it compiles with an error. example: Server: Msg 207, Level 16, State 3, Procedure usp_procedure_name, Line 40 Invalid column name 'cust_po'. However, in SQL Server 2005 this doesn't always happen. It will compile successfully. Is there a bug in SQL Server 2005/Management Studio or is there an option that I need to turn on or off? Or is there an issue with a fix or service pack? Or do I need to apply one?