Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

❑ There are icons at the top (see Figure 12-3) to indicate our different options, including:
❑ Continue: This will run to the end of the sproc or the next breakpoint (including a
watch condition).
❑ Step Into: This executes the next line of code and stops prior to running the following
line of code, regardless of what procedure or function that code is in. If the line of code
being executed is calling a sproc or function, then Step Into has the effect of calling that
sproc or function, adding it to the call stack, changing the locals window to represent
the newly nested sproc rather than the parent, and then stopping at the first line of code
in the nested sproc.
❑ Step Over: This executes every line of code required to take us to the next statement
that is at the same level in the call stack. If you are not calling another sproc or a UDF,
then this command will act just like a Step Into. If, however, you are calling another
sproc or a UDF, then a Step Over will take you to the statement immediately following
where that sproc or UDF returned its value.
❑ Step Out: This executes every line of code up to the next line of code at the next highest
point in the call stack. That is, we will keep running until we reach the same level as
whatever code called the level we are currently at.
❑ Stop Debugging: Again, this does what it says — it stops execution immediately. The
debugging window does remain open, however.
❑ Toggle Breakpoints and Remove All Breakpoints: In addition, you can set breakpoints
by clicking in the left margin of the code window. Breakpoints are points that you set to
tell SQL Server to “stop here!” when the code is running in debug mode. This is handy
in big sprocs or functions where you don’t want to have to deal with every line — you
just want it to run up to a point and stop every time it gets there.
Figure 12-2
Figure 12-3
In addition, there is a choice that brings up the Breakpoints window, which is a list of all breakpoints
that are currently set (again, handy in larger blocks of code). There are also a few of what we’ll call “status”
windows; let’s go through a few of the more important of these.
The Locals Window
Chapter 12: Stored Procedures
As I indicated back at the beginning of the book, I’m pretty much assuming that you have experience
with some procedural language out there. As such, the Locals window (shown in Figure 12-4 as it
403