Reason & Resolution of SQL Error 8965 Explored

The below stated syntax appears on your SQL Server, when the error occurs with the database tables. Since the SQL errors are the common reasons for database inaccessibility, it is important to resolve these issues to gain access over data at the earliest. The error message resembles something to this:

Table error: Object ID O_ID. The text, ntext, or image node at page P_ID1, slot S_ID1, text ID TEXT_ID is referenced by page P_ID2, slot S_ID2, but was not seen in the scan."

Explanation: The SQL error 8965 occurs when the text node becomes orphaned and does not refer to any heap, column or clustered index.

SQL Error 8929
Object ID O_ID: Errors found in text ID TEXT_ID owned by data record identified by RID.

Explanation: This message includes SQL error 8962 or SQL error 8963 when corruption found in text node.

For rectifying these errors, Database Console Commands (DBCC) are helpful to a greater extent if executed in an appropriate manner otherwise they may lead to corruption or inaccessibility of database tables and all other components including stored procedures, index, triggers, etc.

Note: It is recommended to backup database before executing any of the given manual work around.

Backup Restoration

The existing issue with database tables can be resolved by restoring the SQL DB from available clean backup. It will help in creating a replica of database files that can be used in the place of original one to perform the functions and to continue smooth working procedure.

It is a good practice to backup database on regular period of time so that if anything unexpected happens to database tables such as SQL error 8965 issue, you can restore the maximum data from BAK files. In this way, only a limited proportion of data will be lost (may be the most recent one).


The DBCC CHECKDB can be used to repair the damaged database tables or other components. By executing the command all the integral structure of the DB can be checked and the accurate issue and the level of corruption can be detected.

For executing the DBCC, it is recommended to run the command without any repair clause. This will help in detecting the level of corruption in the corresponding MDF, NDF and LDF files. Running DBCC in this way will display an appropriate repair clause that can further be performed along with the specified command to fix the problem.

Note: Running DBCC with repair clause may result in loss of information.

An Alternate Approach

Since data and records in the database tables is crucial; it is important to repair the damaged DB or corrupted files in such a manner that would not put any adverse effects on these records. As it can be concluded that the DBCC commands could turn out in data loss and it is sometimes not possible to restore MDF and NDF files from backup.

Therefore, to prevent any loss of information, the task of repairing databases can be done via SQL Server MDF recovery software that not only helps in restoring databases from all sorts of corruption but also helps in removing variety of errors including SQL error 8965.

Download Now   Purchase Now

sql recovery banner