benjamin.van.dam

FAQ: SQL Server Edition Discovery Script - 2020/Feb

Blog Post created by benjamin.van.dam Employee on Feb 12, 2020

Background

 

During the last couple of years, customers and partners have reported issues with incorrect SQL Server edition discovery. Historically SQL edition discovery was done defaulty by the Inventory Agents. The client/agent have hard coded scanning configurations within the Agent itself, that looks at specific file paths/registry paths for SQL Server and yields software rows. The issue though is that the results yield some false positives of the SQL editions, which sometimes results in the wrong edition of SQL Server to be detected after an upgrade or downgrade on a machine has taken place, and the edition not updating correctly.

As a measure to ensure that both the Scanning Discovery is correct, and the Scanning Capabilities moving forward can be easily modified in the event of future changes, we are aiming to optimise this scanning by using PowerShell to create  more accurate discovery, rather than the previously utilised Hard-Coded Discovery in the Snow Inventory Agents.

In the DIS team, we would continually see support requests for SQL Server editions not being recognised correctly (Example: Microsoft SQL Server 2008 Express being recognised as Microsoft SQL Server 2008 Standard)

 

Benefits of the new SQL Script include:

  • More detailed information regarding the SQL Installations gathered such as instance name and instance status.
  • The script leverages the edition information from several sources, which result in an increased accuracy of SQL Edition discovery.
  • Operational excellence - A script based solution is easier to maintain, improve and troubleshoot.

 

Modifications have been developed in the Snow Inventory Agent from the 6.5 release and upwards to address the above issues and will be available with the 12th February 2020 release.

For more technical information on the changes made, and options to revert changes if you do not wish to use these updates, can be found here - KB0021443

For further support or questions, please reach out to your regional support contact or Partner.

Outcomes