PRB: "Set Next Statement" Does Not Work During SQL Debugging

MORE INFORMATION

When the debugger stops at a statement in the stored procedure, if you move the insertion point to a new statement and click the "Set Next Statement" option, the debugger does not move to the new statement. During SQL debugging, SQL server indicates what the next statement will be. The debugger doesn't have the same information that it receives from native debug information (.pdb, and so on) during C++ debugging. Skipping SQL statements may cause unpredictable results so this option is not implemented.