Re: Question: Database vs TableSpace (please help)

In article <5gtvga$jk6_at_chronicle.concentric.net> Nnoor_at_cris.com (NNOOR) writes:
>
>In MS SQL Server, we used the service manager (database manager in Oracle)
>to startup the server and then all databases on that server would be
>accessible. On Oracle, it seems that you startup a specific database.
>So if we have multiple databases on a server, do we start all of them
>individually? Following is an example...
>
>We have two projects going, X and Y. Both are unrelated and need there
>own databases. Under MS SQL Server, we went into Enterprise Manager
>and simply created two DB's (as simple as right clicking and choosing
>a menu item). Then we only started the server and all of the DB's on
>it were accessible. On ORACLE, I think things work different way. Is
>TABLE SPACE equivalent to "databases" on SQL Server? In our example, are
>we better off creating two DATABSES on the Oracle server and startup
>both individually or create two TABLE SPACES, one for X and one for Y,
>under the same database (e.g. default ORCL database). If later is the
>case (i.e. using table spaces), does Oracle complain about having exact
>same table names under two different table spaces in the same database?
>How do we resolve conflicts? We looked at the documentation and and it
>seems that creating a database is quite long and complex process.
>
>WHAT IS THE BEST WAY TO GO???
The closest thing Oracle has to what you are calling a database is a schema. What Oracle calls a database is a much more all encompassing concept. You can have a separate tablespace for the schemata, or not, it depends what exactly you are going to be doing. Table names are identified fully by including the schema name, so there is no problem with the same tablename in different schemata. For example, if you are user Bill, you can define a table all_users, even though there is already one in user SYS. One would be Bill.all_users, the other would be sys.all_users. You only need the prefix if there is a coding ambiguity. Tablespaces are part of physical design, not logical. See the Oracle7 concepts manual for a very good description of what all these things are. Creating the physical database is a very long and complex process, because Oracle is a much more sophisticated product than SQL server. (Of course, Rdb illustrates that some of the process complexity is unnecessary, and the more recent versions of Oracle are getting simpler, from a DBA's viewpoint, for simpler situations).

>
>Thanks very much.
>
>Regards,
>Nasir (nnoor_at_cris.com)

-- 
Joel Garry               joelga_at_rossinc.com               Compuserve 70661,1534
These are my opinions, not necessarily those of Ross Systems, Inc.   <> <>
%DCL-W-SOFTONEDGEDONTPUSH, Software On Edge - Don't Push.            \ V /
panic: ifree: freeing free inodes...                                   O