As per existing split schema approach we have put Data Scheme and Rules Schema in single data base. Infrastructure teams questions is why cant we have ruleschema created in separate database so that if required we can take backup and restore in any other regions. Is this approach followed for any other clients ? or is it feasible ?
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
PRPC 7 supports split schema within one database and has not totally eliminated queries that join rules to data.
Thus, PRPC 7 do not support completely putting rules and data in separate databases.
If customer only care about work and work history, and they don't need any reports to join assignment to work, then move the org-specific work and work history tables to an org-specific database. They need to use XA drivers and an app server that supports 2-phase commit (WAS, Weblogic, JBoss).
If they consider assignment, attachment and attachment linkage to be organization-specific, they have got a bigger challenge --- those tables must be shared.