How to Fix R2 SQL Error 926 in SQL Server 2008?

  • Written By  

  • Updated on January 16th, 2021

Microsoft SQL Server is a popular relational database management system provided by Microsoft. It offers you great features like no other database tool does. Since how long have you been using MS SQL Server? You must be impressed by the unmatched features SQL Server does have. But do you know SQL Server has some major drawbacks? What major problem have you ever encountered while using MS SQL Server and how did you deal with it?

While using SQL Server, it often happens that you confront an error message. In this blog post, I’ll show you why R2 SQL Error 926 occurs and how you can fix it with ease.


Last week, I found a post on Microsoft Discussion site. The user, who has posted that question, was dealing with SQL Server 2008 R2 Error 926.

However,in the very same thread, I found many other users were also telling that they’re facing the same problem. After that, I searched the same issue on Google and found that many people are confronting this error message. I thought I should try to fix R2 SQL Error 926 so that other SQL users don’t face this error message for long.

SQL Server 2008 R2 Error 926

Error messages are always annoying. If you come across an error message while using MS SQL Server, this will turn into a moment of frustration for sure. One such error message is SQL Server 2008 R2 Error 926. It’s one of the worst error messages in the history of Microsoft SQL Server. Confronting this error message is not less than a nightmare for any SQL user. It makes you unable to access the data and information from the MDF database. Whenever you try to make queries from the new window in order to get the output, you receive this error message repeatedly:

How to Fix R2 SQL Error 926?

There are some basic solutions which you can try here to fix this SQL Server 2008 R2 Error 926. Just have a look:

  • First, refresh the Microsoft SQL Server connection. Sometimes this little thing can resolve your issue.
  • Disconnect the Microsoft SQL Server connection. After a few seconds or minutes, reconnect it.
  • You should try restarting the service forMSSQLSERVER.
  • Restart the Microsoft SQL Server Management Studio.
  • The last thing you can try is to restart the computer system.

These are some basic things you can try at your end. But if none of the above tricks works, you should definitely try some advanced solutions. Where the basic solutions may fail or not work, the advanced solutions must help you. Generally, there are three different manual tricks you can try here to fix SQL Server 2008 R2 Error 926. First, log into the SQL account as system administrator (SA) and try any of the manual solutions shared below:

Solution #1

The best thing you can try here is rebuilding the system database. It’s very helpful to fix corruption problems in the master, model, MSDB or resource system database. Also, it helps you modify the default server-level collation. You can refer to this article to know how to rebuild the system database.

Solution #2

  • First of all, open the new window to execute the query.
  • Now type the following commands:

EXEC sp_resetstatus ‘DB’_Name;

 The above command is used to turn off the suspect flag on a database. It updates the status and mode of columns which are named as sys.databases in the particular database.


 Through this command, the database set on EMERGENCY mode becomes a READ_ONLY.


 This command will check the integrity of all the database objects.

Via this command, you can set up the database to single user mode.

 This command plays an important role here. It’ll repair all the errors in SQL Server 2008 R2.


 The above command will set the multi user mode in the SQL Server database. It’ll allow multiple users access the database file.

Solution #3

  • First of all, open the Object Explorer. Right-click the database in the tree-structure, and click Stop in the options.
  • Now go to the Control Panel>Administrative Tools>Services.
  • On the Services section, find SQL Server (MSSQLSERVER) in the list. Right-click it and click Stop in the options.
  • Now browse to this location:
  • C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
  • In this step, you need to move the MDF and MSDBlog.ldf to any other folder or place.
  • Now copy the files (you’ve moved in the earlier step) from the new location and paste them to the old.
  • Go back to the Object Explorer window where the connection is still open. Now right-click the blank space, and this time click Start in the options.
  • Now you need to refresh the database file.
  • Finally, this will start executing the process to detach the MSDB file.


Download Now


Professional Solution

If the above manual solutions don’t help you fix R2 SQL Error 926, you should look forward to a professional solution. SQL Database Recovery software is recommended by professionals and data recovery experts to handle SQL Server corruption with ease.As a result, it can repair SQL database and successfully restore SQL database objects from it. The file objects include tables, views, store procedure, programmability, triggers, default,functions, etc. Whatever you recover from the corrupt SQL database, you can save them into a new database.Consequently, this amazing recovery solution can fix all the major errors which lead to corruption in the MDF database.

To Sum Up

In this post, I have discussed the easy methods to  fix R2 SQL Error 926 in SQL Server 2008. There are free and manual methods along with the professional solution to this issue. Therefore, you can use all the solutions according to your need. Hope this post helps!! 

About The Author:

Pallavi is a content writer in the field of data recovery and email migration. She has a passion for creating engaging and thought-provoking content. With several years of experience in the field, she has developed a deep understanding of various writing styles and formats,

Related Post

© Copyrights 2017-2024 Database File Recovery. All Rights Reserved.