This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 469812 (SHILOH_BUGS)
A query that performs a parallel scan of an index that has a bit column as a part of the index key may return results that are not correct. The query may return the wrong number of rows, or the aggregate calculations that are produced by functions such as SUM() or COUNT() may not be correct.
Service pack information
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 How to obtain the latest SQL Server 2000 service pack
The following hotfix can only be applied to a computer that is running SQL Server 2000 Service Pack 3 (SP3) or a hotfix build that is based on SQL Server 2000 SP3.
The English version of this hotfix 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.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
To work around this problem, remove the bit column from any indexes where it is a key column. Alternatively, you can also avoid the problem by changing the data type of the bit column to tinyint. Before you change a column's data type with an ALTER TABLE command, you must first drop any indexes that include the column. You can re-create the indexes after the column's data type has been changed.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.