RE: Rule of thumb for new schema vs. new database?

Brian,

   As mentioned by others, you will have more flexibility regarding tuning, recovery, and upgrading if you setup a separate instance. If you have home grown apps, using the same instance may be viable, depending on the requirements of your applications - sharing data, volume of activity, recovery, etc. Recovery scenarios may be rare, but in the event that you need to recover the entire instance, you'll prefer dealing with one application instead of many.

   If this is a 3rd party application, I would be surprised if the vendor would support sharing an instance. Heck - we have vendors that insist that the database be on it's own separate box, let alone the same instance.

Jay

-----Original Message-----
Hi Again,

I have a meeting tomorrow with one of our project managers who is going to request a new schema or database. He wants my advice on which is best for his needs. Now...as I've said before I'm a neophyte DBA and do know the difference between a schema and a new database. I'm inclined to suggest just a new schema, but now I'm wondering to myself what kind of 'rule of thumb' is there is for this kind of decision.

When would it be preferable to create a new db vs. just a schema in an existing db?

Thanks for you help.

Brian Peasey

**DISCLAIMER
This e-mail message and any files transmitted with it are intended for the use of the individual or entity to which they are addressed and may contain information that is privileged, proprietary and confidential. If you are not the intended recipient, you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this communication in error, please notify the sender and delete this e-mail message. The contents do not represent the opinion of D&E except to the extent that it relates to their official business.

--
http://www.freelists.org/webpage/oracle-l