All this DBCC TraceON is doing is trying to set the "QUOTED_IDENTIFIER" to "ON". Our company has tens of thousands of connected Excel reports that will start throwing errors unless I grant an extremely weak username/password sysadmin privileges. I know that I can fix it on the application side by changing the connection string from "APP=Microsoft Query" to "APP=Microsoft Office 2000", but that isn't an option. We don't have the resources to fix all of those reports, this must be fixed on the server side without added this "read-only" user to the sysadmin role.
Main Topics
Browse All Topics





by: rboyd56Posted on 2007-05-16 at 10:43:14ID: 19102725
Books on line indicates that DBCC Traceon can only be run by members of the sysadmin role.
This is a good thing, because many of the available trace flags can drastically shange the behavior of SQL Server and you would not want to give this power to anyone other than a sysadmin.