Back to blog
Ronald Kraijesteijn, Founder
·November 19, 2026·6 min read

Your own SQL Server or your Fabric tenant: where should your master data live?

Home/Blog/Your own SQL Server or your Fabric tenant: where should your master data live?
Three places your master data can live
Your own SQL Server
Primentra
A database on a server you run, in your building or your own virtual machine.
€7,500 a year, flat
Your Fabric tenant
Profisee Anywhere (GA December 2026)
A Fabric SQL database in your Microsoft Fabric tenant, in Microsoft's data centers.
On request
The vendor's cloud
Profisee cloud and most SaaS MDM
The vendor's own cloud, under its contract with you.
On request

Two announcements landed in the same week. On 12 November 2026 Microsoft retired Purview Data Governance: the Unified Catalog, Data Map and Workflows, with end of support by 12 November 2027. Microsoft now points governance to the OneLake catalog in Fabric. Its data security and compliance offerings stay as they are.

Six days later Profisee announced Profisee Anywhere for Microsoft Fabric. It keeps master data in a Fabric SQL database in your own Fabric tenant, and it ships in December. Profisee presents it as an answer to data sovereignty.

So if your team runs on the Microsoft stack, the question of where master data should live just came back. Add MDS, which Microsoft removed from SQL Server 2025, and three Microsoft-stack pieces you may have planned around have moved in one year.

A tenant is not a server

"Your own tenant" and "your own server" both answer the question of whose data it is. They give different answers to the question of where it sits.

A Fabric tenant is your slice of Microsoft's cloud. You hold the keys to it, Microsoft runs the hardware, and you pay for Fabric capacity on top of the MDM license. For a company that already runs its reporting in Fabric, that can be the right home. The master data sits next to the reports that read it.

Your own SQL Server is a machine you run, in your building or in a virtual machine you control. Your DBA backs it up with the jobs that already back up everything else. Your network rules decide who reaches it. When an auditor asks where the supplier master lives, the answer is a server name.

Neither answer is wrong. They suit different companies. A hospital, a municipality or an insurer with a data protection officer who wants the data inside the building will often pick the server. A company that moved its whole data platform to Fabric last year will often pick the tenant.

Five questions that settle it

  1. Where is the golden record stored, as a place you can name? A server, a tenant region, or a vendor cloud. Ask for it in writing.
  2. Who makes the backup, and can you restore it without the vendor? If the restore needs a support ticket, the data is less yours than the contract says.
  3. What runs underneath, and who pays for it? A Fabric tenant needs Fabric capacity. Your own server needs a SQL Server license you probably already have.
  4. How is the price set? Per record, per data volume, per user, or flat. And what does year three cost? Our post on MDM renewal pricing lists the clauses to read.
  5. What breaks when Microsoft moves again? Purview Data Governance and MDS both show that a Microsoft-stack piece can go. SQL Server itself has outlived both, so a tool that only needs SQL Server carries the least of that risk.

Where Primentra stands

We build Primentra, so read this part as our view. Primentra keeps your master data in a database on your own SQL Server, 2017 or later. It runs as a Windows service on your own machine. We never receive the data.

Downstream systems read it through Integration Views, ordinary SQL Server views. Anything that reads a SQL Server view can read them, from an SSIS package to a Power BI report. If you come from MDS, MDS Direct Migration rebuilds your subscription views with the same names.

The price is €7,500 a year, flat, with no per-user or per-record fee. A renewal can rise by the Dutch consumer price index at most. Profisee prices on request and by data volume, as our Profisee comparison sets out.

Profisee is the better fit in one clear case: you match the same customer from several source systems into one golden record, at enterprise scale, and your data platform already lives in Fabric. If your team replaces MDS and wants the data on its own server, try Primentra for 60 days on a copy of your model.

Common questions

Is Microsoft Purview being retired?

Purview Data Governance is. On 12 November 2026 Microsoft announced its retirement, with end of support by 12 November 2027. That covers the Unified Catalog, Data Map and Workflows. Microsoft says the Purview data security and compliance offerings are unchanged, and points governance to the OneLake catalog in Fabric.

Where does Profisee Anywhere store master data?

In a Fabric SQL database in the customer's own Fabric tenant, according to Profisee's announcement of 18 November 2026. General availability is planned for December 2026.

Where does Primentra store master data?

In a database on your own SQL Server, 2017 or later, on a server you run. Primentra is a Windows service on your own machine, and we never receive the data.

More from the blog

MDS broken after SQL Server 2022 CU27 or CU28: what to do while Microsoft works on a fix7 min readWhat is Profisee MDM? Editions, pricing, and its link to Microsoft MDS7 min readDQS went out in the same release as MDS, and almost nobody noticed8 min read

Ready to migrate from Microsoft MDS?

Download Primentra and run it on your own server, or try the live demo first. All features included.

Download free trialTry demoCompare MDM tools