Fixing SQL Server Error 8936 When Your Database Won't Open Cleanly
You run a query or a consistency check and SQL Server throws back Msg 8936: a table error with a B-tree chain linkage mismatch. Your database may be only partly readable, and the last backup may be stale or damaged. This tool, from SysTools, is built for that situation. It reads the damaged MDF file directly and pulls out what it can.
Quick facts
- Purpose: repair corrupt MDF files and recover database contents, including error 8936 cases
- SQL Server versions: files from 2000, 2005, 2008, 2012, 2014 and 2016
- Trial: a free demo previews recoverable items but restricts saving
- Full version: needed to save the recovered data
- Windows support listed: 98, ME, NT, XP, 2000, 2003 and Vista
What error 8936 means
SQL Server uses B-tree indexes, with a root node, branch nodes and leaf nodes. Error 8936 appears when SQL Server finds a break in the chain of logical pages at one of those levels. The message says the next page of one page points to a second page, but that second page's previous link points somewhere else. It usually signals corruption in the database, and you may lose access to some of your data.
Try the standard fixes first
- Run hardware diagnostics, since faulty hardware can cause this corruption.
- Restore from a clean backup if you have one.
- With no clean backup, run DBCC CHECKDB to see how much damage there is, then run it again with the repair clause it suggests.
If those fail and the error keeps coming back, a dedicated recovery tool is the next step.
Key features
Recover tables, views, triggers and stored procedures
The tool restores tables and their data, views, constraints, functions, default rules, triggers, stored procedures, checks and user data types from a damaged MDF file.
Recover keys and metadata
Primary keys, foreign keys and unique keys come back along with the rest of the metadata.
Preview items before you pay
The demo shows recoverable items with their metadata, such as tables, columns, keys, indexes, triggers and procedures. You can check what is recoverable before buying.
Export to a live server or to a script file
You can export the repaired database straight to SQL Server, or save it as SQL Server compatible scripts.
Who it's for
It suits DBAs and small-business admins who have an MDF file with index corruption, no usable backup, and no time to work through repair options by hand. The interface walks you through each step on screen, and a help manual is included.
Pros and cons
- Pro: works on the MDF file directly, so you don't need a healthy server to start.
- Pro: a free demo lets you see recoverable items first.
- Pro: covers a wide range of SQL Server versions, from 2000 to 2016.
- Con: the demo can't save anything, so you only find out the final result after buying.
- Con: the vendor's Windows support list stops at Vista and Server 2003 era systems.
- Con: it doesn't replace a backup strategy or fix the hardware fault that may have caused the corruption.
FAQs
What causes error 8936?
SQL Server found a break in the chain of logical pages at one level of a table's B-tree index.
Can I try it before buying?
Yes. The demo previews all recoverable items but won't let you save them.
Which SQL Server versions are supported?
MDF files created in SQL Server 2000, 2005, 2008, 2012, 2014 and 2016 can be repaired.
Should I run DBCC CHECKDB first?
Yes, if you have no clean backup. Use it to see the extent of the damage, then apply the repair clause it suggests. Use the tool if that doesn't work.
System requirements
- Processor: Pentium II 400 MHz
- Memory: 64 MB RAM
- Disk space: 10 MB minimum
- Operating systems: Windows 98, ME, NT, XP, 2000, 2003 and Vista