Summary: This post will introduce how to fix problems related to the SQL database restore error 5243 and error 5242. It will discuss the different methods that can be used to fix these SQL errors.
Contents
It was a sunny day when I was working with the database and doing some tests. Everything was OK, but suddenly I decided to take a look at the SQL Server Error Log, and then I saw the following error message:
Msg 5242, Level 22, State 1, Line 1
An inconsistency was detected during an internal operation in database ?Invoices'(ID:11) on page (1:35393). Please contact technical support. Reference number 4.Let?s discuss the effective methods to easily fix the SQL Database Restore Problem ? error 5243 and Error 5242.
Requirements
The following software setup will be used in this article in order to accomplish this demo:
- First, you will need to have SQL Server installed. You can use any SQL Server version installed in Windows.
- Also, you will require SQL Server Management Studio installed.
- Finally, we will use Stellar Repair for MS SQL software. This software is designed to fix problems related to database corruption in SQL Server.
Getting started
When you receive the error message 5242 or 5243, it means that your database is corrupt. This error is usually visible in the SQL Server error log.
The error shows the page:
Page (1:35393).
Let?s take a look at different options to fix the error. Here you have some possible options:
- Run the DBCC CHECKDB Transact SQL command
- Try to restore the database SQL Server Page
- Use SQL Database Repair Software
Run the DBCC CHECKDB Transact SQL command
The DBCC CHECKDB T-SQL command can be used to try to restore the database. For more information about the DBCC CHECKDB, you can use the following link.
The REPAIR_REBUILD option can be useful. If your database is too big, using the DBCC CHECKTABLE can reduce the time if you know which table is corrupted.
Try to restore the database SQL Server Page
If the page is corrupt and you know the details of the corrupt SQL database page, it may be possible to restore when a page is corrupt.
In the error message 5243, you can view the corrupted page. Also, it is possible to detect the page using a select in the MSDB database to the suspect_pages table. The suspect_pages table contains the pages that can be corrupt.
In order to restore the page, you can use the following T-SQL commands:
RESTORE DATABASE <database_name>
PAGE = file: page
FROM <device_name>
WITH NORECOVERYIf you do not feel comfortable with T-SQL, you can use SQL Server Management Studio (SSMS).
Use Stellar Repair for MS SQL Software
If you cannot restore using the DBCC CHECKDB or the Restore database specifying the page, it is possible to use this software. This software is simple to learn and use. Install the software and select the way to restore the SQL Server information. You can restore the information in SQL Server file (.MDF) or in another format of your preference like XLS, HTML, CSV.
You can download the software here:
Stellar Repair for MS SQL is a simple, easy-to-use, and smartly developed software that can be used to restore your database in case of database corruption. You only need to specify your data file (MDF) and the software will recover the SQL Server Database information.
Conclusion
As you can see, if you receive the SQL database error 5243, it is possible to recover the data using 3 options. In this article, we show how to recover the information using the DBCC T-sql commands, restoring the page, and finally using the Stellar Repair for MS SQL software.
If the DBCC does not work, try to restore the page and finally, Stellar SQL Repair can be the effective solution.
