Here are some errors you may encounter when using the Index Tuning Wizard:
The connection to the server is broken or the server is offline.
The trace file or script contains no SQL batch or RPC events.
The trace file contains SQL batch or RPC events, but none referencing objects in the selected database.
When processing a large workload, canceling index analysis can take several minutes or more to complete processing.
After accepting the recommended index configuration for a large workload or database, final processing can take several minutes or more to complete.
Queries referencing temporary or other nonexisting objects cannot be tuned.
The Index Tuning Wizard was unable to open a file. Check to see if the workload file was locked by another user or process, or if the workload file was moved or deleted.
The Index Tuning Wizard encountered a problem writing to a work file. Increase the available space on the disk drive where the system temp directory is located.
There was insufficient memory to run the Index Tuning Wizard. Run the Index Tuning Wizard on a computer other than the server, or increase the size of the operating system paging file.
Multiple users concurrently tuning a database may result in missing index errors. It is recommended that only one user tune a database at a time.
| Index Tuning Wizard | Misc. Event Category |
| Rebuilding an Index | Analyzing a Query |
| Maximum Capacity Specifications |