• yocki (2/25/2014)


    Hi Experts,

    What are the effects of adding SYSADMIN Server Roles ?

    I have this user called "SDE". It has PUBLIC Server Roles. Then I add SYSADMIN. All of a sudden, all application that use SDE cant query data.

    One known effect is that this query "SELECT * FROM city" must be reworded as "SELECT * FROM SDE.city" to make it works.

    I dont think that adding SYSADMIN server role is dangerous. Maybe some one here can explain otherwise...

    thanks

    This is one of the many reasons why you should ALWAYS use the 2 part naming convention for all objects in queries. Also, adding the SYSADMIN Server Role to a user is horribly dangerous. [font="Arial Black"]NO ONE [/font]BUT DBAs SHOULD HAVE THE SYSADMIN ROLE.

    --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)