Microsoft KB Archive/174443
Article ID: 174443
Article Last Modified on 7/19/2006
- Microsoft SQL Server 6.5 Standard Edition
This article was previously published under Q174443
BUG #: 16819 (SQLBUG_6.5)
If you perform a SELECT INTO statement 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.
To resolve this problem, install SQL Server 6.5 Service Pack 3 or later.
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in U.S. Service Pack for Microsoft SQL Server 6.5. For information about how to download and install the latest SQL Server Service Pack, see the following Microsoft Web site:
For more information, contact your primary support provider.
The SELECT INTO statement mentioned above will return the following error:
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:
A DBCC CHECKTABLE('<table name>') statement returns the following message:
Additional query words: command sp sp1 sp2 sp3
Keywords: kbbug kbfix kbusage KB174443