Re: Oracle Design

Your second solution won't work at all. The fact that the tables are in different table spaces doesn't matter. The first solution sounds OK -- you will only qualify the tables with user1.tablename or user2.tablename. But why not use the same user and just qualify the tables with set1_tablename and set2_tablename. Its the same effect. Or why not just use the same set of tables but use a column called "set" to partition the data. You could then create views on each table for each set that would show only the data for that set.
Chris

BT wrote:

> Hi,
>
> Would like to check out some stuff regarding the database design in Oracle.
> I have this application which requires the access to different sets of
> identical tables in Oracle. How shld I go abt implementing this w/o causing
> any conflicts becos the tables across the different sets would share the
> same names.
>
> First thot, was to create a new user for each set of tables. This would
> resolve the potential naming conflict but somehow this does not sound very
> correct.
>
> Second thot, was to use different table space to seperate the sets of
> tables. To access the tables in each set, change the default tablespace for
> the user to reference that tablespace containing the required tables. Is
> there any potential problem with this design?
>
> Would welcome and appreciate any advice or help regarding this matter.
> Thanks!
>
> Boon TUN>

-----------== Posted via Newsfeeds.Com, Uncensored Usenet News ==----------  http://www.newsfeeds.com/ The Largest Usenet Servers in the World! -----------== Over 66,000 Groups, Plus a Dedicated Binaries Server ==---------- Received on Thu Mar 11 1999 - 23:11:22 CET