I've done this without any problems.

The RowCount component is specific to SSIS - it's one of the transformation components available in the data flow.

However, it's not really appropriate for this scenario, since to use it,...

I posted a sample and walkthrough here. http://agilebi.com/cs/blogs/jwelch/archive/2007/11/18/changing-destination-tables-with-the-ole-db-destination.aspx

You can use an Execute SQL Task for this in the control flow. Execute a SELECT COUNT(*) FROM Table, and store the resulting count in a variable. Create a second...

Here's the KB article on this:

http://support.microsoft.com/kb/918644

Using a set based update in SSIS is considered a best practice by most of the experts I know of. The OLE DB Command is painfully slow on large recordsets....

Basically, it means there was something in the package that couldn't be converted. I would recommend recreating it in SSIS, since that will take more advantage of the new features....

You need to use an asynchronous output from the script task to add new rows. I posted a similar example (of using a split to output multiple rows) on my...

Have you opened the generated package in Business Intelligence Developers Studio (BIDS)? It's not uncommon for the migration tool to "convert" DTS packages by creating an Execute DTS Package task...

If you are using a SQL Server Integration Services job step type, go to the Configurations tab, and enter it in the Package Password box.

If you are using a CmdExec...