 |
 |
Archives of the TeradataForum
Message Posted: Fri, 16 Sep 2005 @ 13:18:51 GMT
Subj: | | Re: User Setup: SECADMIN vs SYSDBA |
|
From: | | Meade, Cornelius |
I was wondering if anyone would respond to this... I do not think there are any specific pros/cons in any real sense... Your decision should
be driven by what your security goals are... I would say however that it is generally thought to be a good practice to segregate functions
related to the creation and ongoing administration of user accounts to a particular account that is secured and tightly controlled... As an
example, If you would want to allow for someone with access to SYSDBA to be able to move/allocate space but perhaps not be able to create/modify
accounts then you would setup the account accordingly...
Cornelius Meade III
EDS - Consulting Services/BI/CRM
| |