Home Dashboard Directory Help
Search

Renaming a stored procedure will not change definition in sql_modules by SamCPP


Status: 

Closed
 as Won't Fix Help for as Won't Fix


6
0
Sign in
to vote
Type: Bug
ID: 432565
Opened: 4/14/2009 9:31:14 PM
Access Restriction: Public
0
Workaround(s)
view
4
User(s) can reproduce this bug

Description

This is similar to issue 125246 which is now closed.

In SSMS (on a SQL Server 2008 CU4 machine), if I rename a stored procedure in the object explorer, the stored procedure is renamed fine and can be called properly via other stored procs, queries and so on.

The problem is that when I query the sys.objects/sys.sql_modules, the definition of it has the OLD name for the CREATE PROCEDURE.

My server is running on a WinXP SP3 machine (SQL Server 2008 Enterprise Evaluation). My client machine is a Windows Vista SP1 machine.
Details
Sign in to post a comment.
Posted by Microsoft on 3/29/2011 at 3:07 PM
Hello,

Thank you for submitting this suggestion, but given its priority relative to the many other items in our queue, it is unlikely that we will actually complete it. As such, we are closing this suggestion as “won’t fix”. If you feel that this is worth reconsidering, feel free to reopen it and we will take another look.

Jean-Sébastien, SQL-Server
Posted by Microsoft on 7/23/2009 at 9:13 AM
Hi,

Thankyou for this bug report.

This mis-behavior has existed for some long time. We really should fix it! I've added it to our TODO list, and will try to get a fix, in between the many large projects currently underway.

Thanks,

Jim Hogg
Posted by Spivey on 6/22/2009 at 3:12 PM
This does terrible things when you use a compare tool like SQLCompare which runs off of SysComments. Even though the sproc is renamed, SysComments still shows the old name. Other bugs entered about this dating back to 2005 said that this would be looked at in future releases. It has not been fixed as of 2008 sp1.
Sign in to post a workaround.