[Edit 2014: there’s an additional bug in SQL Server 2012/2014 – see this post for details.]
Msg 831, Level 20, State 1, Line 1 Unable to deallocate a kept page.
More details are in KB article 919142, which was only recently made public.
Jonathan had a client issue recently where SQL Server’s buffer pool had been forced down to a ridiculously small size, only a few hundred MB,
(This post first appeared on SQLperformance.com four years ago as part of a blog series, before that website was mothballed later in 2022 and the
One of the easiest ways to increase query performance in SQL Server is to make sure that it can quickly access the requested data, and
Spring is already in the air here in Redmond so time for March Madness! Hundreds of dollars lower-than-ever prices on our signature 158-hour Blackbelt training
In the previous Curious Case I described an issue Jonathan had at a client with very long IAM chains, and the circumstances leading to it.
(The original version of this post first appeared on the now-deleted SentryOne blog at the start of 2022.) One of the most fundamental concepts in
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.
4 thoughts on “(Not a) CHECKDB error “Unable to deallocate a kept page””
Thanks Paul.
Hi Lads,
I meet this issues on SQL Server 2012 with AGs.
No fun at all.
Please find err logs below.
Should I contact to Microsoft directly ?
“
During undoing of a logged operation in database ‘databaseName’, an error occurred at log record ID (26946:8958:47). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Unable to deallocate a kept page.
SQL Server must shut down in order to recover a database (database ID 21). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
“
Yes – likely corruption that you’ll need to recover from.
I also met the same error as Jakub this weekend on a SQL 2012 SP1 (11.0.3349).
Any chance on “hoping” this bug was reintroduced by any chance?