How to Fix SQL Database Restore Error 5243

This article will introduce about how to fix problems related to the SQL database restore error 5243 and error 5242. These are common errors in SQL Database Server. It was a sunny that when I was working with the database and doing some tests. Everything was OK, but suddenly I decided to take a look to 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 SQL Database Restore Problem – error 5243 and Error 5242.


The following software set up will be used in this article in order to accomplish this demo:

  1. First, you will need to have SQL Server installed. You can use any SQL Server version installed in Windows.
  2. Also, you will require SQL Server Management Studio installed.
  3. 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 to different options to fix the error. Here you have some possible options:

  1. Run the DBCC CHECKDB Transact SQL command
  2. Try to restore the database SQL Server Page
  3. 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>


If 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:

Free download

Stellar Repair for MS SQL is a simple, easy to use and smartly developed software 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.


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.

  1. Mildred Peck December 26, 2018
    • Eric Simson December 26, 2018
  2. Elizabeth R. Gudino December 14, 2018
    • Eric Simson December 14, 2018
  3. Jeffrey S Bucher November 28, 2018
    • Eric Simson November 28, 2018
  4. Stan McQueen October 26, 2018
  5. Alisa October 7, 2018
    • Eric Simson October 8, 2018

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.