This morning the SQL Server Release Services Team has pushed out new cumulative updates for SQL Server 2008 R2.
Cumulative Update #13 for SQL Server 2008 R2 RTM
- Knowledge Base article: http://support.microsoft.com/kb/2679366
- Build number: 10.50.1815
- Number of fixes: 9
- Relevant for builds of SQL Server between 10.50.1600 and 10.50.1814
Cumulative Update #6 for SQL Server 2008 R2 Service Pack 1
- Knowledge Base article: http://support.microsoft.com/kb/2679367
- Build number: 10.50.2811
- Number of fixes: 20
- Relevant for builds of SQL Server between 10.50.2500 and 10.50.2810
As usual, I'll post my standard disclaimer here: these updates are NOT for SQL Server 2008 (where @@VERSION will report 10.00.xxxx).
Hi Aaron,
Sorry for commenting on an old thread, but this is the only place where I've seen any good information about SetFileIoOverlappedRange bug # 870529, outside of the CSS blog. I have an SQL Server 2008 R2 installation that I think may be affected by the bug, and I have some questions about the fixes that are available.
The CSS blog (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) mentioned both a Windows fix and an SQL one. Outside of the blog, I see very little mention of the SQL fix- was that ever released in a CU or service pack?
We have the Windows fix (KB 2679255) installed. If we have this fix installed but NOT the SQL Server fix installed (if it even exists), do we need to set trace flag 8903 in order for LPIM to work? (I think the answer to that is no, but I was hoping to get confirmation on that.)
Any information appreciated!
Vince
Eliassal, I can see x86 builds for both cumulative updates. For some reason Microsoft thought it would be clever to hide builds for platforms you're not running, so my guess is you're not seeing the x86 builds because you're accessing the kb article from a different machine running x64. Please be sure to click the link that says "Show hotfixes for the platform and language of your browser"
While setting up System center Configuration manager, I was asked to setup CU6, in the request page there is only CU6 or 13 for x64 and no update to 32 bit, does this mean I need absolutly to switch to 64 bit
Sorry Tim, you're asking the wrong guy – I do not use the report designer at all. You're probably best off opening a case with Microsoft support if you've exhausted all troubleshooting and are confident that the hotfix is the cause (have you searched for the actual error message you receive?). Be aware that their answer might be for you to roll back the hotfix.
This hotfix is crashing a report designer called datadynamics. What is the best way to eliminate the conflict?
Thanks for clearing that up for me Aaron.
Chris
So it looks like any SQL-only fix that is going to be published will come in Service Pack 2 (that is what PCU2 means). So still I would not expect to see them in any CUs in the meantime.
Aaron,
There is a chart in the CSS blog showing both a Windows fix and an SQL one. See here 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
Chris
Isn't that a Windows bug that affects SQL Server? If so, why would you expect a fix supplied through Windows Update and also a fix supplied through a CU?
I don't see the SetFileIoOverlappedRange bug # 870529 in either of these though the Windows fix KB 2679255 came out last week.
I wonder if this has a lower priority now that the Windows fix is out.
Chris