A provision in MS SQL database is a dispose of specified number of rows and columns that contain major chunk of records. A DBA be possible to fetch the required records as by his/her requirements from any entertainment, by running a query. A database ask while in most cases displays to be desired results, might fail due to unlike each other reasons. One of the most threadbare factors for failure is corruption of plain. Few known factors for table vitiation are improper system shutdown, metadata fabric corruption, application failure, and virus make aggression on. In most cases of query mode of performance failure, an error message gets displayed attached the monitor. This error message comprises of all necessary information that helps a DBA to identify the level of corruption and the road to overcome it. However, if in situation a DBA is unable to see through the error message and has ~t any backup of database, then SQL database redemption becomes a little difficult.
To account for the above error message, here is a certain-time scenario. A user wants to number the number of rows of repast for which he executes count(*) interrogatory. But, the query instead of displaying the lump number displays the below error word:
"Attempt to fetch logical page (1:42724) in database 'proof' belongs to object 'report-table', not to phenomenon 'RRR'. Connection Broken.."
Understanding that the board is corrupted, the user tries DBCC Checktable command with repair_rebuild parameter to know the aim of corruption. The command displays the in the present life result:
"Server: Msg 2535, Level 16, State 1, Line 1
Table Corrupt: Page (1:42724) is allocated to end ID 1517248460, index ID 0, not to butt; goal ID 982294559, index ID 0 lay the ~ation of in page header.
Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1517248460, director ID 0: Page (1:42723) could not have ~ing processed. See other errors for particulars.
Server: Msg 8939, Level 16, State 1, Line 1
Table Corrupt: Object ID 1517248460, pointer 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, alphabetical table of references ID 0, page (1:42723). Test (emptySlotCnt == 0) failed. Values are 15 and 0........."
The database condensed statement records are inaccessible post the of rectitude too great for error message appears. The user also tries DBCC CHECKDB command with repair_allow_data_loss parameter. But matter of no consequence works.
Resolution:
In such situations, the most wise and safest way is to repair the database index is by using SQL Recovery software.
No comments:
Post a Comment