14,499 questions
Use debug PRINT and SELECTs. This is what I have used for debugging for the last twenty years. I found that every time when tried to use a debugger, I spent more time on getting to work than I gained from productivity.
How to debug stored proc on mssql running on linux
![](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(304, 3%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFM%3C/text%3E%3C/svg%3E)
Francois Mercier
0
Reputation points
Debugging stored procedure on a SQL server 2022 running on Linux server reports the following error
Unable to start program ‘MSSQL:://IP Address/?/sys/=0’ Operation not supported. Unknown error: 0x80004005.
As described in https://github.com/microsoft/mssql-docker/issues/410
How to solve this problem ?
SQL Server | Other
{count} votes
-
LiHongMSFT-4306 31,566 Reputation points2024-10-10T01:20:16.1433333+00:00 Seems like a connection issue. Can you ping the server successfully?
-
Francois Mercier 0 Reputation points
2024-10-11T11:47:26.92+00:00 Yes, sql is working with all clients (Sql Management Studio, Visual studio, JDBC client, Odbc client, ...) The problem is only when debugging
Sign in to comment
1 answer
Sort by: Most helpful
-
Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator2024-10-09T20:57:22.42+00:00 -
Francois Mercier 0 Reputation points
2024-10-11T11:49:17.35+00:00 See below
-
Francois Mercier 0 Reputation points
2024-10-11T12:00:55.0666667+00:00 This is indeed what we also developed, stored procs for debugging and table to receive these logs, but I wanted to avoid modifying some stored procs to add this logging and use a debugger. But I had hoped that Microsoft had better tools than its competitors regarding debugging (yes, I also spent time to make Oracle Debugger working)
The workaround we have found is to backup the DB and restore it on a local Windows server, and so use the Windows debugging capabilities.
The silence of Microsoft for this feature request is a bit frustrating
-
Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator
2024-10-11T21:10:10.0933333+00:00 This is indeed what we also developed, stored procs for debugging and table to receive these logs, but I wanted to avoid modifying some stored procs to add this logging and use a debugger.
Usually, I debug on my local instance where I can modify procedures as I see fit.
If I have to do this in production or in a database where there are other users, I may re-create the procedure with a new name, so that no one else gets affected. (A debug SELECT will of course wreak client codes that expects something else.)
The silence of Microsoft for this feature request is a bit frustrating
To be fair, it is not a trivial matter, not the least from a security perspective in case you have a remote SQL Server instance. I recall that when I used a debugger that I had to open port 135 (RPC) in the firewall on my machine. That's a not a port you want to have open.
Sign in to comment -