c**t
发帖数: 2744 | 1 import cvs file into one table (SQL Server), there are three indexes
created on the table. Is there any way to import faster?
Now it usually takes 30minutes to finish. about 10 minutes load data,
then build indexes (I guess). |
s******n
发帖数: 45 | 2 what's the current process?
【在 c**t 的大作中提到】
: import cvs file into one table (SQL Server), there are three indexes
: created on the table. Is there any way to import faster?
: Now it usually takes 30minutes to finish. about 10 minutes load data,
: then build indexes (I guess).
|
c**t
发帖数: 2744 | 3 App ftp csv file onto netshare;
scheduled job to pick the file and run dts
It takes about half an hour to finish the job. >60% to build indexes...
I have turned on "lock table", useless. :-(
【在 s******n 的大作中提到】
: what's the current process?
|
s******n
发帖数: 45 | 4 Sounds pretty slow to me. Are you dropping the index and rebuilding after
the import?
【在 c**t 的大作中提到】
: App ftp csv file onto netshare;
: scheduled job to pick the file and run dts
: It takes about half an hour to finish the job. >60% to build indexes...
: I have turned on "lock table", useless. :-(
|
c**t
发帖数: 2744 | 5 It will take longer time to rebuild index...
【在 s******n 的大作中提到】
: Sounds pretty slow to me. Are you dropping the index and rebuilding after
: the import?
|
s******n
发帖数: 45 | 6 DTS is supposed to be the fastest way to get data in. It's actually using the
SQL Server OLE DB IFastload interface to achieve best performance. Assuming
the process is IO-bounded, you may consider storing the data file, index
file, and log file on different disks.
【在 c**t 的大作中提到】
: It will take longer time to rebuild index...
|
k*******d
发帖数: 237 | 7 BCP will be a good choice
【在 c**t 的大作中提到】
: import cvs file into one table (SQL Server), there are three indexes
: created on the table. Is there any way to import faster?
: Now it usually takes 30minutes to finish. about 10 minutes load data,
: then build indexes (I guess).
|
