Home
  •  

Table error: Test failed. Slot overlaps with the prior row.

Microsoft.SQLServer.2000.Table_error___Test_failed__Slot_overlaps_with_the_prior_row (Rule)

Knowledge Base article:

Causes

Slot S_ID's offset in the slot offset array is not greater than or equal to the end of the previous slot, so they overlap. TEST is 'sorted [i].offset >= max', where the lhs of the expression is the ADDRESS, and 'max' is the end of the previous slot.

Resolutions

HARDWARE FAILURE

Run hardware diagnostics and correct any problems. Also 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 problem, 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.

CAUTION: The repair depends on the type of page (see error 8938 for a list of page types):

Any type of page with a NULL page ID:

De-allocate the page and rebuild any index the page was part of.

Any non-allocation page:

De-allocate the page and rebuild any index the page was part of.

GAM, SGAM, or ML_MAP_PAGE page (if the undocumented repair option is specified):

Re-format and rebuild the page.

DIFF_MAP_PAGE page:

Re-format the page and clear the bitmap.

Set the database as having no full backup, preventing differential backups until one is taken.

PFS_PAGE page and all other allocation pages:

No repair possible.

CAUTION: This repair may cause data loss.

CAUTION: If running DBCC CHECKDB with one of the repair clauses does not correct the problem, contact your primary support provider.

Element properties:

TargetMicrosoft.SQLServer.2000.DBEngine
CategoryEventCollection
EnabledTrue
Event Source$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
Table error: Test failed. Slot overlaps with the prior row.
{0}
Event LogApplication
CommentMom2005ID='{CC567044-D1F2-4286-AD38-69EE48F0AC9D}'

Member Modules:

ID Module Type TypeId RunAs 
EventDS DataSource Microsoft.Windows.EventProvider Default
GenerateAlert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.SQLServer.2000.Table_error___Test_failed__Slot_overlaps_with_the_prior_row" Target="SQL2000Core!Microsoft.SQLServer.2000.DBEngine" Enabled="true" Comment="Mom2005ID='{CC567044-D1F2-4286-AD38-69EE48F0AC9D}'" Remotable="true">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="EventDS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>Application</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery>PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery>EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>MatchesMOM2005RegularExpression</Operator>

              <Pattern>^(17052|17055)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery>EventDescription</XPathQuery>

              </ValueExpression>

              <Operator>MatchesMOM2005BooleanRegularExpression</Operator>

              <Pattern>((^.*8942 and (not ^.*\n.*8942)) or (^.*8942.*\n.*8942)) AND (NOT ^.*[0-9]+.*8942) AND (NOT ^.*8942[0-9]+)</Pattern>

            </RegExExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertOwner>$Data/PublisherName$</AlertOwner>

      <AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2000.Table_error___Test_failed__Slot_overlaps_with_the_prior_row.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDescription$</AlertParameter1>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

    </WriteAction>

  </WriteActions>

</Rule>