List,
I would like to have your opinion on the following scenario.
We are having an application which is used by different customers (around 15
customers). On an average each customer will have around 1,000 transactions
per 5 minutes. Now, is it better to have a separate database for each
cust
Hi Maheswara,
I would think seperate databases would be the way to go, if for no other
reason, you can bring one customer offline without affecting the others.
-Rocky
--- "Rao, Maheswara" <[EMAIL PROTECTED]> wrote:
> List,
>
> I would like to have your opinion on the following scenario.
>
> We
Having separate databases gives you some flexibility. You can manage them
separatly, for instance you can upgrade the database to a newer version in
phase. Also, if you lose a database only one customer is affected. Do all
the customers always use the same application (same version)? If one
cu
Hi Doug , (and all) ,
Just curious - the PS environment, do you put finance and HR on the same DB?
Do you share the sysadm user? I'm new to this PS stuff, so this interests
me. Also, in production, do you have the PS databases separated from the
other OLTP databases?
Thanks
Mike Lanteigne
Just my $.02. I agree separate tbs for different app schema's. However, I would
separate applications to their own db, especially if they are 3rd party apps. You
have much less control on COTS. Some run their install scripts as sys. I don't agree
w/ it, but I am not going to rewrite their
Actually I meant Dick, nor Doug, sorry
Mike
> -Original Message-
> From: Lanteigne, Mike [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, March 28, 2001 8:35 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: What is best practice - differenet schema/differ
