Package with a Script Task
There is an ocean of difference between the ActiveX Script Task and the Script Task
in SSIS. Script Task has all the .NET Framework classes that can be easily accessed
through the Object Browser and of course, the intellisense support that is invaluable,
two of the many things that contribute to increased productivity. ActiveX Script
Task, as we saw in the previous chapter, has none of these. It is no wonder that
ActiveX Script Task is poorly described and the recommendation has always been to
replace it with the Script Task. ActiveX Script Task is a task that will fade away in the
next version of SSIS.
VSA (Visual Studio for Applications), the replacement for the well known VBA,
is the scripting engine that drives the Script Task in SSIS. VSA was designed to
add extensibility to the program, so Script Task adds extensibility to the SSIS
programming. It's ideal for tasks that cannot be performed by the out-of-the-box
tasks (which are already numerous) that SSIS provides. Sometimes, it can also be
used for combining the functionality of several tasks without using their graphic
counterparts. It is generally understood that a script is interpreted, but the SSIS
Script Task scripts are compiled and executed when the package is executed. The
language supported by the Script Task is presently limited to Microsoft Visual Basic
.NET (probably more developers use VB.NET as opposed to C#).
Overview of the Hands-On Exercises
In this chapter, we will be working with the following simple examples:
Simple Calculation
Given two numbers calculate their sum using the Script Task.
Pages:
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192