Re: Oracle for a near real-time App

Yes, give it tons of RAM and cache as much as you can (cache tables, large shared pool and db block buffer cache). Tune your SQL for fast access - use indexes and high selectivity, and even consider caching rowids for frequently accessed rows. Obviously steer clear of any 'bulk' operations or over-indexing.

Biggest problem you might have, though, is not speed, but predictability. I've worked on a lot of real-time systems in the past, and *guaranteeing, consistent* performance would not be easy with Oracle and the sort of OSs it's designed to run on.

I guess it all depends on you definition of 'real time'.

Steve Phelan.

James Woodger wrote in message <353CAD9D.7CCA_at_sympatico.ca>...
>I'm considering using Oracle Server for a near real-time App. Would
>anyone raise any red flags, based on their own experiences?
>
>Since the database is small, it's likely that I'll be able to make it
>memory resident. Are there any other database strategies I should be
>considering in the circumstances?
>
>I'd appreciate a copy of comments to my Email at jwoodger_at_sympatico.ca
>
Received on Tue Apr 21 1998 - 10:41:24 CDT