liveBook · Manning

Breakpoint

As explained in 100 SQL Server Mistakes and How to Avoid Them

A breakpoint is a marked execution location at which a debugger pauses program execution.

A breakpoint marks a code location where execution pauses, allowing you to inspect variable values and determine which path the logic followed. section 7.3

Pause before the calculation

Set a breakpoint on the line calculating @CostOfBidPerc in CalculateCampaignSummary. Start debugging with F5, inspect @AvgCPM and @AvgBidPrice in the Locals window, then continue execution. section 7.3

Visual Studio supports conditional breakpoints, but T-SQL does not support breakpoint conditions. Use the available pause and inspection workflow instead. section 7.3

How 100 SQL Server Mistakes and How to Avoid Them covers it

How deep it goes
Explains placement, continuation, variable inspection, and stepping, but stops short of supporting conditional T-SQL breakpoints.
Examples
Demonstrates pausing CalculateCampaignSummary before calculating @CostOfBidPerc and inspecting campaign summary variables.
What it assumes
Assumes familiarity with stored procedures and Visual Studio debugging controls while teaching breakpoint use directly.
What you can do after
Diagnose stored-procedure behavior by pausing execution, inspecting locals, and stepping through code.
How it connects
Connects breakpoints with debugging, stored procedures, execution paths, Locals windows, and stepping.
Cover of 100 SQL Server Mistakes and How to Avoid Them
liveBookmanning.com
Read 100 SQL Server Mistakes and How to Avoid Them on liveBook Get the book at manning.com

Also explained in

Compare how 6 books explain breakpoint →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of 100 SQL Server Mistakes and How to Avoid Them. The section links point to the parts of the book it draws on.