> Create a view which is a union of several (many) batch tables.
The question here though is how Oracle will operate with Selects. If the
view does UNion first, before the where clause, then operation will be
much slower than applying where clause and UNION of result sets.
> Bulk load each batch of data into a smaller (empty?) table & then
> enable the indices. Add the new table to the view. You may want to
> trade off ease of deleting a day's or week's data against load speed
> by making each constituent table for a time period, so it is quick to
> delete (not quite so quick to load).
Way too many tables. DELETES related to input loading are very rare. (Only
when for some reason, there is belief entire input was corrupt). DELETEs do happen
to single records when with over time, correlation of spatial attributes indicates that
a measurement is bad. The nature of the error source though mean correlation
with any input set unlikely. Errors are expected to be more or less random. In
general, once in, the data is expected to stay forever...
Using a loading table and then migrating data to the main table over time, does
sound good scheme though.
----------------------------------------------------------
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/
