This article was previously published under Q203777
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53157 (SQLBUG_70)
The Index Tuning Wizard (ITW) does not work on a table that has a table name defined using characters that cannot be represented in the system locale of the computer that the ITW is run on. If you use a workfile under these conditions to analyze a SELECT statement from the SQL Server Profiler's "Index Tuning Wizard", you may see the following error message:
There are no events in the workload. Either the trace file contained no SQL batch or RPC events or the SQL script contained no SQL queries.
When you run "Perform Index Analysis" with SQL Server Query Analyzer on a table with the same conditions as described in the first paragraph of this article, you may receive the following error message in the results window:
The query was unparseable for one of the following reasons: 1. The user has selected the wrong database or text of the query selected for analysis is not parseable. 2. The keyword GO was selected for tuning.
Database names and column names defined using characters that are represented in the system locale of the computer on which the ITW is run do not affect the ITW or "Perform Index Analysis" behavior.
Use only characters that can be represented in the system locale of the client computer on which the ITW is run in the names of your tables. If you are unsure what these characters are, you may choose to use only the base Latin characters (A-z and 0-9), because these characters can be represented with any system locale.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.