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.
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 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:
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:
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.
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 NORECOVERY
If you do not feel comfortable with T-SQL, you can use SQL Server Management Studio (SSMS).
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.
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.
Priyanka is a technology expert working for key technology domains that revolve around Data Recovery and related software's. She got expertise on related subjects like SQL Database, Access Database, QuickBooks, and Microsoft Excel. Loves to write on different technology and data recovery subjects on regular basis. Technology freak who always found exploring neo-tech subjects, when not writing, research is something that keeps her going in life.
To repair SQL database restore error, I have tried emergency mode in DBCC command:
EMERGENCY MODE DBCC CHECKDB
After completion of this operation, can’t fix this issue.
Any other alternative? URGENT!
Calm down!
You can fix this error using an automated solution like Stellar Repair for MS SQL.
When I try to restore the database in SQL server 2016, I got this error message
‘An exception occurred while executing a Transact-SQL statement or batch. An inconsistency was detected during an internal operation. Please contact technical support. (Microsoft SQL Server, Error:5243)’
But, your guide helped me to fix this error quickly. Thank YOU!
Try alternative solution Stellar Repair for MS SQL software and restore the database successfully.
Before purchasing Stellar Repair for MS SQL software, I want to try this software. Is demo version of this software is available?
Sure, you can try the demo version of this software. Download our product and preview the recoverable SQL server database objects.
I’ve faced SQL Server Error 5243 while accessing database. So, to fix this error I have tried DBCC t-SQL commands but it doesn’t work properly. Then I used Stellar Repair for MS SQL Software. It worked perfectly to fix this issue.
Now, I can access SQL Server database.
Thank you for providing your feedback.
Read “Do’s & Don’ts for SQL Database Corruption” which is more helpful for your database.
Read More
While using SQL Server log I get an error message ‘Msg 5242, Level 22, State 1, Line 1’. To fix this error I tried DBCC CHECKDB and restore the database. But it’s not working. WHY?
DBCC CHECKDB command is not successful in complex cases. In this situation, you can try an alternative solution i.e. Stellar Repair for MS SQL.
Its free demo is available to all without sharing any personal/credit card details.