Nothing is going to cope very well with that ...
It's sounds rather specialised - can you do it with disabling the indexes?
Sounds like you really need a different design to beat the problem, it's
either that or buy a very fast unix box ...
What speed trade offs can you accept??
eg Slow insert versus fast query.
So is 2 billion records in a table enough, how often are the bulk inserts
done?
Myles.
-----Original Message-----
From: Phil Scadden [mailto:[EMAIL PROTECTED]]
Sent: Monday, 16 July 2001 4:34 p.m.
To: Multiple recipients of list delphi
Subject: [DUG]: Single MASSIVE table. Recommendations?
I have application that uses single MASSIVE table (100 million records and
growing). Records get added to it in lots of few hudred thousand to 2-3
million at a
time. Needless to say its a problematic beast. Currently in Oracle which is
struggling
with index re-enabling after bulk load. Interbase as far as I can see hasnt
a bulk
load option at all.
I had wondered about using one of the simpler, single table components out
there to see if they could hack the pace. (eg easytable) Any
recommendations??
----------------------------------------------------------
Phil Scadden, Institute of Geological and Nuclear Sciences
41 Bell Rd South, PO Box 30368, Lower Hutt, New Zealand
Ph +64 4 5704821, fax +64 4 5704603
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
