SQL doctor v3.0
SQL Server performance tuning recommendations
| |
|
Quickly diagnose and cure SQL Server performance problems
- New Dashboard exposes performance metrics in near real-time
- "Quick Findings" instantly identifies SQL Server performance problems
- Generates executable scripts to optimize performance
- Offers access to educational performance tuning resources
- Stores historical analysis recommendations
|
|
|
|
|
New in Version 3.0 - Released 3/8/2012 - Release Notes
- Redesigned Graphical User Interface: A new dashboard provides a summary of all previously executed server analysis, with instant access to the corresponding recommendations.
- New Server Overview: Displays a summary of key SQL server metrics and identifies you of any issues that need to be addressed and provides quick findings based on your current server health –
- Performance Metrics (CPU, memory, blocking processes, network retransmits)
- Disaster Recovery (Full, Log backup status, suspect pages)
- Analysis for Query Plan Statistics: Can now be viewed in real-time in addition to the SQL code; recommendations are provided to address any T-SQL code issues
- Analysis for Wait Stat Statistics : Can now be viewed in near real-time with recommendations for any bottlenecks that may occur
- Analysis for Session Statistics: Any sessions that are running are now displayed from the console with details pertaining to the command, wait times, elapsed times, affected databases and much more.
- Displays Key Server Information: Keeps tabs on your processes, network interface cards, processors , cache, memory, physical and logical disk performance, disk partitions and system information
New in Version 2.0.1 - Released 6/14/2011 - Release Notes
- Updated recommendations: Improved the user experience with enhanced recommendation content and layout.
New in Version 2.0 - Released 4/19/2011 - Release Notes
- See What’s New in SQL doctor 2.0

- Wait Statistics - New recommendations based on the analysis of wait statistics
- CXPACKET - When a query is parallelized, one or more of the parallel threads may require more time to complete. This results in "cxpacket" waits for the remaining threads that are "waiting" for the longest running thread to complete
- ASYNC_NETWORK_IO - This usually occurs when a client application does not efficiently process data from SQL Server over the network. The increase in async_network_io waits is caused by SQL Server waiting for the client application to process the result set.
- PAGEIOLATCH - Occurs when SQL Server waits for a data page to be read from disk into memory. This can be an indication of contention on the same pages by concurrent selects, inserts, updates and deletes, which can be magnified by IO subsystem performance issues, insufficient memory, missing indexes, out of date statistics or inefficient queries.
- Undo scripts - Optimization scripts generated by SQL doctor (DDL,DML) can now be reverted back to what they were before the recommended changes were implemented.
- Selective Category Analysis - Easily direct SQL doctor to a specific area of concern for analysis,i.e (memory,disk,network,security,processor,deadlocks)
- Diagnose Queries - Evaluate the performance of any query to obtain recommendations for improving its performance