Re: design advice

josephcurwen_at_despammed.com (curwen) wrote in message news:<cc68edc4.0402270028.291371ff_at_posting.google.com>...
> Hi all,
> I'd like to have you opinion about the following performance/design
> issue:
>
> a logging system is generating a lot of records every our,(about
> 500k/day)
> I need to store them in a huge Oracle RAC system
> a Java web application connects to the data and executes queries on
> them, mainly on last entered set of records
> queries on informations stored more then 3 months ago are quite rare
>
> as first guess I managed to store them in a table indexed by a
> primary key, let's say in the table 'LOGS'
> the problem is that table is going to grows very big,
>
> have you got 'best practice' ideas to handle the situation in a better
> way?

Look at partitioning.

http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96524/c12parti.htm#CNCPT112

Remember to post the version and platform. http://members.cox.net/oracleunix/readme-cdos.htm

>
> I thought about moving data priodically in a 'LOGS_ARCHIVE' table ,
> for example using a Oracle job
> is it necessary?
> PS I can't use Oracle standard file archiving support, I need data to
> stay on tables
>
> thanks in advance
> jc

jg

--
@home.com is bogus.
1888?  http://www.signonsandiego.com/uniontrib/20040227/news_lz1c27pubeye.html