Put Debugger back into SSMS 18
The SSMS Debugger is critical for debugging complex T-SQL Queries, please return it to SSMS 18
Joe
shared this idea
397 comments
-
Anonymous
commented
Please put back the debugger in current versions of ssms!
-
Anónimo
commented
Please put back the debugger in current versions of ssms!
-
Anonymous
commented
Please put back the debugger in current versions of ssms!
-
Anonymous
commented
The SSMS debugger is an invaluable tool - please bring it back!
-
Esther
commented
Please put back the debugger in current versions of ssms!
-
Martin Sjöberg
commented
Please put back the debugger in current versions of ssms!
-
MHOA
commented
SSMS 18 and 18.1 don't have function Debugger, I will rollback to 17.9.1 !!!
-
weeeezzll
commented
I use the debugger many times every single day to support dozens of SQL instances, hundreds of applications, and thousands of users. I could not do that without the debugger. The TSQL debugger turns a hours long support issue into a minutes long one. Virtually all of our business logic sits in stored procedures on SQL server. Some of our business processes exist entirely inside of SQL server with no outside application code. Just data pushed from PLCs to tables and jobs that tie it all together in a workflow.
This environment would be virtually impossible to support without a TSQL debugger in SSMS.
-
Mark Thornton
commented
This is a really crazy decision by Microsoft! Please reverse it. I am about to move backwards 1 release to get my debugger back!
-
JediSQL
commented
Visual Studio 2019 Community Edition has a SQL debugger that, according to a developer on my team that uses the SSMS debugger, is the same as the SSMS debugger.
-
Anonymous
commented
Reminds me of when MS decided to change the Outlook icons to a 3rd graders icon.
Is it just me, or has MS started going backwards on everything?
-
Maurice Pelchat
commented
I agree with most comments, when you write procedural, imperative code you need a debugger. What is the solution we have now, guesswork, print trace, writing trace data to table? Sorry, this is even not possible with function (scalar or table).
Really a bad idea.
BTW Visual studio is a resource hog, so I don't want to add it to my computer for that kind of work.
-
Ed
commented
Removal of the debugger renders stored procedures and triggers unsupportable.
I was forced to downgrade until I can find a functional alternative that does not require complex administration on the server to enable remote debugging in visual studio.
-
Amanda
commented
My team works with a lot of complex t-sql procedures, and the debugger is a huge productivity win for troubleshooting. Deprecating this feature without providing a viable alternative was a bad move. I will not be using SSMS18, since the debugger is so critical to my workflows. Please add it back in an upcoming SP.
-
Gigi
commented
bad, bad, bad idea. Remove debugger, who was the genius that had this idea?
ADS is not actually an alternative to SSMS for administering and deploying on Sql Server, maybe in future, but when? In 5 years? And in the meantime?
Maybe Visual Studio, but is not the speedest choice...
The only way is SSMS 17.9... :-( -
Anonymous
commented
It renders SSMS pretty much useless for me and my team ... presumably that is a conscious MS strategy - do we all now have to use VS?
-
DAVID M EVERSON
commented
This is the first time I have ever needed to ask anything from Microsoft. Please put the debugger back as it is a critical part to true professional work with complex store procedures!
-
Stefano Alberti
commented
what were you thinking?
-
Mark
commented
I agree. Many database developers might use SSMS and never have visual studio installed.
-
Daniel Smith
commented
This is an absolute outrage. No community feedback was sought before this was removed - not even a warning that it was being considered. When I read the release notes, I could scarcely believe my eyes.
Yes, we can use Visual Studio instead, but it's such a lengthy cumbersome process if you don't have a project already set up for the particular DB that you need to work with.
Almost none of my clients have Visual Studio installed on their SQL Servers, and if there's ever a need to debug something on site, this is going to be a tremendous nightmare.