This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 2%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Has anybody been successful in configuring SQL Server 2019, Visual Studio, and SSDT to enable T-SQL debugging? I have verified that all ports are open on our firewall but I still get this error: "Unable to start T-SQL debugging, Could not connect to computer <hostname>,1987. The debugger cannot connect to the remote computer. The debugger was unable to resolve the specified computer name." I should note that we are using a non-standard port for SQL Server - 1987. I also installed Visual Studio on the server with SQL Server, and I get the same results. I appreciate any help you can offer on what my problem is or how I can further troubleshoot. Thank you in advance!
A Microsoft extension to the ANSI SQL language that includes procedural programming, local variables, and various support functions.
Hi, we have not get a reply from you. Did the answers could help you? If there has an answer helped, do "Accept Answer". If it is not work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 44%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
I had the same issue and it was solved by using the default 1433 port on the instance. The problem arises when you use a custom port for SQL Server. Not optimal for us as we want to use custom ports, so if anyone have a solution please share.
Hi @mh53j_fe ,
Try below steps. For the details, please refer to Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor
Best regards,
Carrin
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @mh53j_fe ,
SSMS needs to be able to find your SQL Server by DNS. When you connect to the DB in SSMS, you can use (local), but (local) does not resolve on your network so the debug program can not find it. Try connecting to localhost or your computer's name on the "Connect to Server" screen. You should not have to run as administrator. Quoted in Unable to start T-SQL Debugging. Could not connect to computer (“*****”)
Best regards,
Carrin
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thank you Carrin-Msft, but this doesn't help.
I am able to connect to the database using the hostname with SSMS 17.x, SSMS 18.x and Visual Studio with SSDT on both my laptop and on the server.80292-t-sql-visualstudio.pdf
I have attached a picture from Visual Studio where (1) I connect to the external database, (2) select the database, (3) select the stored procedure, and (4) run debug on the stored procedure. The picture includes the error message.
Thank you for your help.