MSSQLCity.Com - All about MS SQL
     
About Us  
SSWUG Articles  
Articles  
FAQ  
Administration  
Backup/Restore  
Connectivity  
Development  
General  
Installation  
OLAP  
Replication  
Transfer/move  
Trouble  
SQL 6.5  
Scripts  
Tips  
Test Exams  
Advertise  
Download  
History  
Search  
Traffic  
Related Links  
     
Your button logo
Add to Favorites
 
     
 


How can I resolve the error 605?

Answer:

It is the full error 605 message text:

Attempt to fetch logical page %S_PGID in database '%.*ls'
belongs to object '%.*ls', not to object '%.*ls'.
The error 605 occurs when SQL Server detects database corruption. Read about "Error 605" in SQL Server Books Online. It's therefrom:

Execute DBCC CHECKTABLE on the second object specified in the error message.
To determine the full extent of the corruption, execute DBCC CHECKDB as soon
as possible. Also check the error log for other errors, which often accompany
a 605 error. 

If the 605 error is not transient, the problem is severe and you must run
DBCC CHECKDB with one of the repair clauses. If the error involves an index
page, use the REPAIR_REBUILD clause. If the error involves a data page, it
may be necessary to use the REPAIR_ALLOW_DATA_LOSS clause. In the likely event
that you cannot allow the loss of data, you will need to restore from a known
clean backup. If the problem persists, contact your primary support provider.

 

 
Visit The SQL Server Worldwide User's Group for all the latest news and information about SQL Server, Oracle, DB2 and XML for developers and administrators.

(c) 1997, 2010 Bits on the Wire, Inc