Re: Single database or multiple databases
Posted by: Cameron Guill
Date: January 18, 2008 02:06PM

Upgrading 64 schemas is not that bad (I deal with hundreds). The trade off of the extra work is better security (a single school only has access to its data) and scalability improvements.

If the data is segregated between schemas you can split schemas onto different servers to split the load or into different physical locations (east coast, west coast, asia, etc). Yes, you could set up replication, but this is a simpler fix without having to have major code rewrites if your software was not built replication aware. Your tables will have fewer rows so your queries will return faster. Your backups will be faster since you can backup specific schemas one at a time. The reasons for segregation are plentiful.

The biggest drawback is you may have table cache thrashing. Your table_cache setting will need to be VERY large.

Options: ReplyQuote


Subject
Written By
Posted
Re: Single database or multiple databases
January 18, 2008 02:06PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.