Reblog: Building the Script Component

SQLKover update: For some reason, this was my most popular blog post on the old LTD site. Over 110,000 views. People must be building them script components. 

The problem

From time to time I have to script out some logic using a Script Component in a SSIS package. Business as usual for most developers, but since I hardly have a .NET background, it’s always a very stressful experience (I may be over exaggerating a bit). Sometimes it happens I write a little piece of code with a small bug, it happens to the best of us.

For those who haven’t noticed: you cannot store -1 in a byte. Anyway, the wonderful designer that is the Visual Studio shell fails to warn me of my little indiscretion. Leaving me with a script component that won’t compile.

nocompile
Yes, that’s SSIS 2008 folks!

The matching errors aren’t helpful either.

errors

The solution

The solution is elegant yet simple: we force the designer to tell us what’s wrong by building the code inside the script component.

button

This results in a blue squiggly being added to the code, together with a decent explanation.

buildscript

The moral of this story: if the script component is giving you a hard time, hit that build button!

Koen Verbeeck

Koen Verbeeck is a Microsoft Business Intelligence consultant at AE, helping clients to get insight in their data. Koen has a comprehensive knowledge of the SQL Server BI stack, with a particular love for Integration Services. He’s also a speaker at various conferences.

Leave a Reply

Your email address will not be published. Required fields are marked *