May 22, 2008 at 7:31 am
I've followed the steps in http://www.sqlteam.com/article/debugging-stored-procedures-in-visual-studio-2005 & in the MSDN for configuring and setting up debugging SQL 2005 stored procedures in VS 2008 (seems to be the same as in VS 2005). Everything works fine until I Step Into the Stored Procedure. Everything says that a yellow arrow will appear on the left and I can start going line by line. I never get the yellow arrow.
If I set a breakpoint, it is automatically disabled. The pop-up warning says, "The breakpoint will not currently be hit. Unable to bind SQL breakpoint at this time. Object containing the breakpoint not loaded." I can't find anything about this message or problem on Microsoft's site or on the web. Any assistance is appreciated.
-Matt
May 22, 2008 at 8:55 am
Which version of VS2008 are you using?
I'm sure I saw a comparison of the versions somewhere, and not all versions support TSQL debugging.
May 22, 2008 at 8:58 am
VS 2008 Professional Edition
From the about box:
Microsoft Visual Studio 2008
Version 9.0.21022.8 RTM
I saw that only some version allow debugging, but Professional should be one of them...
June 12, 2008 at 1:09 pm
I too have the same problem.
Using VS2008 Pro on my workstation, set a Data Connection to a SQL Server 2005 remote box that I want to debug some procedures on a 2000 database.
I have followed all the information
http://support.microsoft.com/kb/908099/
But debugging a stored procedure from the VS IDE does not work.
My breakpoint is not hit and the proc runs to completion.
I can see my several PRINT statements show up in the VS IDE Output window.
If I set a Data Connection for a local SQL Server 2005, I can open a stored procedure and debug it - hits breakpoints, inspect variables, step line by line, etc... It works locally but not when I try remote.
Anyone have any ideas?
June 12, 2008 at 2:36 pm
I would like to add that I am completely local. No remote debugging here. Debugging C++ projects works fine.
--Matt
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply