Watching Variables in Ssis During Debug

Watching variables in SSIS during debug

I believe you can only add variables to the Watch window while the debugger is stopped on a breakpoint. If you set a breakpoint on a step, you should be able to enter variables into the Watch window when the breakpoint is hit. You can select the first empty row in the Watch window and enter the variable name (you may or may not get some Intellisense there, I can't remember how well that works.)

Debugging in SSIS

Debugging SSIS packages within the BIDS environment is not the same ball game as working with Visual Studio.

You may find it useful to consult the reference Debugging How-To-Topics(SSIS)

If you have developed your very own custom component, i.e. from within visual studio, then you should be able to debug the specific functionality of that component within the Visual Studio environment, prior to making the component available for use within BIDS.

You are not able to debug the internal .NET code that makes up any of the other built in SSIS components (i.e. the FTP Task) within BIDS so I doubt a custom component will be any different.

SSIS - search or filter Execution Results in Debug Mode

You can enable the Inbuilt Logging Feature and select SQL Server as Provider Type .SSIS execution will be logged in a table named sysdtsLog90(SSIS 2005 in MSDB database) or sysssislog (SSIS 2008).

Select the details which needs to be logged in the Database

Now when you execute your package u can find the information iof SSIS package execution details in the table .

In order to find the task which got failed ,you can just query the table

 select EVENT,source,starttime,endtime 
 from sysssislog 
 where EVENT like '%OnTask%'or EVENT like '%error%' 

Of you can use a 3rd party tool BIDS HELPER to visualize the SSIS Performance

Visual Studio 2015 Debugging: Can't expand local variables?

It might be a bug. Please file a Connect bug with a repro if you have one.

In the meantime, you might be able to workaround the problem by setting the debugger options to use the legacy debug engine: Tools -> Options -> Debugging -> General: check both "Use the legacy C# and VB expression evaluators" and "Use Managed Compatibility Mode".

That workaround has worked for me every time. But please, do still file the bugs!

debugging SSIS packages - debug.writeline

Use Dts.Events.FireInformation instead.

---

Related Topics