Knowledge Base

BUG: FORCEPLAN Does Not Control Join Order in UPDATE Statement

Article ID: 132083

Article Last Modified on 10/16/2003

Microsoft SQL Server 6.0 Standard Edition
Microsoft SQL Server 6.5 Standard Edition

This article was previously published under Q132083

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: kbprogramming KB132083