Is it worth to create different users for DBAs if they are doing the same job?

  • In a team of DBAs tasks are not separated. All the team members do same kind of tasks. Do we need to create separate logins and users for each of them and assign the same role to all or all of them can use the same account? Which is better from the perspective of security.

    • This topic was modified 5 years, 5 months ago by  elea.grig.
    • This topic was modified 5 years, 5 months ago by  elea.grig.
    • This topic was modified 5 years, 5 months ago by  elea.grig.
  • It is not only about security dont forget about:

    - possibly tracking who does what

    - more problematic: isnt the user blocked when someone else is already logged in? so it might cause troubles if more than 1 needs to  do something but the user is already in use

  • One DBA can change password for such sole login and no one will connect.

    security best practices (minimum) :   each dba has its own login,  all logins are in AD group,  this group has sysadmin access.

     

     

  • I whole heartedly agree.  Each DBA must have their own login for accountability purposes.  I'll also state that each DBA login must be an Active Directory login that follows enforced password requirements policies and regular password changes.  Even if you don't agree, you should do it because it's necessary to pass a multitude of audits.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply