{"id":416,"date":"2019-04-12T05:10:14","date_gmt":"2019-04-12T05:10:14","guid":{"rendered":"http:\/\/www.databasefilerecovery.com\/blog\/?p=416"},"modified":"2025-06-10T06:17:30","modified_gmt":"2025-06-10T06:17:30","slug":"how-to-resolve-error-605-in-sql-server","status":"publish","type":"post","link":"https:\/\/www.databasefilerecovery.com\/blog\/how-to-resolve-error-605-in-sql-server\/","title":{"rendered":"How to Resolve error 605 in SQL Server??"},"content":{"rendered":"

Summary: <\/strong>You can encounter the following messages such as: “ Msg 605, Level 21, State 3, Line 1 – Attempt to fetch logical page (1:224) in database 11 failed. It belongs to allocation unit 72058253744865280, not to 72057594040287232.”  This error is encountered when there is damaged MDF files which are inaccessible from the SQL database. However, the precise reason is unknown. To resolve error 605 in SQL Server, many times, you might need the professional expertise of a SQL server expert.  Let’s see How to Resolve error 605 in SQL Server using manual method and professional SQL database recovery tool<\/a><\/strong>.<\/em>
<\/i> Download Now<\/a> <\/i> Purchase Now<\/a><\/span><\/p>\n

Causes of SQL Server Error 605<\/h2>\n\n\n\n

There are two types of severity in this error,<\/p>\n\n\n\n

Severity 21: <\/strong>In this, the problem could be with the pages of database or with engine of SQL server while learning the actual value of expected allocation.<\/p>\n\n\n\n

Severity 12: <\/strong>This is caused when the server query uses read uncommitted isolation level or NOLOCK query hint.<\/p>\n\n\n\n

Error Msg 605 appears when a user tries to log through the system other than the system administrator. The error appears in RED color.<\/p>\n\n\n\n

When severity level is 21, the user session gets terminated and the error is registered in SQL error log and Windows Application Event Log as Event ID 605.So, this is how you know this error has occured.<\/p>\n\n\n\n

You can experience severity level 12 only when it is returned from client application and also if the query flops in situation when it is utilizing read uncommitted isolation level.<\/p>\n\n

Also Read:- How To Fix Microsoft SQL Error 18456-Login Failed Error\n<\/a><\/strong><\/p>\n\n

Methods to Resolve error 605 in SQL Server<\/h2>\n\n\n\n

First and foremost, you should always keep the backup of your data to minimize loss of valuable data.<\/p>\n\n\n\n

In the case of Severity level 21<\/h4>\n\n\n\n

You can follow the following steps.<\/p>\n\n\n\n

First of all you need to have the right information about the data file and page number given in error message,then use the DBCC PAGE command.<\/p>\n\n\n\n

dbcc traceon(3604)
dbcc page(\u2018MyDatabaseName\u2019,1, 224,3)
dbcc traceoff(3604)<\/p>\n\n\n\n

NOTE: <\/strong>You could use any of the 0,1,2,3 options as the last parameter (bold 3) of DBCC PAGE command. You have two different options to choose from:<\/p>\n\n\n\n

    \n
  1. Restore that page from a complete Database backup<\/li>\n
  2. Try DBCC commands<\/li>\n<\/ol>\n\n\n\n

    According to experts, it is recommend to opt for the 1st option, but just in case you don\u2019t have last full backup, the you could easily opt for a second option. Given below TSQL, follow the commands to restore the page from the last complete database backup<\/p>\n\n\n\n

    RESTORE DATABASE MyDatabaseName
    PAGE = \u20181:224\u2019
    FROM DISK = \u2018D:\\MyDatabaseName.bak\u2019
    WITH NORECOVERY<\/p>\n\n\n\n

    But, it can happen that you don\u2019t have the required backup, then the best option is to use DBCC CHECKDB command.<\/p>\n\n\n\n

    If there is no backup of the data, then first you require to verify about the severity level i.e. 21 or 12.<\/p>\n\n\n\n

    DBCC CHECKDB (\u2018MyDatabaseName\u2019) WITH NO_INFOMSGS<\/p>\n\n\n\n

    After executing the above command, it might be recommended to use REPAIR_REBUILD.<\/p>\n\n\n\n

    Note: If you see repair level REPAIR_ALLOW_DATA_LOSS, unfortunately you may lose some of your data. Follow the command below:<\/p>\n\n\n\n

      \n
    1. ALTER DATABASE MyDatabaseName SET SINGLE_USER
      GO
      DBCC CHECKDB(\u2018MyDatabaseName\u2019, REPAIR_REBUILD)
      GO
      ALTER database MyDatabaseName SET MULTI_USER
      GO<\/li>\n
    2. ALTER DATABASE MyDatabaseName SET SINGLE_USER
      GO
      DBCC CHECKDB(\u2018MyDatabaseName\u2019, REPAIR_ALLOW_DATA_LOSS)
      GO
      ALTER database MyDatabaseName SET MULTI_USER<\/li>\n<\/ol>\n\n\n\n

      In case of severity level 12,<\/h4>\n\n\n\n

      In case of severity level 12, you can follw the steps given below:<\/p>\n\n\n\n

        \n
      1. First of all,<\/strong>ignore uncommitted isolation level (or NOLOCK hint).<\/strong><\/li>\n
      2. Do not make any changes while running the SQL query.<\/strong><\/li>\n
      3. Try to avoid <\/strong>mak<\/strong>ing<\/strong> unnecessary interruptions.<\/strong><\/li>\n<\/ol>\n\n\n\n

        These steps may provide you with some relief from error 605 in sql server, but still, these steps do not guarantee high-end qualitative as there is a probability that the SQL server edition may not favor the retrieval process making your job tough. So, to resolve error 605 in SQL Server, you may need a more profesional solution.<\/p>\n\n\n\n

        There are many types of databases like MS SQL Server 2014\/2012\/2008 R2\/2008\/2005 can be used to store the MDF files. It might happen that theabove mentioned approach does not works well for SQL Server 2014, then it would become impossible to fetch and secure the data.<\/p>\n\n\n\n

        Therefore, it is necessary to make use of a tool that can guarantee the recovery of corrupt MDF files to resolve error 605 in SQL Server<\/p>\n\n\n\n

        Professional SQL Recovery to Resolve error 605 in SQL Server<\/h3>\n\n\n\n

        If you want complete recovery of corrupt MDF file components like Triggers, Rules, Functions, Tables, and Stored Procedures, etc. If you wish to preview the recovered file components, then you are recommended to install the DatabaseFileRecovery SQL database recovery tool<\/strong>.<\/p>\n\n\n\n

        Important Features of SQL Database Recovery Tool<\/h2>\n\n\n\n