Excellent article...the communication is very clear. I have a similar problem with my database and have implemented a solution without using vb.net in which such procedures with changed names are found and filtered rather than being changed and compiled again in the destination database. I wonder if we can create a DDL trigger that can prevent users from changing names of Stored Procs from Object Explorer.