SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,069 questions
In T-SQL debugging, "Step Into" behaves like "Step Over."
![](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(41.6, 37%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Jungsooooo
0
Reputation points
- visual studio 2022 (17.11.5)
- Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64) Oct 8 2022 05:58:25 Copyright (C) 2022 Microsoft Corporation Developer Edition (64-bit) on Windows 10 Enterprise 10.0 <X64> (Build 22631: ) (Hypervisor)
During the debugging process of a procedure, when using Step Into on the EXEC procedure statement, it behaves like Step Over. However, the results (e.g., return_value) are displayed correctly.
What could be the reason for this behavior, and how can it be resolved?
On the 6th line, when I use Step Into (F11), [usp_user_insert] does not open, and it skips directly to:
SELECT @return_value as 'Return Value'.
{count} votes
-
Erland Sommarskog 112.8K Reputation points MVP2024-11-22T22:08:18.9+00:00 I never use the debugger, do I don't know. I always work with debug PRINT and SELECT. Given the nature of SQL, a traditional debugger is less useful. So my recommendation is to not spend much time on getting this to work.
Another note: you are running the release version of SQL 2022. You should download the most recent Cumulative Update to get access to many bug fixes and enhancements.
Sign in to comment
Sign in to answer