dont remove debugging from ssms 18.0
what is ssms:
SSMS is an integrated environment for managing any SQL infrastructure, from SQL Server to Azure SQL Database. SSMS provides tools to configure, monitor, and administer instances of SQL. Use SSMS to deploy, monitor, and upgrade the data-tier components used by your applications, as well as build queries and scripts.
--> build queries and scripts
if you remove debugging from ssms --> https://cloudblogs.microsoft.com/sqlserver/2018/10/03/ssms-18-0-public-preview-released/
ssms will be degraded to an simple editor with some nice helpers to write sql but not an integrated enveronment to write scripts and common database objects.
every developer will write good and working code, but sometimes the developer need help. this help will be provided by eg an debugger. and the debugging stuff is one of the most important woolset what every! serious developer need. ssms is not an admin ui to manipulate database objects and so on. it is a very good tool to write tsql scripts, functions and so on. and exact at this place the developer (like me) need help. eg: if you write an udf with some complex code and you need deeper informations inside during runtime --> what is the way to get this infos --> use an debugger! --> if you don't have an debugger, the developer can use the print functions --> but this a real, real bad idea for serious development --> so pls try using print at an udf --> it's not allowed --> bingo --> so you have to change the function to an procedure to use printinf for debugging. real, real horrible and follow up, it makes degrade this tool to an admin script tool and it lost an great and very essential feature, which is useful for every serious developer (and also admin)! pls think about this decision! thanks dietmar
Pietro maria Cascio commented
Anche io penso che SSMS deve avere un debug integrato , altrimenti si è costretti ad usare durante lo sviluppo due ambienti SSMS per l'editing e la progettazione e Visual Studio per il debug e non è proprio comodo…..
William John Adam Trindade commented
Does anyone read what is written here? The impression I have is that we are talking to the walls.
The other ticket (https://feedback.azure.com/forums/908035-sql-server/suggestions/35881492-put-debugger-back-into-ssms-18) has been waiting for moderation for a few months.
We appreciate your feedback.
OMG. Microsoft seems to be doing everything in its power to anger developers. Simple step debugging is essential.
It does NOT entice me to go to azure cloud, I'll switch to AWS or IBM clouds first. Or just goto sqlite or something else just because I'm so ****** that microsoft took this out.
it just like the installer projects in vs. then the "want some candy" approach to the awful install shield limited edition. then they pull the plug on that too.
Kurt Brink commented
As a product integration company, we utilize SQL Server to connect to customer specific databases. Our product is deployed within the customer premise. We install SSMS 17.9.1 as having the ability to debug ODBC sql queries of customer specific databases is an absolute requirement. Removing the debugger from SSMS in version 18.* prevents us using any versions of SSMS newer than 17.9.1. Installing Visual Studio just so we could debug T-SQL is not an option. In our world, we try to install the least amount of software required and adding Visual Studio is a deal breaker. If Microsoft provided a separate T-SQL Debugger, that would certainly be a viable and desirable option as it would enable us to install SSMS and if we need to debug T-SQL, then just install the T-SQL debugger. If Microsoft is unable or unwilling to provide a separate T-SQL Debugger, then we will be forced to look to other products.
Rick Fonner commented
The ability to step through your SQL logic is necessary!
George Padvorac commented
Not having a debugger is a show stopper for me and I will go back to 2016. Its really hard to understand the logic in removing this key feature. Not to mention other things seem to be half baked in 2018 such as "auto complete in dropdown lists in places like the table and query designer. Auto complete has been around for 20+ years and we are used to entering a few key stokes to get the item needed and then hitting the tab key. None of this works now and it feels like 1990. Really bad management by MS. Arrow keys don't work here either. Seriously?
Tarek Madwar commented
SSMS 17 is not working with sql server 2019,
and because i want the debug button,
i will role back to SQL server 2016 only.
will not implement sql server 2019 until debug button is back to ssms
Dominic Wirth commented
The alternativ is Visual Studio but for me this is not a solution. Please bring back the debugging option. How should we DB Administrators do our job? Execute-and-hope?
There is a similar issue here:
Just this Moment I discovered Debugging is removed. I stop all rolling out of SSMS 18 immediately in my Company. We will use SSMS 2014.
I don't see any Advantage, why on writing and testing T-SQL we should use a different application.
There was exactly tthe same topic climbed to 400+ votes rapidly, and then swiftly put to "moderation".
Here is the link of it:
when gathered 400+votes it suddenly became "This idea is awaiting moderator approval"
Good job, M$
Derek McLoughlin commented
Please put debugging back into SSMS 18.
Harry Potter commented
The board moderator will not permit this item to have more than 99 votes. I was the 100th vote and it showed 100 but then upon page refresh it went back to 99. Hogswarts!
Debugging T-SQL from SSMS was essential. Going back to v17.9 and will not upgrade until this functionality returns. Complete blunder by Microsoft.
Ulysses B Brown Jr commented
I just wanted to add my comment just in case volume matters. First a question, if you have a SQL Instance with SSMS 18 but don't have an environment with Visual Studio installed, what are you to use to Debug T-SQL? You cannot debug T-SQL with Azure Data Studio or VS Code.
As a T-SQL Developer, having the ability to debug a complex statement from withing SSMS was very-very useful. Most server instances I've had to connect to via RDP do not have a Dev IDE like VS installed. They only have SSMS available to use to step-through some T-SQL in order to try and resolve an issue that might be an issue that only surfaces under certain specific data scenarios. The debugger was critical for these situations. I just ran into a use case and discovered that SSMS 18.4 does not have the debugger.
Why remove something so useful. I want it back in the product.
William John Adam Trindade commented
Why this other ticket is censored?
We need a real alternative. Visual Studio is not one, because it crashes almost every time... VS simply closes without warning when I try debug TSQL sp.
Please re-evaluate adding the debbuger again or fix SSDT to make it more stable.
I will downgrade. I don't use all the new stuff for Azure, etc. and the bugs never impacted my work. Not having a debugger with no alternative definitely impacts my work.
Hey MS, why don't you survey the users about these bright ideas before you just arbitrarily remove important features!
B. Nichols commented
Since they removed debugging in SSMS 18, I am downgrading back to 17. Why is it Microsoft just can't give us the tools we want, and stop trying to force us to do things the way they think they should be done!?? They better shake this attitude if they have ANY hope of getting Linux users onboard!
Mark A. Fox commented
This would have been the most requested feature if the moderator did not remove the last request that already had nearly 400 votes before it was pulled. The old request (link below) now just says: "The idea is awaiting moderator approval"
The debugger is not optional. Rolling back to version 17