| 1888 Articles Home | Computer Articles | Data Recovery Articles | Data Recovery RSS |  |
||
SQL database recovery post table corruption |
||||
|
Attempt to fetch logical page (1:42724) in database 'test' belongs to object 'report-table', not to object 'RRR'. Connection Broken. |
||||||||||||
| Author: Gaurav Kumar |
|
|||||||||||
A database query while in most cases displays desirable results, might fail due to various reasons. One of the most common factors for failure is corruption of table. Few known factors for table corruption are improper system shutdown, metadata structure corruption, application failure, and virus attack. In most cases of query execution failure, an error message gets displayed on the monitor.
This error message comprises of all necessary information that helps a DBA to identify the level of corruption and the way to overcome it. However, if in case a DBA is unable to understand the error message and has no backup of database, then SQL database recovery becomes a little difficult.
To explain the above error message, here is a real-time scenario. A user wants to count the number of rows of table for which he executes count(*) query. But, the query instead of displaying the total number displays the below error message:
"Attempt to fetch logical page (1:42724) in database 'test' belongs to object 'report-table', not to object 'RRR'. Connection Broken.."
Understanding that the table is corrupted, the user tries DBCC Checktable command with repair_rebuild parameter to know the level of corruption. The command displays the below result:
"Server: Msg 2535, Level 16, State 1, Line 1
Table Corrupt: Page (1:42724) is allocated to object ID 1517248460, index ID 0, not to object ID 982294559, index ID 0 found in page header.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1517248460, index ID 0: Page (1:42723) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table Corrupt: Object ID 1517248460, index ID 0, page (1:42723). Test (m_freeCnt == freeCnt) failed. Values are 1468 and 8066.
Server: Msg 8939, Level 16, State 1, Line 1
Table Corrupt: Object ID 1517248460, index ID 0, page (1:42723). Test (emptySlotCnt == 0) failed. Values are 15 and 0………"
The database table records are inaccessible post the above error message appears. The user also tries DBCC CHECKDB command with repair_allow_data_loss parameter. But nothing works.
Resolution:
In such situations, the best and safest way is to repair the database table is by using SQL Recovery software.
MS SQL Recovery Software Information:
A SQL recovery software can be used by anybody. The database table records remain safe and can be viewed before recovery. Such SQL database recovery products come with a free trial version which can be downloaded and installed on all Windows platforms.
Applied for:
a. MS SQL Server 2008
b. MS SQL Server 2005
c. MS SQL Server 2000
About Author
Gaurav work as a freelancer and researcher for Data Recovery & SQL Database Recovery Software.
For more information visit: http://www.datarecovery-info.com/database-recovery/sql-recovery.html
Article Source:
http://www.1888articles.com/author-gaurav-kumar-36016.html
Other Related Articles Goa - A Wonderful Honeymoon Destination by Aalia Month End Money – For Emergency Needs by Michael Tory SQL database recovery post table corruption by Gaurav Kumar How to Download iTunes M4P Songs to HTC Flyer from Windows by Zamira Know Why American Breakfasts & Cereals Best Selling in the UK by Amey Nikam Unsecured Business Loans- obtain best aid for your business by Terry Bock |
