In TKU February 2017 we added details of Availability Groups
In TKU April 2017 we made two updates:
In TKU May 2017 we improved the additional methods to find databases. We will now try them even if the main method (using database queries) has succeeded.
From TKU October 2017 we discover databases by parsing the ERRORLOG file, but only if the relevant configuration option is enabled.
Compatibility level is now reported for databases.
In TKU November 2017 we improved discovery of databases via directory listing. We still run the procedure if the relevant configuration option is enabled, but now if we subsequently find a database with the same physical name (most probably via a SQL query) we will update the discovered instance name.
(We needed to slightly update the database queries to ensure we get physical name information. We can usually get database_size from these queries and don't need to run separate queries. This means we have removed the get_database_size configuration option. If you are still experiencing difficulties getting database_size please enable the get_db_individ configuration option, but this will increase discovery time)
In TKU January 2018 we added validity checking for databases.
AvailabilityGroup pattern update includes:
- databases in availability group are linked to related ClusterService only. (DRDC1-10025)
- updated code for sql queries to avoid integration errors
- enhanced approach for search of replica databases
- added always_on_availability_group, always_on_availability_group_role attributes for database
- group_id attribute is removed because it is used for internal purposes only
In TKU February 2018 we made the following changes:
Note that both of these features will only work if the relevant configuration option is enabled
In TKU March 2018 we improved the substitutions we use to ensure WMI queries work successfully
In TKU April 2018 we updated the validity check to allow database names with hyphens
In TKU July 2018 we removed validity checking. We now have better ways of parsing osql.exe
In TKU August 2018 we updated the osql command. It now handles long database names much better
In TKU September 2018 we did a major update to the SQL queries we use to obtain information on Database nodes such as name, compatibility, size, and physical name
In TKU May 2019 there was a minor bug fix
In TKU September 2019 there was a minor fix to how we parse the output of osql.exe
In TKU March 2020 there was a bug fix in the query we use for SQL Server 2000 to get a list of managed databases
In TKU October 2020 the following changes were made: