Guidelines to Fix SQL Error 8966

SQL is Structured Query Language that is widely used for keeping records in large databases where the records can be inserted, delete or updated. But sometimes due to several reasons one fails to access the database and all the data stored in it. One may encounter error messages like SQL error 8966 which leads to severe problems for the user.

SQL Server has been provided with an inbuilt tool in the form of DBCC CHECKDB that can repair a damaged or corrupt database. The database can get corrupt due to a number of reasons like

  • System not functioning properly.
  • Concurrent modification.
  • Damage in the database structure.
  • Abrupt system shutdown.
  • Record header corruption.
  • Virus infection.

But sometimes when the corruption is severe the command fails to repair the database or make the data stored in it accessible. In such a situation it displays an error message like any of the ones mentioned below:

"Msg 8966, Level 16, State 2: Could not read and latch page (%d:%d) with latch type %s. 1453(Insufficient quota to complete the requested service.) failed."

"Msg 8966, Level 16, State 2: Could not read and latch page (%d:%d) with latch type %s. 1450(Insufficient system resources exist to complete the requested service.) failed."

"Server: Msg 8966, Level 16, State 1, Line 1 Could not read and latch page (1:24) with latch type SH. sysindexes Failed. "

The occurrence of the error is a clear indication that there is severe corruption in the database and it cannot be repaired by the DBCC CHECKDB command. In such a situation you can use an efficient and reliable SQL repair utility and ensure MDF repair so that you can once again access the entire data stored in the database. These make use of strong scanning algorithms and thus, recover and restore the data from corrupt database and all the database objects like tables, views, triggers, indexes and much more.