HP3000-L Archives

March 2005, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Cathlene Mc Rae <[log in to unmask]>
Reply To:
Cathlene Mc Rae <[log in to unmask]>
Date:
Wed, 23 Mar 2005 15:50:02 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Grant/Revoke has nothing to do with groups within a account. it has to do
with access rights.

Your user identification within the DBEnvironment is the same as your
system logon.

The creator of the DBEnvironment is called the Database Creator (DBC) and
has Database Administrator (DBA) authority. The DBA has the responsibility
to GRANT and REVOKE authorities of other users. These authorities relate to
the DBEnvironment or to specific tables within it.

Some of these authorities allow users to CONNECT to the DBEnvironment and
SELECT, INSERT, and UPDATE against tables. If you are the creator of a
table, you have OWNER authority over that table, which lets you perform any
operation on it, including granting authorities to other users.

With IMAGE/SQL, by default, the TurboIMAGE/XL creator (or someone who knows
the maintenance word to the TurboIMAGE/XL database) and the DBA of the
DBEnvironment is set up as the DBC with DBA authority within the
DBEnvironment. Additional users can be added and authorities granted.


the allbase/sql manual is very helpful on the subject of security.

Best Regards
Cathlene Mc Rae

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2