QUERYTRACEON and sysman privs - by ChrisAdkin

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 794226 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 7/17/2013 3:58:53 AM
Access Restriction Public


I am a free lancer and on various different engagement I have found that the use of trace flag 2301 and 4199 can make a tremendous difference to query performance in a very postive way. However using these trace flags via QUERYTRACEON requires users to have the sysadmin privilege, which in businesses which are security senstive is a red flag. What I would like to see is a way of applying trace flags 2301, 4199, 4137, 4138 at query level without users that write reports having to have the sysman privilege. This is a massive pain point, you have introduced trace flags that can make a massive difference to performance, so that they do not cause regression it would be nice for them to be applied at statement level, but from a security perspective this is not practicle. 
Sign in to post a comment.