Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Are there any server-level security concerns I might be missing with granting a login ALTER TRACE on a SQL 2005 instance?

  • I don't care that the login can see anything that's happening on the server
  • They won't be able to actually DO anything that the trace would show, outside of what they already can (unless I'm missing something). All devs pretty much cover each other and have permission to modify db data and code anyway.

The only thing I can come up with is performance degradation from having excessive (too many, too large, etc) traces running, but this is a controllable concern for me and not a show stopper. Pretty much the only things a dev in this scenario should not be able to do are create/drop databases and modify server security (db security is fine, they're all dbo on each user db).

share|improve this question
pre sql 2000 sp3 it used to be an easy way to get application passwords. profiler doesn't display any textdata with the word 'password ' (& other hot words) since 2000 sp4 :( – Nick Kavadias Oct 19 '09 at 13:31
up vote 1 down vote accepted

See this article:

share|improve this answer
Thanks! I'd missed that article... – squillman Oct 16 '09 at 23:12

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.