New SQL Server 2008 SSIS packages were created to upgrade from SQL Server 2000 DTS packages. The old SQL Server 2000 DTS package completes in approximately ten seconds. It copies data from the server that it is running on (SQL Server 2000) to a destination server running SQL Server 2000.
The new SQL Server 2008 SSIS package takes about seven minutes to complete. So the difference from ten seconds using the SQL Server 2000 DTS package to seven minutes using the SQL Server 2008 SSIS package is unusually slow.
The SSIS package was copied and then modified to test the speed by moving data in the opposite direction (exporting from the SQL 2000 destination and importing into the SQL 2008 server). The SSIS package was able to pull the data from the SQL Server 2000 destination in thirteen seconds. This reversal of the flow of data shows that the SSIS package is able to import, but not export to the SQL Server 2000 destination in a reasonable amount of time.
The Data Flow contains an OLE DB Source using a SQL Command as the data access mode. The command text specifies the columns to retrieve.
The OLE DB Destination uses a Data access mode of "Table or view - fast load" and specifies the name of the table.
Table lock is enabled
Maximum insert commit size is 2147483647
The connection's packet size is 32767
I’ve researched data flow performance tuning, read the data loading performance guide, read some best practices, and watched some of the SSIS videos. The problem of data moving too slowly from SQL Server 2008 to 2000 persists and I’m looking for suggestions.