January 23, 2014 at 2:09 pm
Our production server has been generating rather frequent (at least once a day) 825 errors and I am considering enabling trace flag 818 for more information on the issue.
KB article 826433 indicates that this flag could be helpful in diagnosing i/o problems, but the article only explicitly indicates SQL2000 - 2008 as applicable.
Does anyone have any experience using trace flag 818 in a production environment on SQL2012 SP1?
January 24, 2014 at 9:52 am
dave-L (1/23/2014)
Our production server has been generating rather frequent (at least once a day) 825 errors and I am considering enabling trace flag 818 for more information on the issue.KB article 826433 indicates that this flag could be helpful in diagnosing i/o problems, but the article only explicitly indicates SQL2000 - 2008 as applicable.
Does anyone have any experience using trace flag 818 in a production environment on SQL2012 SP1?
I don't have experience with TF 818. But I can tell you that if a client of mine surfaced an 825 error I would STRONGLY recommend getting ALL production SQL Server stuff off of that server and A) patching EVERYTHING in the IO stack and B) performing extensive IO testing (both SQLIO and SQLIOSIM) to validate the IO subsystem was once again bulletproof. I would also be checking with IO system vendor(s) for issues too. 825 is a signal that IO errors DID HAPPEN, but one or more retries got "good data" back. Don't play around with that!
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply