A B-tree tree-level page contains a record for each child page, along with a key value for that child page. If the child page is a leaf-level page, all records on the page must have key values greater than or equal to the key value in the parent page. If the child page is a tree-level page, all records must have key values greater than the key value in the parent, except the first record, which must have a key value that exactly matches that in the parent.
Knowledge Base article:
Causes
A B-tree tree-level page contains a record for each child page, along with a key value for that child page. If the child page is a leaf-level page, all records on the page must have key values greater than or equal to the key value in the parent page. If the child page is a tree-level page, all records must have key values greater than the key value in the parent, except the first record, which must have a key value that exactly matches that in the parent.
It follows that for parent page P_ID2, with children P_ID1 and P_ID3, all key values on page P_ID1 must be less than the key value stored for page P_ID3 in the parent page.
In this case, the highest key value on page P_ID1 (that is, the keys of the last record on the page) are not less than the key value for the P_ID3 stored in the parent page P_ID2.
There are three states possible for this message (1, 2, and 3) and they all mean the same thing. They are distinguished only by where in the code the problem is discovered.
Resolutions
HARDWARE FAILURE
Run hardware diagnostics and correct any problems. In addition, examine the Microsoft Windows NT system and application logs and the SQL Server error log to see if the error occurred as the result of hardware failure. Fix any hardware-related problems.
If you have persistent data corruption problems, try to swap out different hardware components to isolate the problem. Check to ensure that your system does not have write caching enabled on the disk controller. If you suspect this to be the case, contact your hardware vendor.
Finally, you might find it beneficial to switch to a completely new hardware system, including reformatting the disk drives and reinstalling the operating system.
RESTORE FROM BACKUP
If the problem is not hardware related and a known clean backup is available, restore the database from the backup.
DBCC CHECKDB
If no clean backup is available, execute DBCC CHECKDB without a repair clause to determine the extent of the corruption. DBCC CHECKDB will recommend a repair clause to use. Then, execute DBCC CHECKDB with the appropriate repair clause to repair the corruption.
CAUTION: If you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider before executing this statement.
Performing a repair will rebuild the index. If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.
Overridable Parameters
Name
Description
Default Value
Enabled
Enables or disables the workflow.
Yes
Interval (seconds)
The recurring interval of time in seconds in which to run the workflow.
300
Priority
Defines Alert Priority.
1
Severity
Defines Alert Severity.
1
Synchronization Time
The synchronization time specified by using a 24-hour format. May be omitted.
Timeout (seconds)
Specifies the time the workflow is allowed to run before being closed and marked as failed.
200
Timeout for query execution (seconds)
The workflow will fail and register an event, if the query execution takes longer than the specified period.
60
Timeout for database connection (seconds)
The workflow will fail and register an event, if it cannot access the database during the specified period.
Home
ENU