Hi, I'm comparing two databases' stored procs and I'm getting some strange results. My comparison is scripting some stored procs which are neither in Database A or B. As a matter of fact, they appear to be very old stored procs that were dropped from the source database a long time ago. Yet the comparison seems to think that the source still has it and creates the stored procs to be created in the target database. Why is this happening?
The only thing I can think of here is that you're running into the old "sp_rename" bug in SQL Server. When someone uses sp_rename to rename a stored procedure it only changes the name in the sysobjects table - it does not update the textual definition in the syscomments table.
When the object is scripted so that it can be run on the target it takes the definition from syscomments...which may have a different name.
I would look through the list of stored procedures that were dropped from the target database and the list of ones that were added to see if you can spot a correlation.
Compare DB's
Posted - 06/15/2009 : 13:13:03
