BUG: Update Syntax Allows Ambiguous Tablenames/Aliases

 Last reviewed: May 2, 1997
Article ID: Q151113

The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 & 6.5
BUG#: 15178

SYMPTOMS

In an update statement, if you specify a particular table/alias name for the table to be updated, and specify a different tablename/alias as a prefix to the column(s) to be updated, no errors are generated.

WORKAROUND

No workaround is required. The only table that will be updated is the table that you specify with the UPDATE, irrespective of any aliases that you use in the SET clause.

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.

MORE INFORMATION

The following script demonstrates this problem.

create table t1 (x int) go 

/* Example 1 */
update t1 set arbitrary.x = 10 go 

/* Example 2   ->  ONLY FOR SQL SERVER 6.5 */
update a set b.x = 10 from t1 a, t1 b go

Additional query words:
Keywords : kbbug6.00 kbbug6.50 kbprg kbusage SSrvProg
Version : 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: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.