Re: Creating schema in oracle10g express edition

uhm.. yes all you tell me is true.. but i'm sorry, i continue to think that the separation of schemas to the users are more efficient.. i want show you a simple situation: think you have a server with one oracle instance installed.. this is a web server.. if u have 20 websites resindent in (for example) iis web server, and all sites require the connection of n tables, with one schema u must share the same credential with all 20 web site administrators.. than to create separate accounts with oracle u have to create 20 separate schemas.. else if u have sql server with one database (or schema or container or u want tell..) you can create more accounts with more privileges to access specificed objects (for example specificed tables or views etc..).. same speech with db2..
it's not a limitation of oracle respect to sql server or db2 concepts? i tell you again WHY i've to create a user account to create a container!!??

hpuxrac ha scritto:

> dops wrote:
> > ok, thanx very much for your all reply ;)
> > my only difficult is the concept of creating a user to create a
> > schema..
> > this concept isn't present in sql server or db2 becouse in this
> > databases i've to create a "library" or a "database" to create an
> > container of all objects (tables etc..)
> > In oracle if i've 50 schemas have 50 users.. omitting the fact that a
> > single user can be used to connectiong all schemas object through
> > permissions settings.. but the fact remains that I must create 50 users
> > on the database :(
>
> Well then on the sql server side you have 50 separate databases to
> manage? Each with it's own set of transaction logs right?
>
> To me anway the oracle side makes more sense.
>
> You don't often create 50 separate schema's in oracle to host the
> tables for a set of application. Usually you have a couple of schemas
> and you keep adding additional tables to the important schemas.
>
> An integrated application should keep going after mostly the same
> tables right? Even applications that are only somewhat related can go
> after ( not necessarily should but can ) tables in the same schema.
>
> Do you have someone that is designing your applications? Some kind of
> application architect or senior developer? It might be a good idea to
> spend some time talking with them.
Received on Mon Nov 20 2006 - 16:16:15 CST