THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Jamie Thomson

This is the blog of Jamie Thomson, a freelance data mangler in London

SSIS: Script component debugging comes to SQL Server Integration Services 2012

One of the biggest complaints I see developers raising about SSIS since it was released in 2005 is that the only way to debug Script Components is the distinctly simplistic and old fashioned method of sticking up message boxes - there is no way to step through the code as it executes (something that Microsoft developers have generally been able to do for eons).

Happily that is no longer the case, or won't be soon anyway. In his session yesterday at the PASS Summit SSIS team member Matt Masson revealed that proper Script Component debugging (breakpoints, step into, step over, etc...) will be coming to SSIS 2012. Matt asked me to point out that nothing is certain, things may change before RTM blah blah blah but ostensibly SSIS developers can now sleep easy in the knowledge that message box debugging has gone away forever. Great news!

@jamiet

Published Friday, October 14, 2011 10:48 AM by jamiet

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Alvin Ramard said:

If script debugging is new in 2012, then what do you call what I have been doing in 2008?

I set breakpoints in my script.

I set watches on my script variables.

I stepped through my code as it exdecuted.

I did not use message boxes.

Am I missing sometning here?

October 14, 2011 9:12 AM
 

Alvin Ramard said:

Oops, my mistake in the previous comment.

I was thinking control flow, not data flow.

October 14, 2011 9:23 AM
 

Phil said:

The alternative to message boxes is using Dts.Events.FireInformation. Documented here: http://msdn.microsoft.com/en-us/library/ms136054.aspx. This provides various advantages, over message boxes; it prints to the output pane so you can copy-and-paste the message or refer to it at design time, and if you leave it in the script you won't hang the package!

October 17, 2011 9:45 AM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Powered by Community Server (Commercial Edition), by Telligent Systems
  Privacy Statement