Hi all, Our consultant has presented a schema design which I have never seen (not that I have seen all the designs in the world) but I also failed to see the advantage.
Basically our application consists of 35 tables and all is under one schema named after the application. Granted, the application has many components such as billing tables, event tables etc. Now the consultant wants to split all 35 tables into as many as 8 different schemas! Such as a billing schema, a event schema. To me this only complicates the whole thing as now you have to manage 8 schemas and manage many grants, synonyms. Not to mention some tables are not clear cut as which component it belongs to. I just don't see what this buys us. Has anyone seen such a approach? And what's the benefit of doing so? Thanks _________________________________________________________________ Join the world�s largest e-mail service with MSN Hotmail. http://www.hotmail.com -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: oracle dba INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
