I dont see a point to pl/sql and data tables separate. Its over engineered. first off you need direct grants for this and you can't use roles which can be a hassle. 2nd you need addition grants so its 'work'. I dont see any value in this whatsoever. I do like repository schema (data/code, etc...) application user schemas where people login. so you can control privileges and they cant run drop table etc... that is pretty standard. On Mon, Apr 7, 2014 at 4:11 PM, Jeff C <backseatdba@xxxxxxxxx> wrote: > 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. > > >