FIX: Parallel logical operation returns results that are not consistent (330212)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q330212
Shiloh_Bugs:362444

SYMPTOMS

A SELECT statement that performs parallel logical operations may return a number of rows that is not consistent. View the execution plan to determine if the query is running in parallel. To obtain the execution plan, run SET SHOWPLAN_TEXT ON in a separate batch before the query. For example:
USE pubs
GO
SET SHOWPLAN_TEXT ON
GO
SELECT * FROM authors
GO
A parallel plan contains the word "Parallelism" in the execution plan output; the following sample code illustrates this point:
|--Parallelism(Repartition Streams, PARTITION COLUMNS:([fvs].[FileID]))

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack



Hotfix file information

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date          Time      Version        Size             File name
-------------------------------------------------------------------- 
16-Oct-2002   18:52     2000.80.693.0  7,356,984 bytes  Sqlservr.exe
Note Because of file dependencies, the most recent hotfix or feature that contains the previous files may also contain additional files


WORKAROUND

To work around this behavior, add an OPTION (MAXDOP 1) hint to the query.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
This problem was first corrected in SQL Server 2000 Service Pack 3.

Modification Type:MinorLast Reviewed:9/27/2005
Keywords:kbHotfixServer kbQFE kbSQLServ2000sp3fix kbbug kbfix KB330212