BUG: Stranded Compile Time Table Created by a Failed SELECT INTO

 Last reviewed: September 30, 1997
Article ID: Q174443
The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG #: 16819 (6.5)

SYMPTOMS

If you perform a SELECT INTO using an "index = <index name>" optimizer hint where <index name> is not a valid index name, an unusable destination table will be created. This destination table cannot be dropped by using a DROP TABLE statement.

WORKAROUND

To work around this problem, install SQL Server 6.5 Service Pack 3.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. For more information, contact your primary support provider.

MORE INFORMATION

The SELECT INTO statement mentioned above will return the following error: 

   Msg 308, Level 16, State 1
   Index '<Index Name>' on table '<Table Name>' (specified in the FROM
   clause) does not exist.
Subsequent SELECT INTO statements fail because the table exists in the database's system catalogs.

A search of the sysobjects table will show the table name with a sysstat = 195. Attempting to drop the table with a DROP TABLE <table name> statement returns the following message: 

   Msg 3701, Level 11, State 1
   Cannot drop the table 'B', because it doesn't exist in the system
   catalogs.
DBCC CHECKTABLE('<table name>') returns the following message: 

   Msg 2501, Level 16, State 2
   Table named b not found; check Sysobjects

Additional query words: command sp sp1 sp2 sp3
Keywords : kbbug6.50 SSrvTran_SQL kbusage
Version : WINNT:6.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

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: September 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.