I have a 64-bit Windows Server 2008 R2 running 64-bit SQL server 2008 R2 RTM (soon to be SP2).
I have read the CSS blog regarding the SetFileIOOverlappedRange bug (http://blogs.msdn.com/b/psssql/archive/2012/03/20/setfileiooverlappedrange-can-lead-to-unexpected-behavior-for-sql-server-2008-r2-or-sql-server-2012-denali.aspx) . I believe that my SQL Server installation may be affected by this bug, and I have some questions about the fixes that the blog mentions:
1. The blog mentions both a Windows fix (KB 2679255) and an SQL one (bug # 870529 for SQL Server 2008 R2 PCU2 release). Outside of the blog, I see very little mention of the SQL fix anywhere- was that ever released in a CU or service pack?
2. If I'm reading the blog correctly, the SQL fix requires trace flag 8903 to be set in order for Lock Pages in Memory to work. If you install the Windows fix but do NOT install the SQL fix, does trace flag 8903 need to be set? (I think the answer to that is
no, but I was hoping to get confirmation.)
Any information appreciated!
Thanks,
Vince