This build includes many fixed issues, including the following updates from previous releases.
To collect query-related data, SQL Doctor 3.6 now supports the use of Extended Events, allowing for optimal data collection during analysis.
SQL Doctor installation is compatible with Microsoft Windows Azure and Amazon EC2 environments.
SQL Doctor is able to connect to Microsoft SQL Azure and Amazon RDS SQL Server databases.
SQL Doctor is able to analyze and provide recommendations for SQL instances hosted by Microsoft Windows Azure and Amazon EC2 environment.
SQL Doctor has no longer issues recognizing license after Windows 10 Anniversary update.
SQL Doctor is no longer showing error while running the deadlock report.
SQL Doctor is no longer displaying an error when viewing the details of the recommendation addressing a blocking condition.
SQL Doctor is no longer showing an error after analyzing a server. “An unhandled exception occurred while running Idera SQL doctor. Specified argument was out of the range of valid values".
SQL Doctor 3.5 comes with new and enhanced recommendations to improve your SQL Server performance. In addition, links within recommendations associated to online content have been reviewed and updated for this release.
SQL Doctor 3.5 fully supports monitoring of SQL Server 2014 instances.
SQL Doctor 3.5 is SQL Server 2016 compatible. This version of SQL Doctor is not certified against newer builds of SQL Server and should not be used with these builds in a production environment. IDERA provides experimental support while you use your installation in a testing environment to ensure the features you rely on most are working as or better than expected.
SQL Doctor Help (User Guide and Release Notes) is now wiki-hosted and available at wiki.idera.com > SQL Doctor.
An issue preventing some users with system administration permissions from adding a SQL Server instance for analysis in SQL Doctor no longer occurs.
With this release, SQL Doctor is independent of the SQL Toolbox. New installations of SQL Doctor no longer require you to install SQL Toolbox.
SQL Doctor now allows you to quickly check for updates to the product from within the user interface. You can check for new versions of SQL Doctor by clicking Help > Check for Updates.
SQL Doctor 3.1 fully supports the use of SQL Server 2012.
A new dashboard provides a summary of all previously executed server analyses, with instant access to the corresponding recommendations.
The Server Overview displays a summary of key SQL Server metrics, warns you of issues that need to be addressed, and provides quick findings based on your current server health.
Tune your query plans by viewing real-time query plan performance metrics and quick findings along side the T-SQL code.
Identify and fix any bottlenecks by viewing real-time statistics and quick findings for waits on your server.
Track session performance by viewing the commands, wait times, elapsed times, affected databases, and much more.
Keep tabs on your processes, network interface cards, processors, cache, memory, physical and logical disk performance, disk partitions and system properties.
SQL Doctor 3.0 is SQL Server 2012 compatible. This version of SQL Doctor is not certified against newer builds of SQL Server and should not be used with these builds in a production environment. IDERA provides experimental support while you use your installation in a testing environment to ensure the features you rely on most are working as, or better than, expected.
There are no fixed customers issues in this release.
Improved the user experience with enhanced recommendation content and layout.
The server analysis now checks the age and location of your database backups and, if needed, provides information about how you can ensure your backup data sets are both recent and easily accessible.
The server analysis now checks the following wait statistics:
The server analysis now checks the following index configurations:
Now, when you perform a DDL or DML optimization from within SQL Doctor, you can run an undo script that reverts any changes that were made by the original optimization script.
Easily direct SQL Doctor to a specific area of concern for analysis, such as memory, disk, network, security, processor, and deadlocks.
Remember where you left off by flagging recommendations and returning to them later for follow-up.
Evaluate any query to obtain recommendations that improve its performance without running a full server analysis
Resources included with recommendations are now applicable to the operating system and SQL Server version being analyzed.
| | | | | | | |