Piotr Lipski
2007-12-03 09:44:46 UTC
Hi.
There is a SQL 2005 Server Std with linked server to iSeries. There is a
task that imports a huge (~30mln recs) table from iSeries each weekend.
I can do the import in two different ways:
1.
INSERT INTO [local].[sqlserver].[table]
SELECT ... FROM [linked].[server].[table].[name]
or
2.
Define SSIS package that does more or less the same thing - standard
data transfer between two sources, with column mappings etc. etc.
The amount of data is the same each week (+- 1%)
Method 1 takes ~4h20m to execute. Method 2 takes ~2h50m.
Both use the same odbc driver for iSeries.
I prefer using the first method because it's easier to implement and
causes no problems when moving the import job between servers but method
2 seems to be much faster. So I wonder what causes the difference and
how to speed up method 1 (if possible at all).
There is a SQL 2005 Server Std with linked server to iSeries. There is a
task that imports a huge (~30mln recs) table from iSeries each weekend.
I can do the import in two different ways:
1.
INSERT INTO [local].[sqlserver].[table]
SELECT ... FROM [linked].[server].[table].[name]
or
2.
Define SSIS package that does more or less the same thing - standard
data transfer between two sources, with column mappings etc. etc.
The amount of data is the same each week (+- 1%)
Method 1 takes ~4h20m to execute. Method 2 takes ~2h50m.
Both use the same odbc driver for iSeries.
I prefer using the first method because it's easier to implement and
causes no problems when moving the import job between servers but method
2 seems to be much faster. So I wonder what causes the difference and
how to speed up method 1 (if possible at all).
--
PL
PL