Article ID: 2809338 - View products that this article applies to.
This issue occurs because the log pool uses a global pointer to a memory object for all databases.
When many threads try to write logs by using the log pool, all the threads have to wait for the pointer to a memory object spin locks.
Note The log pool is an in-memory cache of the transaction log. This cache is used to optimize reading the log for recovery, transaction replication, and rollback operations and for the AlwaysOn Availability Groups feature.
Cumulative update information
Cumulative Update 3 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2812412Note 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 2012 SP1 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:
(http://support.microsoft.com/kb/2812412/ )Cumulative update package 3 for SQL Server 2012 Service Pack 1
(http://support.microsoft.com/kb/2772858/ )The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
After you apply this hotfix, a new T9024 trace flag is added. After you enable this trace flag, the SQL Server node partitions the pointer to a memory object.
Note If you also enable the T8048 trace flag, the CPU partitions the pointer to a memory object. Try adding this trace flag if the symptoms associated with this issue persist after you enable T9024 trace flag.
PrerequisitesTo apply this hotfix, you must have SQL Server 2012 SP1 installed on the computer.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
File informationThe global hotfix version of this has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this imageExpand this image
Collapse this tableExpand this table
Collapse this imageExpand this image
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2809338 - Last Review: March 18, 2013 - Revision: 5.0
Contact us for more help
Connect with Answer Desk for expert help.