Re: One Ora SID vs. Many ORA SID's

There are pros and cons about each. With multiple instances you have to realize you are probably going to require more memory resources due to having multiple SGA's. How much depends on the size of the SGA's you create for each instance. This is particularly a problem if your server is short on memory. On the flip side, multiple instances do allow you to tune the instances with more granularity. If one instance is read only, its requirements are different from an OLTP instance. It also makes things a bit easier if you need to shut down one of the databases for maintenance, the others would be unaffected. I can't say there is an easy answer to this. You have to take a serious look at your resources and needs.

Dave

Larry.Hughes_at_experian.com wrote:

> My application has a registration database(series of tables), audit database,
> and a forsale database. I was considering having each of these in seperate
> SID's. What are the trade off's vs. have all of the tables in one SID ?
>
> The Foresale is a read only so redo log's are not needed, thus archivemode off
> would be set if it was in it's own SID. I realize we have more granularity
> with backup and restore at the database level with multiple SID's.
>
> Do I incur an abundand amount of overhead with the 3 SID's vs. 1 SID? The
> registration and audit databases should have fairly lighter transaction
> activity than the Forsale database.
>
> Thank you in advance.
>
> Larry
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Received on Tue Dec 22 1998 - 11:55:15 CST