We\'re having sporadic, random query timeouts on our SQL Server 2005 cluster. I own a few apps that use it, so I\'m helping out in the investigation. When watching the % CPU tim
Run Profiler and filter for queries that take more than a certain number of reads. For the application I worked on, any non-reporting query that took more than 5000 reads deserved a second look. Your app may have a different threshold, but the idea is the same.