|
|
|
SSCrazy Eights
Group: General Forum Members
Last Login: Friday, May 18, 2007 3:36 PM
Points: 9,870,
Visits: 1
|
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Monday, October 20, 2008 4:01 PM
Points: 135,
Visits: 53
|
|
According to Books on line and I quote verbatim
"The following table lists and describes the trace flags that are available in SQL Server 2005.
260, 1204,1211,1222,1224,2528,3205,3625,4616,7806"
There is no mention of trace flag 3226. So one could say that the official answer to this question is wrong and the correct answer should be "you cannot suppress the message".
The questioner should also take note of the fact that trace flags may not be supported in future editions of SQL Server.
Regards
Tim Brimelow
|
|
|
|
|
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, June 18, 2009 8:34 AM
Points: 83,
Visits: 37
|
|
This would be the answer to my dreams -- except it isn't working for me.
I have SQL Server 2000. I was overjoyed when I saw the answer to this question. I've asked it myself on this site, probably 3 years ago! There was no apparent solution.
The blog entry to which the question refers says you can do this by executing
DBCC TRACEON (3226);
So I put that into a SQL Server Agent job (so it will run every time SQL Server starts) and have now run it at least 3 times (twice manually and once after a restart), and I'm still getting my usual 400+ backup success messages every hour.
Can anyone tell me: (1) Have they tried this on SQL Server 2000, and (2) Is my method of doing it valid?
|
|
|
|
|
SSC Journeyman
Group: General Forum Members
Last Login: Thursday, June 18, 2009 8:34 AM
Points: 83,
Visits: 37
|
|
Since I didn't get a reply to my post, I posted the question in the "main" section. Short answer: in my case, it only works as a startup parameter, not in DBCC.
I decided to document it here for anyone that might come looking again. Full thread at http://www.sqlservercentral.com/Forums/Topic421160-357-1.aspx .
|
|
|
|
