Re: I would like to know how experts look at this problem

You don't give enough information.

An oracle database in a client/server environment with a few concurrent users will easily handle that sort of load on almost any modern hardware.

On the other hand you then start talking about transaction queues which Oracle has to be specifically configured for (its advanced queueing), Oracle handles multiple concurrent transactions admirably well - a queue implies serialization of work.

So what is your design going to be client/server n-tier, multimaster replication, what version of Oracle and what platforms.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
"Gregor" <crec_at_nospam.xs4all.nl> wrote in message
news:3e65e79c$0$120$e4fe514c_at_dreader4.news.xs4all.nl...


> Hello all,

>

>

>

> I am a software developer, with some knowledge about databases, but I

would


> like to know how experts look at this problem.

>

>

>

> I am developing a Management Information System for a customer. This

> customer has 2 DBA's how disagree with me. This is the situation:

>

>

>

> My application retrieves it data from an Oracle database. There are 150

> concurrent users.

>

> There are 3 different levels of users:

>

>   1.. Directors

>   2.. Local managers

>   3.. Shop managers

>

>

> There are 5 directors and 5 local managers. When one of these users asks

for


> information, the query returns approximately 500.000 record (sorted

> alphabetical!). The queries for the shop managers only return

approximately


> 10.000 record (sorted alphabetical).

>

>

>

> Shop managers use the system daily and others use it weekly.

>

>

>

> The DBA's of my customer say that this system is never going to work,

> because it is too much for the database server.

>

>

>

> I think that with the right hardware and the right configuration of the

> oracle database it should work.

>

>

>

> What do you think?????????????

>

>

>

>

>

> Thanks,

>

> Gregor.

>

>

>

> P.s. I have been told that if oracle is processing one big transaction, a

> small transaction in the queue, has to wait until it the large transaction

> has finished. I know this is the case with MS Access, but I thought Oracle

> was more sophisticated (preemptive)?

>

>

>

>

>

>

>

>