Sounds like a good theory but we tried it and it was no better.
We have implmented a batching mechanism of 1000 records at a time and this
helps a little.
----- Original Message -----
From: Steve Galyer <[EMAIL PROTECTED]>
To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
Sent: Tuesday, August 10, 1999 9:11 PM
Subject: Re: [DUG]: DBF updating slow
> It has to do with the way in which databases build their index chains -
when
> you add records in ascending sequence the database must move through its
> chain of indexes right to the end to find the next available slot, whereas
> if you load in descending sequence then the first slot in the index chain
> will point to the next available slot.
>
> Steve Galyer
>
> -----Original Message-----
> From: Peter G Jones <[EMAIL PROTECTED]>
> To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
> Date: Tuesday, 10 August 1999 13:24
> Subject: Re: [DUG]: DBF updating slow
>
>
> >Hmmm, why descending order?
> >
> >
> >>From: "Steve Galyer" <[EMAIL PROTECTED]>
> >>Reply-To: [EMAIL PROTECTED]
> >>To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
> >>Subject: Re: [DUG]: DBF updating slow
> >>Date: Mon, 9 Aug 1999 15:21:47 +1200
> >>
> >>An old trick was to pre-sort your input records into descending sequence
> >>before loading - worked last time I tried it.
> >>
> >>Steve Galyer
> >>
> >>
> >>-----Original Message-----
> >>From: Aaron Scott-Boddendijk <[EMAIL PROTECTED]>
> >>To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
> >>Date: Monday, 9 August 1999 14:46
> >>Subject: Re: [DUG]: DBF updating slow
> >>
> >>
> >> > While appending bulk records to a dbf file we have found that the
> >>process
> >> > slows to a crawl after about 1000 records. Closing and re-opening
the
> >> > tables does not help. Shutting down the application and restarting
> does
> >> > help. We have tried dbiSaveChanges also di nothing to speed it up.
> >>
> >>You're not posting twice are ya ;)
> >>
> >>on a more serious note
> >>Does the delay seem to be increasing drive activity? if it's not then
it's
> >>not the
> >>search logic for record insertion and I'd return to checking your
> insertion
> >>code
> >>to make sure that there's not a memory leak - say something like
creating
> a
> >>new database connection each time without closing the last or perhaps
> >>object
> >>construction each iteration that could be cached for the whole
process...
> >>LIkely to
> >>need an example snippet to get any furthur down the guesstimate track.
> >>
> >>1. Open Exclusively if at all possible.
> >>2. Ensure that no live datacontrols are connected to your exclusive
> >>dataset.
> >>3. don't dbiSaveChanges every iteration since the table is exclusive
> no-one
> >>else
> >> can mess with it anyway.
> >>
> >>--
> >>Aaron Scott-Boddendijk
> >>Jump Productions
> >>(07) 838-3371 Voice
> >>(07) 838-3372 Fax
> >>
> >>
>
>>--------------------------------------------------------------------------
> -
> >> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> >> Website: http://www.delphi.org.nz
> >>
> >>
>
>>--------------------------------------------------------------------------
> -
> >> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> >> Website: http://www.delphi.org.nz
> >
> >
> >______________________________________________________
> >Get Your Private, Free Email at http://www.hotmail.com
>
>---------------------------------------------------------------------------
> > New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> > Website: http://www.delphi.org.nz
> >
>
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
