Incomplete MSFT SQL Server Edition Information in Software Discovery Model

[Nurulaslah Anua]

This discovery model, "Microsoft SQL Server 2016 (64-bit)," doesn't specify an edition. We discovered 50 devices with this model installed.

We searched these 50 devices in the MS-SQL instances table (cmdb_ci_db_mssql_instance) and found multiple editions (Enterprise and Standard).

How can we normalize the discovery model "Microsoft SQL Server 2016 (64-bit)" when some devices have the Standard edition and others have the Enterprise edition?

search the same devices from MS-SQL instances table

Also without edition our SAM ELP will be incorrect. Please help!

[MikeW_SAMBeast]

This is bang on the money, David. The only thing that slightly irritates me is that the OS discovery pattern also discovers the SQL Server install (version only) and keeps this record as 'installed software'. It would be great if the post-script deleted these records discovered by the OS pattern, but I guess you can't have everything. 🙂 Like you say, if I exclude SQL Server install records where "Created by Application Pattern" = false, then I'm good to go.

[dreinhardt]

Hi @MikeW_SAMBeast @Community Alums , thanks for your comments and insights into the discovery process and the different sources and sw install results (generic without edition based on add/remove & detailed install based on Pattern). I fully agree with you, the add/remove sw installs are annoying and the recon stills shows SQL Server installs without editions to be licensed.

 @MikeW_SAMBeast - could you please share details on your comment "Like you say, if I exclude SQL Server install records where "Created by Application Pattern" = false, then I'm good to go." Do you work with "Install Conditions" or setting the not needed sw-installs to Active = False? Looking forward to this and the upcoming discussion.

Best, Dennis

[mikew_samexpert]

Hi Dennis - I configure the sw install conditions so that the license calculator only counts SQL Server sw installs where "Created by Application Pattern" = true.

[dreinhardt]

@mikew_samexpert , thanks. How do you handle/capture the devices/installations where the discovery pattern is unable to capture the correct edition? Are these tracked in a separate software model ?

[mikew_samexpert]

Hi Dennis,

These days, Discovery collects the versions and editions of the base SQL Server database installation. Back in the day AND for SQL Server installs discovered by SCCM, where no Edition value is fetched, the only way around this is to speak with the SQL Server DBA and get the Edition values and then insert this in the Edition Over-Ride field on the sw installation CI record.

There are still a couple of gaps that Discovery has in collecting Edition values linked to a couple of the SQL Server components and for those, I would create separate software models whilst I undertake the journey of finding the correct Edition values.