Re: Who should own Oracle tables?

Matt,

Thanks for the reply. I appreciate the help. Since you seem to know your stuff I would like to ask you a couple of additional questions if you don't mind =).

: I usually have an account created that holds the tables for an application
: area (e.g., PERSONNEL_MGR, REGULATORY_MGR). That way, ownership of the
: tables is transferred from the developer(s) to a central repository for
: that application area. Privileges can be granted to the users from that
: *_MGR account. Sometimes, it is desirable to remove access from a
: developer once a system goes live. It reduces the risk of "oops".

1. Do you create a separate _MGR acct for every application? Or do you have one _MGR acct that owns the tables of all apps?
2. I followed your suggestion and created an OWNER acct that will own all application tables. Only problem is that I cannot assign privledges to roles, only to the OWNER's tables. What privledge can I give this acct to allow it to give privledges to roles as well as its tables? I am trying to avoid giving this acct DBA privledges since application developers will be using it.
3. What tablespace do you put each application's tables in? Do you create a separate tablespace for each application? If so does this improve the efficiency of data access? What is a good size tablespace to start with?

Thanks for the help,

Eddie Hernandez                              North Broward Hospital District
Programmer/Oracle DBA                        1608 SE 3rd Avenue 
hernb0_at_nbhd.org                              Ft. Lauderdale, FL 33316
***************************************************************************