Put Debugger back into SSMS 18
The SSMS Debugger is critical for debugging complex T-SQL Queries, please return it to SSMS 18
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.
Björn Hoch commented
I really need an alternative. Any ideas ?
Björn Hoch commented
Where is the debugger ? Even it wasn't never perfect, there were many situations I really needed this feature.
Agradecería, si alguna persona lo sabe, que opciones tenemos para depurar Transact-SQL de forma gratuita. Debido a que la versión 18 corre en Windows 8.1, emocionado la instalé, y, ¡¡¡Puff!!! me habían quitado las opciones de depurar T-SQL.
Grant Nilsson commented
The debugger is critical. Who writes perfect scripts first time. It is one of the fundamentals of SSMS and needs to be put back in
I was shocked to see that the debugger was removed from SSMS 18. I'll go out on a limb and say that NOBODY asked for that feature to be removed.
Bruce Reid commented
This was a shock! I spent a while trying to find the Debugger on some optional toolbar to no avail. Thankfully, I have an older SSMS on an other computer, which works well and will be used . Please bring back the Debugger.
BTW, having PRINT statements appear somewhere when debugger would be nice to have.
As buggy as it is, I'll move back to version 17. There is no point in using SSMS without the debugging capability. Please put it back.
Ken Grover commented
THIS IS CRAZY.... I just installed SSMS v18.0 only to find, rather NOT FIND, one of my most useful tools, the debugger. I can't believe MS is making me go back to prior versions. Yes, it's free now, but that matters to me not at all.
Who would think removing an essential function like this would be a good idea? Must be not an dev for sure...
Dinesh loganathan commented
What is the alternate for T-SQL Debugger? Do we simply need to print the values manually ?
James Menzies commented
While I agree that the debugger wasn't very good. I have always wanted to be able to query the content of table variables and temp tables for example Being able to debug PROCEDURES and TRIGGERS is a key feature.
Declaring debugging to be a premium feature based on the name of the product would also mean that SSMS should stop supporting commands such as CREATE PROCEDURE: it just doesn't make sense. Nominative determinism just is NOT a thing no matter how attractive it might be as an idea.
The implication that that we should use Visual Studio Enterprise for debugging tsql is specious. It is no better than SSMS was but the VS interface is not focused on the SQL - it just isn't ideal.
Dean McMillan commented
The lack of a debugger, although as some claim is not an 'essential' part of SSMS, is something that MS has dropped the ball on.
There would be millions and millions of lines of T-SQL running on many thousands of SQL Instances around the word every day that needs maintaining. It's not going anywhere, and it's not able to be all fixed or debugged using print statements as some claim is possible. Really, that's a massive step backwards.
If SSMS cannot provide debugging then why not ADS?
Miles Musicki commented
Please bring the debugger back!!!
Everyone complaining about debugger being an 'essential' part of SSMS. Its not. And that isn't debatable. SSMS is a management tool. Not a development tool. Sure, you can use it for that, but that isn't what its for.
the SSMS debugger wasn't good. If you're cheap and don't want to pay for a real SQL development tool, go download visual studio express.
Jeff Mergler commented
The debugger is a critical feature for SSMS.
I've already instructed my team to remain on SSMS v17.9 until further notice.
Hello guys, where did the debug execute mode disappear ? :( Best regards
David Avery commented
I was stunned to see that the new version of an evolving toolset has just lopped off its left foot! I have been using MSSQL since OS/2 days. The T-SQL debugger is essential to the intake/learning process for my client's complex SQL systems and to troubleshoot complicated SQL stored procedures. T-SQL is a language, It needs a debugger!
Umasankar Thangavel commented
I installed the SSMS 18.0 to fix the out of memory bug and ended up with Debuggerless SSMS :(