Skip to main content

Breakpoints in SSIS

Breakpoint is responsible to stop execution of package when specific event occur in control flow to investigate and troubleshoot  the state of the SSIS package.
There are 10 events in control flow
OnPreExecute: This event is raised by task or container certainly before it run
OnPostExecute: this event raised immediately after execution of logic of task completed.
OnError:  This event raised when an error occur in task or in container.
OnWarning: This event is raised when task or container in a state does not justify the  an error but show as a warning.
OnInformation: Basically this is called when task or container need to provide information.
OnTaskFailed: this event raised when it task fails.
OnProgress: This is called and show update when task logic executed.
OnQueryCancel : This called when executing task has been cancelled.
OnVariableValueChanged: This event raised by Integration Service runtime when value of a variable change. The RaiseChangeEvent of the variable must be set true to raise this event.
OnCustomEvent: This event raised by tasks to raise custom task-defined events.

To implement breakpoint start right click on the Control Flow and click on the EditBreakPoint on the option
After clicking on EditBreakpoint  a window open from where you can chose the breakpoint option as per given above description and click on OK now breakpoint is applied on task flow.

Now you notice a red point on the Task where you applied the breakpoint this indicate there is a breakpoint on the task. Let's run the package now you see what happen when the breakpoint is reached, a title yellow arrow is added to the breakpoint arrow.
To get some information there are some number of things can be use once a breakpoint has been used.
Start with Call Stack Window which provide information where the breakpoint is located.
Next is Breakpoint window where all breakpoint is listed there, the blue area which show all listed Breakpoints from where you can disable and enable breakpoints .
Second red area is the control panel from here you can remove the breakpoint from the task.

Output window show the progress of the package and breakpoint.

Local Window the most important window the breakpoint bring which contains information on the current status of package execution and the amount of the time in which  the package has been executing.

It contains all of the package variables which troubleshoot some odd package behavior it is related to variables not being populated as I thought they should.  This is the best way to finding out what the package is doing during execution

Popular posts from this blog

Query to find stored procedures by nested stored procedure name

Problem: Suppose we have a stored procedure which has been used in several stored procedure, I mean stored procedure usp_proc1 is nested in many stored procedures like below
So I want to find all those queries who containing usp_proc1
Solution: There is a lot of solutions, I'm giving some of them below. If you want to get the only name of the stored procedures then use the following query. Using join query on system tables syscomments and sysobjects we can get the stored procedures name which containing the particular table, nested procs or any other string. FROMsyscommentss

Check for changes to an SQL Server table?

Problem: Suppose your team is working on the under-development project so it might be possible continuous work on the database and perform changes in Table, Stored procedure as per requirement, and daily you have to update the testing server database as per changes are done in developing server database then how it is possible to trace those changes. There are a lot of solutions for this problem which is listed below Solution 1: For SQL Server 2000, 2005 and above use the CHECKSUM command SELECTCHECKSUM_AGG(BINARY_CHECKSUM(*))FROMYour_Table_NameWITH (NOLOCK); That will return the same number each time its run as long as the table contents haven't changed. Unfortunately CHECKSUM does not work always properly to detect changes. It is only a primitive checksum and no CRC calculation. Therefore you can't use it to detect all changes, e. g. symmetrical changes result in the same CHECKSUM! Solution 2: 1.Run the following query. Before executing query replace DB_Name with your database name…

Merge and Merge join transformation in SSIS

Using Merge Transformation we can combine two sorted data-set into single data-set basically Merge Transformation used to combines rows from two sorted data flows into one sorted data flow. Following tasks you may perform using Merge Transformation: 1.Suppose we have a scenario like, we need to merge data from a database table and excel means we want to merge data from two different data sources. For such type of scenario, you can use Merge Transformation. 2.If we want to merge data from two same structured tables but exists two different servers. 3.Sometimes we get an error due to data in a row, after correcting errors in the data we can re-merge rows easily. See below explanations may help you to understand Merge Transformation: I do evaluate here, you already know about the data source, data conversion, data flow, task flow, control flow etc. Note:Before Merge transformation, we need to sort the data using Sort Transformation. After sorting data add data path to Merge…