MDS and DQS - Beyond the TLAs to Data Quality
summary
Demonstrates using Microsoft Data Quality Services with Master Data Services and SSIS DQS components to profile, cleanse and match records, reference third‑party sets (Azure Data Market, Melissa) and audit every correction. Live demos show concrete counts — 1272 imported / 311 new addresses / 502 unique postcodes (785 added, 502 uniques) — and notes performance gains from hours to under an hour after CU1. Exports land in SQL/CSV/Excel and MDS centralizes master records, cutting redundant data ~20–40%.
AI-written summary · about
chapters (14)
- 0:00MDS and DQS overview
- 1:49Speaker background and session overview
- 4:36Why data quality matters
- 9:07Microsoft data quality overview
- 12:41DQS client demo
- 27:30Data cleansing and matching
- 36:08SQL 2012 SP1 improvements
- 38:15Domain management in DQS
- 43:11Historical analysis in DQS
- 47:17Master Data Services intro
- 50:07Centralizing data with MDS
- 55:46Setting up MDS database
- 57:13MDS and DQS integration
- 58:17Data quality benefits and next steps
related talks
44mData Quality Management
41mData Quality Management: The Good, The Bad, and The Messy
35mApplying Data Quality Monitoring
24mHow Graph-based Master Data Management Accelerates Data-powered Projects
21mData quality as a product
24mDataEngBytes 2023 - MEL-T1-05 - Izzudin Hafiz
01h 02mShift Data Quality Left with Data Mesh Principles
21mUsing Semarchy to Master Data Management