I am seeing some odd behavior from my migrated package.
On my old machine, which is a five year old machine, I had a DTS package
running on MSDE. My package would import a 100MB database Access 2000
database in about five minutes. I am now migrating my package to SSIS and
SQL Server 2005 on Windows Server 2003. I upgraded the package into BI
Studio. I have deployed the package to the server. All of the data is on
the local hard drive.
My production server is a dual processor machine. The migrated package I
would hope would run much faster on this fancy new box. Instead, the SSIS
package takes over 30 minutes to complete.
There are no complicated transforms here--just a simple data load that needs
to run every day. This is a dedicated server machine, so it doesn't have
much impact if it runs this long. It does seem to be very, very wrong for
this to take so long, though.

Has anyone else seen this?

Dana