In 2018, Niko Neugebauer — a SQL Server MVP and one of the most careful database analysts in the community — published a detailed breakdown of the MDS database configuration. Compat level 110. TORN_PAGE_DETECTION. No Query Store. 8 MB log growth. He documented every setting that was wrong, explained why it mattered, and published it for anyone to read.
Seven years later, Microsoft shipped SQL Server 2025 without MDS. The product was gone. And every single problem Niko identified in 2018 was still there in the final version.
This isn't a post about the deprecation announcement — we covered that already. This is about the years before it, when the signs were in plain sight for anyone paying attention.
The database was stuck in 2012
MDS installed itself with compatibility level 110 — the setting for SQL Server 2012. Not 120. Not 140. The 2012 compat level. On a product that shipped with SQL Server 2016, 2017, and 2019.
Compat level isn't cosmetic. It controls which query optimizer features are available. Level 110 blocks Intelligent Query Processing, Query Store, and Batch Execution Mode on Rowstore — features Microsoft spent years building into the engine. In practice: slower queries, no performance monitoring, and no way to tune the engine without going around MDS's own configuration. On a platform managing your organization's most critical reference data, you were running a query optimizer from 2012.
Then there's Page Verify. MDS installed with TORN_PAGE_DETECTION, a page integrity mode Microsoft deprecated in SQL Server 2005. The recommended setting — CHECKSUM — has been standard for nearly twenty years. Using the deprecated mode “significantly increases chances of undetected corruption.” For a master data platform, where the integrity of your golden records is the entire point, that was a serious flaw.
Query Store was off by default. Columnstore indexes weren't used, despite millions of rows being common in real deployments. And referential integrity — foreign key constraints between tables — was absent. For a product whose core value is ensuring data quality and consistency, the database itself enforced none of it.
The product stopped moving
By 2018, meaningful MDS development had effectively stopped. The feature list didn't grow. Performance didn't improve. The Excel Add-in didn't get new capabilities. Updates arrived, but they were security patches, not improvements.
By 2022, this was an open secret. On Microsoft's own Q&A forum, users asking about the MDS roadmap were getting answers that translated to: there isn't one. Microsoft staff acknowledged that MDS would “likely not get many (if any) future feature updates” and would receive only security updates going forward.
That's vendor EOL language. They just weren't using those words yet. The organizations most affected were the ones that had invested the most: hundreds of users, dozens of entities, years of configured business rules. The longer you'd been on MDS, the harder the silence was to ignore.
When your own updates break your own product
2025 brought a particular kind of chaos to MDS deployments. The problems didn't come from the deprecation announcement — they came from Microsoft's own update pipeline.
In April 2025, Microsoft's Office Security team released version 2504 (build 18730.20030). The update disabled ActiveX controls by default — a reasonable security decision, since ActiveX is a legitimate attack surface. The problem: the MDS Excel Add-in depends on ActiveX to connect to the MDS database. When it was switched off, the add-in stopped working overnight across every organization that received the update. The workaround was manually re-enabling ActiveX in the Trust Center on each affected machine, which undid the security improvement the update had just made.
Four months later, the KB5065222 Windows cumulative update (September 2025) broke the MDS web application on every environment that received it. No confirmed fix was published before SQL Server 2025 shipped without MDS. Microsoft's own update infrastructure had spent the year breaking Microsoft's own product.
“Just use Azure Logic Apps”
When Microsoft confirmed MDS wouldn't be included in SQL Server 2025, the suggested migration paths were Azure Purview and Azure Logic Apps.
Azure Purview is a data governance and metadata catalog. It documents what data exists and where — it's not a master data management tool. It doesn't replace stewardship workflows, approval processes, or golden record management. Describing it as an MDS replacement is roughly like recommending a map when someone's car breaks down. The SQL Server 2025 alternatives post breaks down exactly what each suggested path does and doesn't cover.
Azure Logic Apps was harder to parse. The guidance essentially meant: build your own MDM solution using cloud workflow automation. SQL Server MVP Koen Verbeeck was direct about what that actually requires — implementing the equivalent of MDS's capabilities this way means rewriting all of them from scratch. For organizations with years of business rules, hundreds of configured entities, and teams trained on specific workflows, “rewrite it yourself” isn't a migration path. It's a project.
What you're actually dealing with
If you're running MDS today, the situation is straightforward:
- Your database is running at SQL Server 2012 compatibility level — unless you manually changed it, which required going around MDS's own setup scripts.
- Your Excel Add-in depends on ActiveX, which Microsoft has already disabled once in a routine security update.
- The web application has been broken by at least one recent Windows cumulative update, with no confirmed fix before the product was removed.
- Microsoft's suggested replacement products don't do what MDS does.
- SQL Server 2022 extended support runs to 2028. After that, even security patches stop.
The product was broken years before Microsoft removed it. The removal made it official. If you're now evaluating what comes next, our MDS alternatives comparison covers all the major options with pricing and a direct migration path for each.
We built Primentra after too many client calls where we were explaining what was broken without a better answer to give them. It runs on your SQL Server, installs in a day, and covers the same ground MDS did — without the decade of deferred maintenance. It's self-hosted on your infrastructure, so no SaaS vendor lock-in. The migration guide covers how to move your model and data across from MDS.