I just learned an interesting fact about SQL 2k8 SSIS script tasks this morning. Generally, I don’t use Script Tasks because I can accomplish with other tasks what most of our devs do with the Script Task. But yesterday I found a situation where my only option was the use of this bugger. So I open it up, expecting to see the same Public Main Sub setup I saw in 2005 and instead got the below:
So I’m banging my head against the wall, trying to understand why Microsoft would make such a major change to SSIS between 2005 and 2008 and asking myself why no one on the internet bothered to complain about it. (Understand, I’m operating on about 3 1/2 hours of sleep from several late nights of trying to finish a 35,000 word project.) Then, this morning, I have an epiphany. Doh. This is the setup for a Visual C# script, not a Visual Basic script.
Sure enough, when I open the Script Task this morning, first item under the Script tab is “ScriptLanguage” and if you click in there, you can alter it from Microsoft Visual C# 2008 to Microsoft Visual Basic 2008. Yay. I’m not going to have to spend a week that I don’t have to learn a brand new programming language. I can save C# for the new year and a new project where I won’t have any choice but to learn it.
Now if I can just find my pillow, the day would be perfect.
