Thanks for the question, Joanne
.
Asked: May 02, 2000 - 1:21 pm UTC
Last updated: May 02, 2000 - 1:21 pm UTC
Version:
Viewed 1000+ times
You Asked
We are a small company providing billing software to
approx 80 customers, on MS Access and MS SQL Server platforms
currently, adding Oracle in the next release. App has approx 200
tables. Just getting started.
Have made SYSTEM user the owner of the app tables, granting
select, insert, update, delete on each to a role, then granting
that role to each app user.
Should we create another user to own the tables, if so, why?
Thanks for any advice you can offer. If there are resources that
you are aware of that discusses this issue, please let me know
where to find...
and Tom said...
You should not use either SYS or SYSTEM for anything. These are 'special' Oracle users (especially SYS, more so then SYSTEM). The attributes, priveleges, and characteristics of SYS and SYSTEM can and will (and have) change over time -- possibly affecting your application.
SYS and SYSTEM should only be used for Oracle supplied tables and packages.
Is this answer out of date? If it is, please let us know via a Comment