Hi friends I am new to DTS as well SSIS. I have about a 100+ DTS packages to be migrated to SSIS. Just to get an Idea I downloaded and installed upgrade advisor for 2008r2. I exported one of the DTS packages on to my laptop and ran the upgrade advisor to convert it to SSIS package. After converting the DTS package to SSIS package I get to see that all ActiveX scripts are of no use(they were coded in VB script). I am not much of a scripting guy. Now how can I go ahead to covert this VB script to script task in SSIS script task? Can anyone throw light on this please? Any kind of help is really appreciated!!! Thanks, Gopal

Kind of depends on what the ActiveX Scripts did. I have seen some that were best handled by other stock SSIS Control Flow componenets or features, like Configurations, For Each loops, that kind of stuff. Can you give us some insight into the scripts, or what the package is supposed to be doing?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

I havn't started moving any DTS package yet. As I am new to this I wanted to know if there is a proper procedure to start of with? I still didnt get a chance to have a look at the script yet. I just did a trial run of upgrade advisor so I have an idea how it works. Thanks, Gopal

The proper procedure (unfortunately) is to completely understand what the old DTS package did - including those parts that aren't ActiveX scripts - and design the correct SSIS equivalent. Hopefully, your DTS developers didn't use the scripts for advanced things like modifying the package as it executed... Talk to me now on

based on what you are doing on each ActiveX task, you can use lots of tasks inside SSIS package to handle this. this is not all-in-one approach, you should dedicate on this aspect and learn SSIS tasks also script task to implement your old dts packages in new SSIS packages http://www.rad.pasfu.com

@ Todd McDermid I dont think that the scripts are that complicated as this are used mostly for ETL purposes. And from your reply I think I should really sit down with a developer to understand what these scripts are doing in the package. These packages were last edited mostly in year 2005 and unfortunately all of those developers are not with the company anymore[:(].

@Reza Thank you for your support!! Well I guess I will have a hectic schedule further.... [:)].