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

Oracle 8.0.4 allows for a read-only tablespace with the appropriate overhead savings, therefore eliminating the need in this case for multiple SIDs.

But in terms of different availability profiles there could be many other reasons to separate the tables into multiple SIDs. The driving reason should be business or ecomonic. For example if you split the SIDs onto multiple servers there is the server licensing cost that becomes less motivating. If you can keep them all on the same server, then It may be better to split them up, we do this too for many reasons; full exports are quicker and maybe even simultaneous, there are different user groups with different demographics causing different backup time requirements, and different security profiles (eg payroll is very sensitive).

In article <75oet6$eo1$1_at_nnrp1.dejanews.com>, 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 - 18:18:23 CST