Re: TableSpace and users

Don't make a mistake by placing user objects in the system tablespace. Too many people start out making that mistake and it will affect your performance tremendously in the future.

You should distribute your data based on it's activity. In other words, dont put the two tables that get updated all the time in the same tablespace.

Generally, if a user is going to own objects over 10M, I like to seperate them into their own tablespace. Also, from the beginning, you should learn to seperate your indexes from your tables. That will speed up your queries later on.

J

Danielle Fortes wrote in message ...

>Well ... I was thinking to use Oracle´s tablespaces to separate database
>objetcs from several different applications like Human resources, Payroll
>and others ? I know the advantages but could someone tell me about the
>disadvantages to use this resource ? We develop products so I beleive that
>using tablespace I can improve distributions too.
Received on Wed Jul 29 1998 - 18:20:41 CDT