performance for multiple tablespaces
Hi,
I have 8 oracle instances with an only user for every instance.
My customer asked me to create an only instance with 8 tablespaces and 8 different users.
These instances could also further increase.
I think that avoiding creating all these tablespaces on an only instance, because I think that it would be possible to have a reduction of the performances, considering that the tablespaces INDX, TEMP and SYSTEM are the same.
According to you what problem would it be possible to verify afterwards doing an operation of the kind?
Thanks
Raf
Re: performance for multiple tablespaces
Quote:
Originally posted by raf
My customer asked me to create an only instance with 8 tablespaces and 8 different users.
Ur customer seems to be more intelligent that u. 8 tablespace is peanuts.
Re: Re: performance for multiple tablespaces
Quote:
Originally posted by adewri
Ur customer seems to be more intelligent that u. 8 tablespace is peanuts.
I'don't believe that my customer is a good dba.
please read this link:
http://asktom.oracle.com/pls/ask/f?...D:2246908001297
wait your answer!
Raf
Re: Re: Re: performance for multiple tablespaces
Re: Re: Re: performance for multiple tablespaces
Maybe your client is not a good dba, but it seems to me he is far better DBA as you are! :D
Your problem can hardly be compared to the one that Tom Kyte si dealing with in the link you provided.
Your question was:
- I have 8 customers, data for each is stored in separate database (!!!!)
- Q: Is it better to have one instance with 8 separate tablespaces, one for each customer?
The question in asktom was:
- I have one database
- I have 1000 customers, data for all of them is stored in single schema (all of them share same tables and are sepparated by some kind of client identifiers)
- Q: should I separate them in their own tablespaces (as a result there will be more than 1000 tablespaces
So if you want to apply your situation to the one at asktom, the questions to Tom Kyte should read:
-Q1: Should I have 1000 databases?
or
-Q2: Should I have 1 database with each customer in his own tablespace?
or
-Q3: Should I have 1 database with all 1000 customers data sharing one tablespace?
Tom's answers would probably be something like:
-A1: You must be kidding, right (or are you out of your mind)?
-A2: Doable, but it's hardly manageble. However it doesn't require (almost) no recoding of your aplications
-A3: The best options, however it probably involves some tables redesign and application recoding