FIX: SELECT with Subquery Containing BETWEEN Clause is Slow When Starting Range is the Minimum Value

View products that this article applies to.

This article was previously published under Q248604

BUG #: 55938 (SQLBUG_70)

Expand all | Collapse all

SYMPTOMS

The following query gives varying performance depending on the value you use for col6 in the BETWEEN clause:

SELECT T1.col1 ,T1.col2 ,T1.col3
FROM Table1 AS T1
WHERE EXISTS
(SELECT * FROM TABLE1 AS T2
WHERE T1.col1 = T2.col1 and T1.col4 = T2.col4 AND
(T2.col5 = 801101 OR T2.col5=801102 OR T2.col5=801105 OR T2.col5=803198 ) AND T2.col6 BETWEEN 1 and 10 )

A value lower than the one used in the BETWEEN clause must exist in the table. In the preceding example, col6 in TABLE1 must have a value lower than 1 or it will degrade performance.

Back to the top

WORKAROUND

Insert a dummy row in the table with a value for col6 that is lower than the one used in the BETWEEN clause.

Back to the top

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

254561 (http://support.microsoft.com/kb/254561/ ) INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

Back to the top