What is our primary use case?
I use
Microsoft Data Quality Services to handle data inconsistencies, such as missing or improperly formatted data. The tool serves purposes like ensuring data quality when using
SQL Server, as it comes with a complete pack of
Data Quality Services, Master Data Services,
SQL Server Integration Services,
SQL Server Reporting Services, and
SQL Server Analysis Services.
What is most valuable?
The primary advantage of
Microsoft Data Quality Services is its capability to automate certain tasks, which are otherwise achieved through SQL queries. For example, it helps in handling scenarios where XYZ@@gmail.com needs correction to XYZ@gmail.com, or multiple names like USA, US, and United States of America need consolidation into a single format. It rejects unsuitable records, simplifying the review process. Additionally, its inclusion in the SQL Server package makes it cost-effective, as no extra cost is involved.
What needs improvement?
Multiple areas in Microsoft Data Quality Services could be improved, such as its ability to perform changes automatically, as it currently identifies but does not correct data issues. Regular expression processing is complicated and slow. Technical support from Microsoft is poor, as they do not provide adequate assistance with issues encountered in integration or forming automation. Sometimes solutions to problems take several weeks due to a lack of support, relying instead on personal networks and experience.
For how long have I used the solution?
I have been using Microsoft Data Quality Services for around five years.
What was my experience with deployment of the solution?
The deployment requires adjusting permissions, as certain job automation tasks fail due to access issues. An approach was crafted with a pseudo user executing jobs, which solved the problem eventually, but without guidance from Microsoft.
What do I think about the stability of the solution?
Microsoft Data Quality Services is not a perfectly stable system, as minor bugs can occur when dealing with high volumes of data. The system, along with Master Data Services, experiences glitches, especially when using fuzzy logic.
What do I think about the scalability of the solution?
I think Microsoft Data Quality Services can be easily scaled.
How are customer service and support?
The technical support from Microsoft for Microsoft Data Quality Services is poor. They often do not respond well when issues are raised, and I frequently turn to online searches for solutions.
How would you rate customer service and support?
How was the initial setup?
During the installation of SQL Server, the option to install Microsoft Data Quality Services and accompanying tools like Master Data Services is available. It is a straightforward process that ensures these solutions are set up together with SQL Server.
What about the implementation team?
I have been handling the entire BI project from start to finish on my own, from requirement gathering to deployment.
What's my experience with pricing, setup cost, and licensing?
Microsoft Data Quality Services comes as part of SQL Server without additional costs, making it a competitive solution.
What other advice do I have?
Integration of MDS and DQS components in
SSIS packages can be complex, requiring specific access permissions not clarified by standard documentation or support. I rate Microsoft Data Quality Services a six to seven out of ten. I would like to remain anonymous in the review except for my name. My job title has changed from Senior Software Developer to Technical Lead.
Which deployment model are you using for this solution?
On-premises
*Disclosure: My company does not have a business relationship with this vendor other than being a customer.
