Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 170
  • Last Modified:

Debugging SQL in VS 2010

Hello Experts,
I am trying to debug Stored Procedure in Visual Studio 2010.   It doesn't Step Into my SP code at all.  I have Sql Server 2008 installed.  In the SP, the break points are looking odd.  Please see the picture and let me know what I am missing.  It was working before.  There is no known changes I did recently.  Thank you very much in advance.
SQL-Debug.png
0
RadhaKrishnaKiJaya
Asked:
RadhaKrishnaKiJaya
  • 5
  • 3
1 Solution
 
Jacques Bourgeois (James Burger)PresidentCommented:
The fact that you see the breakpoints (red dots) does not mean anything is your are not in the proper environment and setup.

This can be due to many factors, but the most current ones are the followings:

- You are working with SQL Server Express. It does not support debugging.

- You did not activate SQL Server debugging in the Debug tab or your project's Properties window. In many solutions, the debugger must be activate in all the projects, even those that do not access the database.

- You do not have the debugger rights on the database.
0
 
RadhaKrishnaKiJayaAuthor Commented:
Thank you James!  I am not working on SQL Server Express version.  In the Project Property window, the SQL Debug is already checked.  Any other thoughts?  Thank you again!
0
 
RadhaKrishnaKiJayaAuthor Commented:
When hover the mouse to the break point I see this message "The breakpoint will not currently be hit. No symbols have been loaded for this document."
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Jacques Bourgeois (James Burger)PresidentCommented:
Then you have to rely on the sixty different possible solutions presented here and there. Here are a few links:

http://www.go4answers.com/Example/vs2010-breakpoint-not-currently-hit-26548.aspx
http://weblogs.asp.net/guybarrette/the-breakpoint-will-not-currently-be-hit
http://aspnet.4guysfromrolla.com/articles/051607-1.aspx

They are for older versions of Visual Studio or SQL Server, but the mechanism has not changed, so they should also apply to your environment.

Good luck
0
 
RadhaKrishnaKiJayaAuthor Commented:
James, I tried your links.  None of them worked for me.  Please let me know if you have any other ideas.  Thank you!
0
 
Jacques Bourgeois (James Burger)PresidentCommented:
Just to be sure. I assumed that this was already set. Are you in Debug mode? Under the Advanced Compiler options of the Compile tab of the project's Properties window, is Generate Debug Info set to Full? Some of the debugger features that worked with pdb-only in previous versions of Visual Studio require Full in newer versions, and the change is not made automatically when you convert a project from one version to another.

Other than that, it's Google or Bing. The suggestions and links that I gave you ware the ones that worked for me in the past. As is unfortunately the case with such problems, there are many other solutions on the Internet. You might be able to find one that apply to your environment.
0
 
RadhaKrishnaKiJayaAuthor Commented:
I am sorry to say, none of the experts advise work for me.  I will go ahead and close this case.
0
 
RadhaKrishnaKiJayaAuthor Commented:
This is not resolved yet.  Reason already described.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now