Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

← SQL Server

Put Debugger back into SSMS 18

The SSMS Debugger is critical for debugging complex T-SQL Queries, please return it to SSMS 18

1,014 votes
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Joe shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

399 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Flag as inappropriate

    WTH!!!! If I can write sql queries and stored procedures in SSMS, I should be able to debug them there as well. Why do I now need to acquire and use a separate tool to do so????

  • Kelly Norton commented  ·   ·  Flag as inappropriate

    Debugger is a very useful tool when troubleshooting in customer environments, please restore this functionality

  • Daniel commented  ·   ·  Flag as inappropriate

    SSMS debugging is ways quicker and easier regarding the workflow than using SSDT and VS! Please put the Debugger back in SSMS for everyone's sake! Thank you.

  • Anonymous commented  ·   ·  Flag as inappropriate

    This has caused a lot of time wasted not having a debugger. And then trying to juggle different sql versions to try to get the debugger to work with version 17.

  • Anonymous commented  ·   ·  Flag as inappropriate

    No debugger? No problem. What a great idea! I'm mean really who's debugging code? It's 2020 - just ship it. As developers we follow the MS best practice of never testing your code.

    I propose for SSMS 19 you remove the query editor. Also you should probably remove the ability to view databases as well for good measure.

    Seriously MS are you huffing paint? Why would you remove the debugger?

  • Josue Barrios commented  ·   ·  Flag as inappropriate

    As a result of the debug tool being removed, I have been forced to have 2 versions installed, a newer one to do everyday things and an old one to debug.

  • chris commented  ·   ·  Flag as inappropriate

    Has MS gone mad? I just went to diagnose a processing issue with a client. I had to move all the code back to my local machine so I could debug it. Recommending the client go back to 17. Put debugger back.

← Previous 1 3 4 5 … 19 20

SQL Server

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice