Microsoft SQL Server Data Quality Services Recognition

Loading

carolai asked a question.

November 26, 2020 at 12:33 PM

Microsoft SQL Server Data Quality Services Recognition

Hi all

I assume a lot of you also are using Microsoft SQL Servers.

Since some time I noticed that SLM shows SQL Server Standard editions and an additional MS SQL Server Data Quality Services. DQS is not included in Standard edition and so SLM shows this as uncovered application.

So I first asked my colleagues, who installed that and they told me they are not aware of installing DQS. So I staretd a lot of research, had several discussions with our consultant and also Snow. Seems during installation of SQL Server Standard you can also checkmark Data Quality Services and could be used as part of Integration Services:

https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15

Integration Services is a set of graphical tools and programmable objects for moving, copying, and transforming data. It also includes the Data Quality Services (DQS) component for Integration Services.

At the moment result is, that SRS is recognizing DQS based on only a regkey, but no executable. I asked SRS team to change the recognition rules if possible, but they told me they don't know an executable, and I cannot tell them, because we don't have an installation.

Does perhaps anybody of you use DQS and can tell me how this can be recognized correctly?

Many thanks

This content is a preview of a link.

docs.microsoft.com

https://docs.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-version-15?view=sql-server-ver15

Top Rated Answers

Portal User
6 years ago
Few things (and a shameless plug for one of my Idea submissions):
1) the Binary for DQS is DataQualityServices.exe
2) The path pattern is "%Program Files%\Microsoft SQL Server\%Version%\Tools\Binn\DQ\DataQualityServices.exe"
3) "Data Quality Client" does not require licensing it is only the SQL that is processing that requires the licensing.
4) Developer edition (2016 and above) contain this feature and is valid in for non-production ( think this is gray zone as how can you prove the data is non-prod data? oh well)
5) SNOW does not currently pickup WSFC and I've sumitted an IDEA to have it included. Its related to SQL as you can haver active/passive setup and only the active node need to be licensed. Unfortunately MAP picks this up but SNWO does not. This is a request to vote for my idea if you like it :) https://ideas.snowsoftware.com/ideas/IDEAS-I-948

Expand Post
Selected as Best

All Answers

dschigt
6 years ago
Hi Carola,

When checking a couple of computers in our estate, I do see indeed MS SQL installed. These are all based upon, indeed, a registry key.
Giving a bit more backgroud from our end: we had quite some difficulty in getting proper MS SQL editions and versions detected for quite a long period of time.
Currently we have Snow agent 6.5.0 deployed, including powershell script: SnowScript - Scan-MicrosoftSQLServer 1.2.
This helped enormously to get back on track regarding correct MS SQL detection.
Does this perhaps help for you?

Best regards,

Detlev Schigt

Expand Post
carolai
6 years ago
Hi Detlev,

Thanks for your reply.
Unfortunately the problem of Data Quality Services detection cannot be solved with that powershell scripts. Also machines with that SnowScript - Scan-MicrosoftSQLServer 1.2. are reporting a MS SQL Server * Standard edition (any version 2012, 2016, 2019) and additionally in some cases a MS SQL Server Data Quality Services.

I know Data Quality Services is not part of SQL Server Standard edition, so SLM do not mark this as bundle content of Standard edition.

I think my colleagues marked everything during the SQL Standard installation. So the regkey was created. But as far as I read in Internet, this does not mean there was an installation of Data Quality Services. With that checkmark only a DQSinstall.exe would be downloaded. But as long as you don't execute this DQS Install, there should be no impact.
Expand Post
- Portal User
  6 years ago
  Few things (and a shameless plug for one of my Idea submissions):
  1) the Binary for DQS is DataQualityServices.exe
  2) The path pattern is "%Program Files%\Microsoft SQL Server\%Version%\Tools\Binn\DQ\DataQualityServices.exe"
  3) "Data Quality Client" does not require licensing it is only the SQL that is processing that requires the licensing.
  4) Developer edition (2016 and above) contain this feature and is valid in for non-production ( think this is gray zone as how can you prove the data is non-prod data? oh well)
  5) SNOW does not currently pickup WSFC and I've sumitted an IDEA to have it included. Its related to SQL as you can haver active/passive setup and only the active node need to be licensed. Unfortunately MAP picks this up but SNWO does not. This is a request to vote for my idea if you like it :) https://ideas.snowsoftware.com/ideas/IDEAS-I-948
  
  Expand Post
  Selected as Best
  - carolai
    6 years ago
    Hi Kris,
    
    Thank you very much for your help. I think this is the information DIS team required to adapt the SRS rules. Hope this then may help.
    
    Your idea is great and I voted for it. When active/passive could be already evaluated by the powershell, then this would save us time. We just ask our colleagues and then document this in SLM by using the exctended coverage. But this is a manual process and when it could be evaluated automatically, this really would help
    Expand Post

Related Product Forums

→ Flexera One

→ FlexNet Manager

→ Snow License Manager

Need help finding an answer?

Ask a Question →

Loading

Microsoft SQL Server Data Quality Services Recognition