Separate Schemas for Data and Application?
- From: Jeff C <backseatdba@xxxxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 7 Apr 2014 13:11:48 -0700
I wanted to know what everyone's opinion is on separating schemas. Like
having a data only schema, a code only schema and then a schema the
application logs into and executes code from the app schema. Or do you put
all data and code in a single schema and then a separate schema for the
application to run as?
Also do you implement table API's? If you do then this probably nullifies a
lot of these options.
Let me know what you do.
Thanks.
Other related posts:
