In TKU September we enhanced the Microsoft SQL Server pattern so it would recognise additional build numbers of the product.
New Versioning capabilities added in TKU November - versioning now performed by WMI Query in preference to Registry Query, since if it succeeds the full_version will reflect all hotfixes applied
In TKU December update, the pattern attempts to obtain listening port information.
In addition to this, the pattern attempts to obtain the list of databases managed by the SQL Server instance
The code that determines whether an instance-based or group-based SI will be created has been improved to create instance-based SIs more often
In TKU January we revised the versioning mechanism, particularly pertaining to the WMI Query method. Trailing zeros are now removed from the bottom of the extracted version, and the mapping table was subsequently simplified to accomodate this change.
In TKU June 2010 an inconsistency where the port attribute could be set as either integer or string (depending on how the data was obtained) was removed. The port attribute is always set to string. Finally, additional SQL Server versions were added to product version mapping table.
In TKU September 2010 a change was made to ensure the pattern does not check for registry keys that clearly do not exist
In TKU October 2010 a number of additional registry keys were added to support the acquisition of edition and backup directory information for Microsoft SQL Server 2008 R2.
In TKU January 2011 a number of changes were made on the pattern:
In TKU March 2011 the pattern has been further enhanced to determine whether the discovered SQL Server is within an SQL Server cluster, and if so to attempt to determine the cluster IP address the SQL server is listening on. If the information is obtained, it can be used by Deep DB discovery patterns shipping with ADDM 8.2 to query the database server using a specific IP address
In TKU May 2011 the SQL Server pattern has been further enhanced with an additional approach to determining the cluster IP address for SQL Server instances that are part of an SQL Server.
Furthermore, the SQL Server Database Detail pattern was updated to optionally obtain database sizes (in KB) and store them as an attribute of DatabaseDetail nodes, as well as to optionally execute the 'sp_databases' query as the primary query to obtain the list of databases
In TKU October 2011 all the creation code for DatabaseDetail nodes was moved to the extended pattern. Should the extended pattern be unable to get a list of databases from a JDBC database query, it will attempt to get such a list from a directory listing or command. In addition, the path to the data directory is now alternatively obtained from registry.
In TKU November 2011 an explicit database query to get the list of databases was added to support Microsoft SQL Server 2000. In addition, the list of databases can now also be obtained via a WMI Query. The file-based method of getting the list of databases was moved to become the last of the four methods. The pattern now handles the storing of multiple listening ports by the addition of a new attribute, port_list, on the Software Instance.
In TKU January 2012 the extended database details pattern was modified to handle correctly database filenames that contain a space.
In TKU February 2012 for SQL Server 2000, added support for obtaining listening IP address when it is part of a cluster.
In TKU March 2012, the deep discovery pattern module now prevents a null database detail node being appended to db_details list. WMI queries now partially handles named instances and searches for both PerfFormattedData and PerfRawData. In addition, the pattern now correctly handles database filenames containing a '$'.
In TKU May 2012, the pattern was updated with SP information moved to the correct attribute to make SI attribute values consistent with those of other discovered Microsoft products. Content of the SI 'name' attribute was left the same (to include SP information if present).
In TKU June 2012, the pattern compatible with Atrium Discovery 8.3 and later was updated through an addition of a 'product' SI attribute set to combination of 'type' and 'edition' to improve CMDB mapping that is used by the Atrium Product Catalog
In TKU July 2012, the file-based database discovery method in the extended pattern now creates Detail nodes instead of DatabaseDetail nodes. In addition, a configuration option has been added to enable file-based database discovery, it now being disabled by default. Support of IPAddress node was added.
In TKU September 2012, the extended pattern was updated to resolve an issue with obtaining a list of databases via SQL query when discovering SQL Servers with case sensitive collation settings. Furthermore the extended pattern was updated to reduce the number of individual messages relating to table detail node creation being written to the log file.
In TKU October 2012, the pattern was updated with the addition of a method to obtain the binding address for clustered instances. In addition, a trigger process containing a '~' is now normalized using a common function as well as any calls to the Windows Registry now also searching in the Wow6432Node space.
In the extended pattern module, one SQL query to obtain database list, 'SELECT name AS database_name FROM SYS.SYSDATABASES' was updated to 'SELECT name AS database_name FROM sys.sysdatabases' to support both case insensitive and case sensitive setups.
In TKU November 2012, an issue in the pattern which could in certain circumstances cause the pattern to exit with an ECA engine error was corrected (QM001773290).
In TKU December 2012, the pattern was updated so that SQL servers that are in a cluster have a 'cluster_name' attribute set in case this is obtained via a registry query (QM001774745)
Furthermore, the pattern has had a minor update to ensure mapping of certain attributes to Atrium CMDB BMC_Product CI matches Atrium Product Catalog Data (as published by BMC)
In TKU May 2013, the pattern was enhanced to improve identification of SQL Server 2012 and registry queries added to obtain edition information when discovering SQL Server 2012.
Finally, the product version mapping tables were updated.
In TKU Feb 2014, the extended pattern was updated in having underscore removed from servername in WMI query calls.
In TKU Mar 2014, the extended pattern was updated in having dollar characters removed from servername in WMI query calls in addition to underscores.
In, registry key parsing for port extraction was improved.
In TKU May 2014,fixed ECA error caused by absent cmdline attribute in DiscoveredService node.
In TKU Jun 2014, better handling of special characters (_, $) within servername in WMI query call was added to the DatabasesAndTables pattern within the Extended Discovery pattern.
In TKU Aug 2014, the pattern includes the following updates:
From TKU Sep 2014, the pattern includes the following updates:
In TKU April 2015 the pattern was updated with the following changes:
In TKU May 2015 the pattern was updated with the following changes:
In TKU August 2015 the pattern was updated with the following changes:
In TKU September 2015 we fixed a bug regarding database query calls to remote hosts
In TKU October 2015 the pattern was updated with the following changes:
In TKU March 2016 the pattern was updated with the following changes:
In TKU April 2016 we updated the regular expression used to obtain instance name. In addition, the release mapping tables was further updated.
In Technology Knowledge Update 2016-Dec-1 more version pairs added to the Microsoft SQL Server version mapping table.
In TKU January 2017:
In TKU March 2017 we improved WMI versioning. We now add a mapping from the build number WMI gives us to the internal version number. (There was a small bug in this update that we fixed in TKU April 2017)
In TKU May 2017 we:
In TKU October 2017 we added:
In TKU January 2018 there was
In TKU April 2019 the following changes were made:
From TKU December 2019:
In TKU March 2020 we made a small bug fix to how we report the Software Instance name
In TKU April 2020 we made the following changes:
From TKU October 2020 we report "" as the bind_address whenever we see 0.0.0.0 as the bind address in the Linux configuration file. We made a slight improvement to how we map internal version to product_version