Article ID: 2503834 - Last Review: April 18, 2011 - Revision: 1.0 FIX: Assertion error when you try to recover a database in SQL Server 2008 R2
Microsoft distributes Microsoft SQL Server 2008 R2 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 fix release. SYMPTOMSIn Microsoft SQL Server 2008 R2, a database is marked as suspect when you try to recover the database. Additionally, the following assertion error is logged in the SQL Server 2008 R2 Errorlog file: <Date> <Time> <SPID> Error: 17066, Severity: 16, State: 1. <Date> <Time> <SPID> SQL Server Assertion: File: <page.cpp>, line=4953 Failed Assertion = 'm_freeCnt + emptySlots * sizeof (Slot) >= spaceNeeded'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. CAUSEThis issue occurs because a page may not have sufficient space when you recover a database. Any thread that is involved in an Online Index Rebuild operation or a Shrink Database operation can compress a new page. If the page has insufficient space, the assertion error occurs. RESOLUTIONCumulative update informationThe fix for this issue was first released in Cumulative Update 7. 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: 2489376
(http://support.microsoft.com/kb/2489376/
)
Cumulative Update package 7 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
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. APPLIES TO
| Other Resources Other Support Sites
CommunityGet Help NowArticle Translations
|






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top
