Make DBCC Trace flags available as OPTION QUERYTRACEON - by GV1973

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 780194 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 2/27/2013 9:00:26 PM
Access Restriction Public


Please make trace flags 652, 8744 available at query level (using OPTION QUERYTRACEON) this way without requiring sysadmin rights users can use it, there won't be messages printed for the query and it will be only active for a given query.
DBCC TRACEON(652 /*652: Disable page pre-fetching scans*/)
DBCC TRACEON(8744 /*8744: Disable pre-fetching for ranges*/
If there are other traces which can be query level but not available today please consider them too.
Sign in to post a comment.
Posted by Microsoft on 3/1/2013 at 9:29 AM
Hello Gokhan. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you. -Walter A Jokiel, Program Manager, SQL Server (
Posted by Martin Smith on 2/28/2013 at 2:04 AM
This doesn't address your main point but regarding your statement that one of the benefits is "there won't be messages printed for the query" you can already achieve this with `DBCC TRACEON(652) WITH NO_INFOMSGS`