SSMS debugger out of sync with code

Nick Ryan 221

This question has been asked before: ssms-debugger-out-of-sync-when-stepping-through-code

I have followed the recommendations there but my debugs are still out of step. I ran DROP and CREATE on my SP then stopped and restarted SSMS (2016). I then stepped into my stored procedure and the code is aligned for the top part but if I scroll down, at a certain point in the code, it is no longer aligned. I select a line for a breakpoint and when I click add, it highlights a block of code that isn't just the instruction I selected nor is it whole lines.

Are there any other tricks that may help?

Viorel 114.7K Reputation points

2022-08-25T08:53:54.347+00:00

Does it work better if you specify a new name for your procedure, and debug it?
Nick Ryan 221 Reputation points

2022-08-25T23:11:19.12+00:00

That was worth a try but unfortunately it didn't work any better than the original SP.

1 answer

CathyJi-MSFT 21,136 Reputation points Microsoft Vendor

2022-08-25T02:51:34+00:00

Hi @Nick Ryan ,

> stopped and restarted SSMS (2016)

As fa as I know, last supporting debugging SSMS version is 17.9.1, suggest you using it, you can get it from here. If it is still not work, you can easily connect to SQL Server from Visual Studio and perform Debugging on Stored Procedures after connecting the server. Please refer to below blog to get detail steps.

How to Debug Stored Procedures in SQL Server using Visual Studio 2019

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Please sign in to rate this answer.
Nick Ryan 221 Reputation points

2022-08-25T03:33:06.94+00:00

Thanks for the suggestions but they're not helpful for me, here, unfortunately.

I don't have admin privileges on my desktop so I'm stuck with SSMS 18.4 with no debugger. If I connect directly to the SQL Server it has an older version of SSMS, 2016, as I said above. As that has debugger in it, I was trying to use that.

The customer I'm working for, at present, doesn't keep their databases as projects in Visual Studio. I guess I can script it out and make it a database project which could be worth it if I have a lot of debugging to do but seems like overkill. Still, thank you for that suggestion as it may be what I need to do if I get totally frustrated with the version I'm trying to use.

CathyJi-MSFT 21,136 Reputation points Microsoft Vendor

2022-08-25T06:56:26.31+00:00

Thanks for your reply.

SSMS 2016 is older, SSMS 17.9.1 is a better choice.
In addition, please reading the blog that I offered. It may give you an idea.

Nick Ryan 221 Reputation points

2022-08-25T20:35:38.533+00:00

I don't have the option to install other versions of SSMS, the client nor their supporting service company will allow it, so I'm stuck with the ones I have.

I'm going to look at the blog, now, and hopefully that will have something I can use.

OK, to debug from Visual Studio requires configuring the Firewall which requires elevated permissions which I don't have. Installing VS on the actual SQL Server is not permitted so it seems I'm stuck.

I'm sure your tips will help others who are permitted those levels of access but it seems I'll have to manage without a debugger. The Oracle fanboys I'm working with have a point when they say that at least the Oracle debugger is rock solid.

CathyJi-MSFT 21,136 Reputation points Microsoft Vendor

2022-08-26T05:57:52.427+00:00

Thanks for your reply.

You can ask help from someone who has permission, or ask DBA for help.

Patrick Simons 0 Reputation points

2023-08-09T06:55:11.41+00:00

The problem still exists in the Visual Studio SQL debugger that the debugger is out of sync with code. See here https://developercommunity.visualstudio.com/t/VS2022-SQL-debugging---buggy-command-lin/10331453

And vote up.
Sign in to comment

Share via

SSMS debugger out of sync with code

1 answer