Re: Separate Schemas for Data and Application?

From: Juan Carlos Reyes Pacheco <>
Date: Mon, 7 Apr 2014 19:56:48 -0400
Message-ID: <>

Depending how big is your software, you may prefer to separate different system in different schemas,
one for amount of units of code
two to use a different tablesplace, because if you have a p roblem and you are restoring a datafile the other systems don't get affected. three for organization and privileges

the problem are the grants you have to do, there is not a grant all between schemas.

What is a table API?

2014-04-07 16:11 GMT-04:00 Jeff C <>:

> 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.

Received on Tue Apr 08 2014 - 01:56:48 CEST

Original text of this message