ActiveX&VB.net versus transformation tasks

Hello all -

Working on DTS packages we used to have two different ways of exporting data to spreadsheet... We could do it by a single transformation task or either writing an ActiveX script, after running a procedure.

I am able to cover the first way already, while dealing with SSIS... But, I wonder if it is worth to research on how I would write a vb.net code to load data into a spreadsheet (considering we are advised to try vb.net instead of ActiveX while working on these new packages).

It is always a huge discussion to know what is the best way of doing something so my point here is to hear some of you and decide if I just keep exporting data by doing transformation tasks or if I will ever go trying to deploy a vb.net code to do that... What is the best on performance, etc...?

Thanks in advance for all your help as always.

SSIS contains an Excel Destination that you can use.|||

Hi Phil.

Thanks for your reply. I know about the excel destination which is very much the same of doing transformation tasks in our old dts packages.

My question was... If I generate the spreadsheet through a vb.net code like we used to do with ActiveX scripts for dts packages, will I win anything on performance or something else? Example...

Working on dts packages we would always choose to generate a spreadsheet through procedures combined with ActiveX scripts because the procedure would have a query plan and would have less overhead, comparing with data transformation tasks. I don't know about SSIS because I am new here If you can add any insight to this I really appreciate that.

Thanks again.

|||I think you'll see better performance from the built-in Excel Destination. Script components are generally slower than pre-built components.