Kurt Brink

My feedback

  1. 1,434 votes
    Sign in
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  585 comments  ·  SQL Server  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Kurt Brink commented  · 

    Imaging if you will a customer premise installation that needs to link to a separate and different type of database engine. Now imaging trying to debug that without SSMS debugger. Installing Visual Studio is not an option. SSMS Debugger is critical. Removing it from SSMS was a mistake. Huge mistake. Please provide at least a Debugger add-on option to SSMS.

    Kurt Brink supported this idea  · 
    An error occurred while saving the comment
    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.

Feedback and Knowledge Base