index corruption ?

We have a problem with a result set returned from a query:
select number, version, division, account
from probill
where currentstatus in ( '0', 'B', 'D', 'J', 'R', 'A' )
and rebill = 1
order by number
Primary key on number, version ; non-clustered index on currentstatus,
non-clustered index on rebill.
Each row of the result set returned is duplicated, 306 rows.
If I reindex the table, the problem goes away temporarily. If I
execute : sp_configure 'max degree of parallelism', '1' and
reconfigure, I get the correct result set, 153 rows. Setting the
maxdop to '0' again and I'm back to 306 rows.
Any idea(s) what could cause this type of problem? Hardware? Corrupt
indexes? SQL server bug? All the hardware diagnostics check out fine.
Sounds like a bug with the parallel plan to me. Are you current on service pack? Have you checked
against KB?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<nospam15151@.mailinator.com> wrote in message news:chptbj$a9c@.odak26.prod.google.com...
> We have a problem with a result set returned from a query:
> select number, version, division, account
> from probill
> where currentstatus in ( '0', 'B', 'D', 'J', 'R', 'A' )
> and rebill = 1
> order by number
> Primary key on number, version ; non-clustered index on currentstatus,
> non-clustered index on rebill.
> Each row of the result set returned is duplicated, 306 rows.
> If I reindex the table, the problem goes away temporarily. If I
> execute : sp_configure 'max degree of parallelism', '1' and
> reconfigure, I get the correct result set, 153 rows. Setting the
> maxdop to '0' again and I'm back to 306 rows.
> Any idea(s) what could cause this type of problem? Hardware? Corrupt
> indexes? SQL server bug? All the hardware diagnostics check out fine.
>
|||<nospam15151@.mailinator.com> wrote in message
news:chptbj$a9c@.odak26.prod.google.com...
> If I reindex the table, the problem goes away temporarily. If I
> execute : sp_configure 'max degree of parallelism', '1' and
> reconfigure, I get the correct result set, 153 rows. Setting the
> maxdop to '0' again and I'm back to 306 rows.
> Any idea(s) what could cause this type of problem? Hardware? Corrupt
> indexes? SQL server bug? All the hardware diagnostics check out fine.
Sounds like a MAXDOP bug, since that fixes it... Are you running the
lastest Service Pack (3a)?
If so, you might want to check http://support.microsoft.com and see if
there's a hotfix available for what you're experiencing.
|||Hi,
We are running sp3a. I wasn't able to find anything specific in the
knowledge base. Q 330212 looked close though. That's what led me to
try changing the maxdop setting.