Cannot debug a stored procedure in Visual Studio 2005 or in Visual Studio .NET after you rename SQL Server

View products that this article applies to.

SYMPTOMS

When you rename your installation running Microsoft SQL Server a different name from your host server, you cannot step into the SQL stored procedure to debug in the Visual Studio 2005 or Visual Studio .NET development environment. T-SQL debugger silently executes the stored procedure and then does not stop at the breakpoint in the stored procedure.

Back to the top

CAUSE

During installation, SQL Server stores the server name in a system table entry that the debugger uses. When you modify the SQL Server name, the system table entry updates the server name. For T-SQL debugging to work correctly in Visual Studio 2005 or in Visual Studio .NET, the computer name and the SQL Server installation name must match. If you rename the SQL Server installation, the computer names do not match the SQL Server installation name, and then T-SQL debugging fails.

Back to the top

STATUS

This behavior is by design.

Back to the top

MORE INFORMATION

Steps to Reproduce the Behavior

Verify that T-SQL debugging works in Visual Studio 2005 or in Visual Studio .NET.

Run the following command in Query Analyzer to rename your SQL Server:

sp_dropserver 'OldServerName'
go
sp_addserver 'NewServerName','local'
go

Stop and then restart SQL Server to update the @@servername global variable with the correct server name.
To verify that the server name is modified, use Query Analyzer to run the following command:
SELECT @@servername
Delete and then re-create your data connection in Server Explorer.
Open the stored procedure in Server Explorer, and then set a breakpoint.
When you try to step into the stored procedure, notice that T-SQL debugger ignores the breakpoint that you set.

Back to the top