Learn more about SQL Server tools

mssqltips logo

Tutorials          DBA          Dev          BI          Career          Categories          Webcasts          Scripts          Today's Tip          Join

Tutorials      DBA      Dev      BI      Categories      Webcasts

DBA    Dev    BI    Categories


Breakpoints in SQL Server 2005 Integration Services SSIS

By:   |   Last Updated: 2006-11-14   |   Comments   |   Related Tips: More > Integration Services Development


In SQL Server 2000's Data Transformation Services (DTS) the tool had the ability to issue each portion of a package one step at a time.  With some custom coding, it was possible to determine variables and the package status by creating T-SQL tasks to write the items to a table.  Unfortunately, this process could become very tedious for large DTS Packages. 

Another alternative was to move portions of the DTS package that were working to another DTS Package.  Then have the problematic package call the first package and then step through the remainder of the tasks in the problematic DTS Package.  This just cut down on the number of clicks, but was also tedious.

With the many changes in SQL Server 2005, does Integration Services (SSIS) have a better way to review the variables and overall SSIS Package status at particular points in time?


Yes - SQL Server 2005 Integration Services (SSIS) has the ability to apply breakpoints to specific objects in the package.  When the SSIS Package is executed interactively in the SQL Server 2005 Business Intelligence Studio (BIDS), the breakpoint can give the Developer\DBA an opportunity to review the status of the data, variables and the overall status of the SSIS package.

How do I setup the breakpoints in SSIS?

In the BIDS, navigate to the control flow interface.  Right click on the object where you want to set the breakpoint and select the 'Edit Breakpoints...' option.  This will display the screen shot listed next section.

What are the conditions that I can set for a breakpoint in SSIS?

Breakpoints have 10 unique conditions when they can be invoked.  The breakpoints can also be used in combination.  One typical example is using both the OnPreExecute and OnPostExecute events to determine the status of the variables as the process begins and ends.

What other breakpoint parameters can be configured?

For each of the breakpoints, the Hit Count Type and Hit Count can be configured. 

The Hit Count Type values are:

  • Always
  • Hit count greater than or equal to
  • Hit count multiple
  • Hit count equals

The Hit Count value is an integer greater than 1.

The image below shows an example of these options, but is only an example not a probable configuration.

Next Steps

Last Updated: 2006-11-14

get scripts

next tip button

About the author
MSSQLTips author Jeremy Kadlec Since 2002, Jeremy Kadlec has delivered value to the global SQL Server community as an MSSQLTips.com co-founder and Edgewood Solutions SQL Server Consultant.

View all my tips

Post a comment or let the author know this tip helped.

All comments are reviewed, so stay on subject or we may delete your comment. Note: your email address is not published. Required fields are marked with an asterisk (*).

*Name    *Email    Email me updates 

Signup for our newsletter
 I agree by submitting my data to receive communications, account updates and/or special offers about SQL Server from MSSQLTips and/or its Sponsors. I have read the privacy statement and understand I may unsubscribe at any time.


Learn more about SQL Server tools