I'm using a simple DTS package to import large text files
(600-900MB/25MM-30MM rows) into a database. The database has plenty of space
for these files, but when I import a file, it starts off very slow (about 1k
rows/5 seconds) and gradually speeds up until the row count flies by at
speeds you usually see for smaller files.

This behavior is making the import take a really long time and I was
wondering if someone here had some insight into why this is happening and
what I can do to fix it.

Thanks!

I cannot explain why the speed up but things to help

1. Destination table has no indexes or triggers
2. The Data File is not going to expand during the import i.e. enough
space.
3. No users accessing the table.



--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"MatthewR" <MatthewR (AT) discussions (DOT) microsoft.com> wrote

Those are things I should have specified:

The destination table has no triggers or indexes
The data file is 30GB in size and has over 1/2 of that space remaining
I am the only person accessing the table (or even the database)


"Allan Mitchell" wrote:

And the transation log?

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com


"MatthewR" <MatthewR (AT) discussions (DOT) microsoft.com> wrote

Ah, another good question.

The transaction log is currently 8356 MB. I don't recall what I started it
at, but it was certainly a round number. The transaction log is set to grow
at 10% at a time, hence the growth.

Could I possibly need to expand the transaction log?
If so, how would that explain the behavior I'm seeing?
Is there a way to not log the import?

"Allan Mitchell" wrote:

You cannot "Not log the import" but what you can do is minimise the amount you do log. Set the recovery model to SIMPLE. You need
to understand the ramifications of this.



--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com


"MatthewR" <MatthewR (AT) discussions (DOT) microsoft.com> wrote

Well, I learned something new today. Never heard of different recovery
models. I read about them in Online Help and then checked the setting in EM,
but apparently it's already set to "Simple".

"Allan Mitchell" wrote: