Schema Inter-dependencies

From: D-Squared <>
Date: Fri, 14 Nov 2008 06:52:42 -0800 (PST)
Message-ID: <>

I am at a new position where they host multiple applications in Oracle (9.2.07, just migrated to 10gR2) that are all hosted on the same database. The applications have references across schemas, nothing special there. My question, coming from a SQL Server environment, is what is best practices for this type of environment? I understand if multiple schemas have interdependencies if they are all a part of the same external schema. However, I question what the best practice is if I have multiple apps, (A, B, C....Z) and B has external dependencies on A's schema objects. Is this considered best practice? Or would it be better to have each app (and associated schemas) reference each other through views? For example, for the B app and B schema to get to the A apps A schema, would it be better to create view B.V_EXTERNAL_1 which selects out of A.V_EXTERNAL_1? This way if the schema in A or B changed I would not have to rewrite application code or SP's.

Also, what do I do if A is a user tracking application that holds a distinct ID of all users in the enterprise. B needs to validate the email and contact info of a user in the enterprise. Should B, a completely seperate app living on the same database, directly reference A?

Any help you could provide would be greatly appreciated! Received on Fri Nov 14 2008 - 08:52:42 CST

Original text of this message