September 9, 2008 at 10:47 am
I see this every once in a while in my SQL Server Logs, I am wondering what it is and what triggers it.
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 9, 2008 at 10:55 am
Someone (or some application) turning on the trace flag that allows trace output to go to the console rather than the errorlog.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
September 9, 2008 at 11:00 am
So would it happen when SQL Agent runs a integrity check? But someone has to set it? I know nobody is doing it manually.
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 9, 2008 at 11:28 am
Its not needed to run DBCC CHECKDB - not sure whether Agent sets it or not in 7.0 or 2000.
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
September 10, 2008 at 12:24 pm
I'm running SQL2K sp4 and this message is not in my logs, even after a server restart. Possible it's in your startup parameters?
-- You can't be late until you show up.
September 10, 2008 at 12:29 pm
It is not in my startup parameters. Waht about starting a trace, wouold that trigger it (Profiler).
Warm Regards,
Arthur Lorenzini
Sioux Falls, SD
September 10, 2008 at 12:39 pm
Google yielded this, among others. Some interesting stuff that may help you solve the mystery.
http://www.sqlservercentral.com/articles/Administering/howtousetraceflagsinsqlserver2000/1860/
-- You can't be late until you show up.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply