Microsoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 or SQL Server 2008 fix release.
Symptoms
Consider the following scenario:
-
You enable the row versioning feature on a database in SQL Server 2008 R2 or in SQL Server 2008.
-
You configure the database to use the snapshot isolation level.
-
You run many transactions that update the database concurrently.
In this scenario, error messages that resemble the following are logged in the SQL Server Errorlog file.
Error message 1
<Date> <SPID> A time-out occurred while waiting for buffer latch -- type 2, bp 0000003DDEFCBC80, page 3:58642854, stat 0xc0000b, database id: 6, allocation unit Id: 72057594048806912, task 0x000000717CC2A748 : 0, waittime 300, flags 0x3a, owning task 0x00000062F0A6CE08. Not continuing to wait.
Error message 2
<Date> <SPID> Timeout occurred while waiting for latch: class 'APPEND_ONLY_STORAGE_FIRST_ALLOC', id 0000006196214E30, type 4, Task 0x000000002CA45948 : 0, waittime 300, flags 0x1a, owning task 0x00000062F0533288. Continuing to wait.
Error message 3
<Date> spid#,Unknown,Error: 845<c/> Severity: 17<c/> State: 1.
Cause
This issue occurs because the formatting of the version store pages starts after allocation. However, the pages are latched. Therefore, high contention for pages occurs.
Resolution
Cumulative update information
SQL Server 2008 Service Pack 3
The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2673383 Cumulative update package 4 for SQL Server 2008 Service Pack 3Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 R2 Service Pack 1
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2544793 Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2534352 Cumulative update package 8 for SQL Server 2008 R2 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
This issue might not occur if you increase the number of data files for the Tempdb database to maximize disk bandwidth. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2154845 Recommendations to reduce allocation contention in SQL Server tempdb database
References
For more information about row versioning-based isolation levels, visit the following MSDN website:
General information about row versioning-based isolation levels
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
