Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Designing an application log for performance (NEWBIE)

Designing an application log for performance (NEWBIE)

From: David Thom <davidt_at_npsinc.com>
Date: Wed, 28 Apr 1999 10:00:03 -0500
Message-ID: <7g77o4$h5q$1@uuneo.neosoft.com>


We're jumping into a project with Oracle8 (our first with Oracle), and need some guidance on how to design an application "log" table for high-performance/high-volumes (not the Oracle internal transaction log, but an application table which is receive rows of application-level data).

We're estimating as many as a million rows/day, initially running on two clustered 4-way Alphas each with 2GB RAM under Digital UNIX 4.0e.

Are there any Oracle-unique considerations when adding huge numbers of rows to an existing table? What if this same table also needs multiple indexes? Are there design considerations which would help minimize the performance hit of updating the indexes?

Any guidance appreciated!

David Thom
NPSi Houston Received on Wed Apr 28 1999 - 10:00:03 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US