Recently our SQL Server 2005 has started showing a strange behavior.
Whenever you do an ALTER PROCEDURE to make changes to a stored procedure it
can take 2 minutes or more to complete the operation. Any suggestions?

Signature
Adam S
Aaron Bertrand [SQL Server MVP] - 30 Jun 2008 16:55 GMT
Is it possible that several users are calling the stored procedure, and your
ALTER command has to wait for their transactions to commit? You could test
this by trying the ALTER command during low/off-peak periods.
On 6/30/08 11:46 AM, in article
3CBCE426-9F18-45BD-86F7-C712492AAD8E@microsoft.com, "Adam S" <Adam
S@community.nospam> wrote:
> Recently our SQL Server 2005 has started showing a strange behavior.
> Whenever you do an ALTER PROCEDURE to make changes to a stored procedure it
> can take 2 minutes or more to complete the operation. Any suggestions?
Aaron Bertrand [SQL Server MVP] - 30 Jun 2008 16:55 GMT
(Of course you can also check for blocking and other information about your
process to see what it is spending its time doing.)
On 6/30/08 11:46 AM, in article
3CBCE426-9F18-45BD-86F7-C712492AAD8E@microsoft.com, "Adam S" <Adam
S@community.nospam> wrote:
> Recently our SQL Server 2005 has started showing a strange behavior.
> Whenever you do an ALTER PROCEDURE to make changes to a stored procedure it
> can take 2 minutes or more to complete the operation. Any suggestions?