...and be the first to learn about new releases
SQL CoPilot has been tested with SQL Server 2016, SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, SQL Server 2008 and SQL Server 2005 SP3. It works with Standard, Enterprise, Developer and Express editions.
SQL Azure is NOT currently supported although this is planned for a future release, and neither are versions earlier than 2005 SP3.
SQL CoPilot has been designed to cope with known bugs that could affect the data displayed. Here is a quick summary of those bugs and a quick description of how SQL CoPilot is affected. Note that these issues have an impact on all third party tools - SQL CoPilot copes better than most:
This was corrected in SQL Server 2008 Build 2757 and SQL Server 2008 R2 Build 1702. SQL CoPilot is still able to read the deadlock information by correcting the XML before parsing it.
This applies to 2008 and 2008 R2. For deadlocks, SQL CoPilot displays the batch start time, so the time of the deadlock can be estimated. For other events in the system_health session, a warning is displayed that the event time may not be correct. This was fixed in SQL Server 2012
This is by design. It would not be safe to store passwords in the .bak file generated when you back up your instances, tags and threshold. This is a security decision - you will need to change them back to use SQL authentication using the "Manage Instances" screen.
System Health reports use the system_health extended event session. Extended events were introduced in SQL Server 2008. You will not see these reports on SQL Server 2005.
Always On is a feature introduced in SQL Server 2012. You will not see this information for earlier versions.