The information in this article applies to:
SYMPTOMS
The SQL Server optimizer may choose to use a reformatting strategy for a
join when in fact it is faster to use a nonclustered index. This can occur
if all of the following conditions are true:
WORKAROUND
To work around this problem, try any of the following:
MORE INFORMATION
The SQL Server optimizer chooses the nonclustered index for the join when
it is run from a batch because the number of rows in the temporary table is
known when the join query is optimized.
Additional query words: performance slow non clustered non-clustered
Keywords : SSrvStProc SSrvTran_SQL |
Last Reviewed: April 19, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |