Re: technical reasons for splitting data-model into schemes

From: <cmohan_at_iname.com>
Date: Thu, 23 Apr 1998 15:01:13 -0600
Message-ID: <6ho6m9$84j$1@nnrp1.dejanews.com>

Grouping objects belonging to a particular application into a schema is always a good idea.
Logical database backups (EXPORT/IMPORT) could benefit from splitting the database objects across multiple schemas, since you can do a user level export, which could be much shorter than the full database. And a TABLE mode export cannot export objects other than tables.

Hope this helps,
CM

In article <353C63B7.1195_at_herba-chemosan.at>, michael.pelzelmeyer_at_herba-chemosan.at wrote:
>
> Are there any technical reason - besides better organization for
> developers, dba's - for splitting a big data-model into schemas?
> The only technical consequence I know is the default tablespace and
> temporary tablespace.
> Does somebody know any splitting criterias? (e.g. group by business
> area, ...)
> TIA
> Michael
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/ Now offering spam-free web-based newsreading Received on Thu Apr 23 1998 - 16:01:13 CDT