Learn more about SQL Server tools


Latest from MSSQLTips

Free SQL Server Learning

Get your SQL Server in shape this Summer with Spotlight on SQL Server

Encrypting Data with SQL Server

Physical and Virtual Performance Monitoring with SQL Diagnostic Manager

Breakpoints in SQL Server 2005 Integration Services SSIS

MSSQLTips author Jeremy Kadlec By:   |   Read 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 Update: 11/14/2006

About the author
MSSQLTips author Jeremy Kadlec
Since 2002, Jeremy Kadlec has delivered value to the global SQL Server community as a SQL Server Consultant at Edgewood Solutions, co-founder of MSSQLTips.com as well as Baltimore SSUG co-leader.

View all my tips

print tip Print  
Become a paid author

join MSSQLTips for free SQL Server tips     

Learn more about SQL Server tools
Post a comment or let the author know this tip helped you.

       All comments are reviewed, so stay on subject or we may delete your comment.

*Name   *Email Notify for updates

       Note: your email address is not published. Required fields are marked with an asterisk (*)

Get free SQL tips:

*Enter Code refresh code     

Sponsor Information



Get Free SQL Tips










BI Professionals


Q and A

Today's Tip







Tip Categories

Search By TipID



First Timer?


Free T-shirt



User Groups

Author of the Year

More Info








Copyright (c) 2006-2015 Edgewood Solutions, LLC All rights reserved
Some names and products listed are the registered trademarks of their respective owners.