Woody wrote:

>> I need to create a table where every days i will add around 2 000 000
>> > rows, to delete them every night (after compiling them to produce some
>> > statistics). so the table will receive around 60 000 000 rows every month
>> >
>> > I m afraid that this will cost a lot of IO on the hard drive and will slow
>> > all the systems ... also i m not sure that after i delete the row, the
>> > space will be mark as free for futur insert ... is it possible to keep
>> > this table in memory ? if not what i can do ?
>> >
> Why not look at it from a different perspective. Instead of saving all the
> records, computing the statistics and then deleting the records, why not
> simply keep a running calculation based on available data? Or keep running
> totals of what you need and compute the stats when needed? If the data isn't
> going to be kept anyway, does it really matter if the records get saved? If
> you update fields that keep running totals of available/needed information,
> you can always run statistics based on those at any time.
>
> Anyway, just a thought..

Some calculations will need the full table to give accurate averages and the like?
Create a RAM disk and just store a couple of single day files, one live and one
processing the previous day. No need to 'delete' the content, just delete the
file when finished?

--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php