Re: High transaction rate Oracle DB

Tom-

Stuff like this ought never be characterized as "easy". But, with the right design and implementation it is not unreasonable. You haven't told us anything about the nature of the application, but I surmise that it is OLTP. We don't know how much data will be hit at a time, nor do we understand the patterns involved, like selectivity of index, sparsity, etc. Were I on site, I would want to know about the hardware, memory, nature of client, network type and topology, competing applications (especially as it relates to network contention). How much logic will be put on the server in the form of stored procedures and triggers? Is this two-tier? Might there be a transaction processor involved?

What about skewing of key values? That can affect performance pretty dramatically. Is the disk striped? Raid? Is this 24x7? Can you afford an outage every week to do maintenance?

Anyway, there are a million issues involved, not the least of which have more to do with the sql you run than how the instance is tuned. And if you are new to Oracle, don't jump in the deep end without some serious help. And no rookies on a big-gun, high visibility project.

But easy... naahhhh.

Roger

Roger Snowden
Sr. Systems Engineering Specialist
Oracle Corporation
rsnowden_at_NOTus.oracle.com <-- to reply, remove the obvious

Tom Laszewski wrote:
>
> I am putting together an Oracle database with 500+ concurrent users with
> 8 large tables of
> about 30 gigabytes. The transaction rate against the 8 large tables
> will be about 100 Oracle
> transactions (one select,insert,update ordelete) per second. Does this
> sound like it can be done fairly easy? Any hints?
>
> Thanks
Received on Sat Dec 19 1998 - 12:14:42 CST