With user try to login with ID that is not Sys admin type user then MSG 605 occurs. This error Msg comes in red color the user comes across with this error when they try to login SA, Administrator or any other SysAdmin login. Error is demonstrated below;
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
There are two levels of severity in this error Level 21 and Level 12.
If severity Level is 21, the user session is detached and error is sent into SQL error log and Windows Application Event Log as 605 Event ID.
If severity level is 12, then it only results in error returned to client application. In this error message, allocation unit is an ID that determines index and object to which the page relates.
To solve both level of errors do as follows;
In severity 21:
The page might be damaged or incorrect and should be retrieved from backup but if you are unable to restore using backup then repair it using DBCC CHECKDB.
Verify hardware or the system level problems
Make sure that the PAGE_VERIFY=CHECKSUM database option is switched on. You may even receive error Msg 605 after enabling checksum, checksum can provide you with ultimate proof regarding page modification within the I/O system.
In severity 12:
• Avoid uncommitted isolation level (or NOLOCK hint)
• Prepared for retrying the query till the error was not faced by you
• Do not make changes to the affected table (s) during running the query.
If above method do not help ypu them you can opt for SQL Database File Repair Tool. SQL Repair Tool is the most trustworthy tool to fix error in SQL Server Database files. It also recovers corrupted and damaged database files without backup. It also recovers views, indexes, tables, stored procedures, unique/primary keys etc. that are saved in your damaged SQL database