Search

Make DBCC Trace flags available as OPTION QUERYTRACEON by Gokhan Varol

Active

2
0
Sign in
 to vote
Type: Suggestion
ID: 780194
Opened: 2/27/2013 9:00:26 PM
Access Restriction: Public
0
Workaround(s)
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.
Details (expand)

Product Language

English

Category

Developer Tools (SSDT, BIDS, etc.)

Proposed Solution

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.
If there are other traces which can be query level but not available today please consider them too.

Primary Benefit

Improved User Interface

Other Benefits



Virtualization

 
File Attachments
0 attachments
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 (wajokiel@microsoft.com)
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`
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement