August 24, 2004 at 10:51 am
Hello Everyone,
what is the most restrictive server role required to run the profiler on a SQL Server 2000?
Regards,
Carl
August 24, 2004 at 11:44 am
It seems to be sysadmin fixed server role.
But why do we need this level of security to be able to run the profiler?
In my own opinion, another role should be created for that purpose.
Regards,
Carl
August 24, 2004 at 12:25 pm
For SQL Server 2000 you must be sysadmin to run Profiler. There are several reasons for this, Profiler can show a great deal of information about the data and the database that you probably want to keep away from the eyes of most users, and Profiler can also impose a significant overhead on the system. Those who have system admin rights are assumed to know how and when to use Profiler.
Incidentally, in SQL 2005 I understand that permissions will be much more granular and that non-sysadmins will have access to some Profiler functions. But as usual, be careful what you ask for, with that increased granularity and control, expect to deal with increased complexity.
/*****************
If most people are not willing to see the difficulty, this is mainly because, consciously or unconsciously, they assume that it will be they who will settle these questions for the others, and because they are convinced of their own capacity to do this. -Friedrich August von Hayek
*****************/
August 24, 2004 at 12:56 pm
I'm aggree with you.
But its one thing to be able to see private informations and degrade performances and another thing to be able to:
- create tables
- create databases
- configure the server
- delete logins
- kill process
- manage disk files
- etc.
I think that more granularity is a requirement here.
Regards,
Carl
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply