When you create a new SQL Server Integration Services (SSIS) package you may find yourself wanting some functionality that the built-in tasks cannot accomplish. This situation is where the Script Task comes into play. This task can accomplish anything that can be done with any .NET programming. Interestingly, the Script Task is not a scripting language at all. In SSIS 2008 you can use VB.NET or C# to write complete coding solutions to perform just about any task your imagination can come up with.
When you drag over a Script Task and double-click it to open the Script Task Editor, you first see three nodes listed on the left: Script, General, and Expressions. Expressions are discussed in later lessons of this book (see Lessons 17, 29, and 30). In this lesson, we want to focus on the General and Script nodes.
Under the General node you see the name and description of the Script Task. This does not affect the code in the script; it is used for ease of reference when viewing the tasks in the Control Flow. The name shows on the tasks in the Control Flow. The description is usually a longer line of text describing the purpose of the Script Task. It is a best practice to always change the values of these fields to values that will make it easy for anyone to see and understand the function of the task.
In the Script node you have four properties to set.
The first is the ScriptLanguage. VB.NET is used for all of the examples in this lesson
EntryPoint is the ...