Troubleshooting SQL Server Query Analyzer

Here is a problem that you may encounter when using SQL Server Query Analyzer to execute a script:

• Showplan does not return a plan for Transact-SQL statements referencing temporary objects. You can trace the SQL:BatchStarting and Execution Plan events in SQL Server Profiler while executing the Transact-SQL statements to see the plan.

Here are some problems that you may encounter when using SQL Server Query Analyzer to tune a database for a query:

• Unable to recommend indexes because the query did not reference only tunable tables. This problem was caused by one or both of the following reasons:
  • The query did not reference any tunable tables.
  • The query or batch contained the USE statement.
• No indexes suggested. This problem can be caused by any of these reasons:
  • The tables are very small.
  • Supporting indexes may already exist.
  • Only a clustered index would have improved performance.

Note SQL Server Query Analyzer will not recommend clustered indexes when tuning a single query.

• Unable to parse query. This problem can be caused by any of these reasons:
  • The GO command after the query was selected for tuning. The GO command should be excluded from the selected query text for analysis.
  • The wrong database was selected for the query.
  • The text of the query selected for analysis is not parseable.