Home Forums SQL Server 2005 SQL Server 2005 Security login permissions to run the SQL Server Profiler RE: login permissions to run the SQL Server Profiler

  • October 6, 2012 at 10:20 am

    #1546433

    naga.rohitkumar (10/5/2012)

    ya i too agree with u ALTER TRACE

    but if we use default master the user can able to have access on all databases know

    i mean it for running a profiler only to one or seleted databases

    Based on that, I have to ask... Why do you want to give a "user" privs to run SQL Profiler? Unless they have the ability to create a Server Side Trace (and I personally believe that no user should have that level of privs), a user could easily cripple the server by creating a client side trace.

    To wit, I believe that no user should have more than PUBLIC privs on production databases and their access should be limited to only what they can return using a stored procedure that they've been given EXECUTE privs on.

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