BUG: FORCEPLAN Does Not Control Join Order in UPDATE Statement

Last reviewed: April 8, 1997
Article ID: Q132083

The information in this article applies to:

Microsoft SQL Server, versions 4.21a, 6.0 and 6.5

BUG# NT: 8455 (4.21a)

SYMPTOMS

The join order is not controllable in UPDATE statements, even though SET FORCEPLAN is ON. The optimizer does not permit the override on the join sequence.

WORKAROUND

Proper index design and query design aids the optimizer in choosing the desired join sequence. Updating statistics on the tables involved in the join also results in the proper join order for performance considerations.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: update Windows NT
Keywords : kbprg SSrvWinNT
Version : 4.21a 6.0 6.5
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.