Home Dashboard Directory Help
Search

SSMS 2012 - Debugger fails to navigate through dynamic SQL query and step by step from there. by Maurice Pelchat


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 776807
Opened: 1/17/2013 9:02:38 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

SSMS 2012 T-SQL Debugger doesn't handle correctly dynamic SQL debugging which SSMS2008 was doing fine.

When the debugger reach the Exec statement, a windows for Dynamic SQL displays but with no code visible (first bug) and trying to do F11 displays an error message (second bug).

There is no way to continue debugging without closing the windows and doing F11 again.
Details
Sign in to post a comment.
Posted by Microsoft on 4/8/2013 at 10:50 AM
Hello Maurice. This issue is being tracked in a different connect item. Please look for updates here: http://connect.microsoft.com/SQLServer/feedback/details/736509/sql-server-2012-rtm-management-studio-cannot-debug-sp-executesql Please let us know if you have any questions. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Microsoft on 2/21/2013 at 1:54 PM
Hello Maurice. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Maurice Pelchat on 1/17/2013 at 9:09 AM
It is apparent that SSMS 2012 is a big rewrite, but Microsoft should give more priority in correcting bugs introduced in this rewrite.

I have submitted many annoyances introduces by this version like the one related to selecting through shortcuts the database context. The combo box previous behavior is completely broken, and since this is a feature constantly used by DBA this a MAJOR ANNOYANCE. I have received no feedback since and there are MANY MONTHS since I submitted it. Even if I use a french version, I'm pretty sure that these bugs exists in all languages. They should AT LEAST TRY IN ENGLISH VERSION and give a feedback.

Sign in to post a workaround.