Mirror, Mirror on the Wall: Fabric Mirroring for SQL Server at FabCon + SQLCon Europe 2026
If you have ever watched a production SQL Server grind to a crawl at 9am because forty people opened the same Power BI report, this session is for you. On Tuesday 29 September, David Postlethwaite and I are on stage at FabCon + SQLCon Europe in Barcelona to talk about Fabric Mirroring for SQL Server, and why it changes the argument between the DBA and the BI team for good.
The session is called Mirror, Mirror on the Wall, who can Sync their Data Best of all. It runs 11:15 to 12:15, it is pitched at Level 300, and it is built for data engineers, DBAs, Power BI developers and architects who need a cleaner way to serve analytics from operational databases. Here is what we are going to cover, and why I think it earns an hour of your conference.
The problem every DBA recognises
Most organisations still run reporting straight off the same SQL Server that runs the business. It starts innocently. One report, one DirectQuery connection, one analyst. Twelve months later there are 300 reports, a scheduled refresh window that overlaps with the overnight batch, and a helpdesk ticket every Monday morning that says “the system is slow”.
The usual fixes are all compromises. Readable secondaries cost licences. ETL into a warehouse means the data is hours old by the time anyone sees it. Throttling the BI team means the business stops getting answers. And the classic move of pointing Power BI at production with a “please be careful” note is not an architecture, it is a hope.
I have lost count of the health checks where the single biggest cause of blocking and CPU pressure was not the application at all. It was analytics workloads issuing thousands of SELECT statements against tables that were never indexed for that access pattern.
What Fabric Mirroring actually does
Mirroring in Microsoft Fabric gives you a near real-time copy of your SQL Server database in OneLake without the SELECT storm. Rather than querying your tables on a schedule, it reads change data from the transaction log and lands it as Delta tables in Fabric. Changes typically arrive in minutes. Your production instance carries the cost of change capture, which is light, instead of the cost of every report that anyone ever built.
Once the data is in OneLake it behaves like any other Fabric item. You get a SQL analytics endpoint you can query with T-SQL, a default semantic model, and the option to build Direct Lake models on top so Power BI reads from the lake rather than from your OLTP box. The mirrored data is also available to notebooks, warehouses and data agents, which matters if your AI roadmap depends on operational data that is currently locked behind a change board.
This is the part I want to be plain about, because the marketing can be breathless. Mirroring is not magic. There are prerequisites, supported versions, gateway considerations for on-premises instances, and data type edge cases. Some tables will not mirror cleanly first time. We will show you where the sharp edges are, because that is more useful than another demo where everything works.
What we will cover in the session
David runs SQL Server in a regulated financial services environment, so he brings the “will this pass a change review” perspective. I bring twenty years of consulting and training on the Microsoft data platform. Between us the session covers four things.
1. Spotting when analytics is hurting OLTP
Before you fix anything you need evidence. We will walk through the wait stats, Query Store patterns and blocking signatures that tell you reporting is the culprit, not the application. If you have ever had to prove this to a sceptical development manager, you will want these slides.
2. Setting up and configuring Mirroring for SQL Server
Live, end to end. Prerequisites on the SQL Server side, what the on-premises data gateway does and when you need it, how to choose which tables to mirror, and how to validate that changes are flowing. We will also cover what Mirroring costs you in Fabric capacity terms, because “it’s included” always has a footnote.
3. Redirecting Power BI with minimal change
The bit most teams underestimate. You have hundreds of reports pointing at a production connection string. We will show how to move them to the Fabric SQL endpoint or a Direct Lake model with as little rework as possible, what breaks, and how to phase the migration so nobody loses a dashboard on go-live day.
4. Real-time insight without production risk
Finally, the architecture conversation. Where Mirroring fits alongside shortcuts, Eventstreams and a conventional warehouse, and when you should choose something else. Mirroring is one tool. Knowing when not to use it is the mark of an architect rather than a demo jockey.
Why this matters commercially
Strip away the technology and this is a cost and risk conversation. Every hour a DBA spends firefighting report-induced blocking is an hour not spent on resilience or upgrades. Every delayed report is a decision made on stale numbers. And every workaround you bolt onto production to survive month end is technical debt with a compounding interest rate.
If Mirroring lets you take the analytics load off production, you get three things at once: a calmer OLTP system, fresher data for the business, and a landing zone in OneLake that your Fabric and AI initiatives can build on. That is a rare combination where the DBA, the BI lead and the CIO all get something they wanted.
Who should come
- DBAs who are tired of being the bottleneck and want an answer that is not “buy more cores”.
- Power BI developers who need fresher data without fighting the database team.
- Data engineers deciding between Mirroring, pipelines and CDC for their SQL Server sources.
- Architects mapping how operational data gets into Fabric without a rebuild.
Fair warning: we are in the same slot as the Microsoft SQL roadmap Corenote. If you want the roadmap, go and see Bob, Priya and Anna. If you want to leave with something you can configure the following Monday, come and see us. The recordings will cover the rest.
Beyond the session
FabCon + SQLCon Europe runs 28 September to 1 October at the CCIB in Barcelona, with over 4,000 Microsoft data professionals, 130 sessions and a full SQLCon track alongside Fabric. Microsoft’s own Shortcuts and Mirroring session on the Wednesday and the SQL Server AMA on the Thursday pair well with ours if you want to go deep on the topic across the week. David and I will both be around the Community Lounge afterwards, so bring your hardest “but what about” question.
Book your place
If your Power BI estate is leaning on a production SQL Server that was never designed to carry it, this is the hour to spend. Get your ticket for FabCon + SQLCon Europe 2026, add session T06 on Tuesday 29 September at 11:15 to your schedule, and come and find out who really can sync their data best of all.
The post Fabric Mirroring for SQL Server: Our FabCon Europe 2026 Session appeared first on Gethyn Ellis.
PakarPBN
A Private Blog Network (PBN) is a collection of websites that are controlled by a single individual or organization and used primarily to build backlinks to a “money site” in order to influence its ranking in search engines such as Google. The core idea behind a PBN is based on the importance of backlinks in Google’s ranking algorithm. Since Google views backlinks as signals of authority and trust, some website owners attempt to artificially create these signals through a controlled network of sites.
In a typical PBN setup, the owner acquires expired or aged domains that already have existing authority, backlinks, and history. These domains are rebuilt with new content and hosted separately, often using different IP addresses, hosting providers, themes, and ownership details to make them appear unrelated. Within the content published on these sites, links are strategically placed that point to the main website the owner wants to rank higher. By doing this, the owner attempts to pass link equity (also known as “link juice”) from the PBN sites to the target website.
The purpose of a PBN is to give the impression that the target website is naturally earning links from multiple independent sources. If done effectively, this can temporarily improve keyword rankings, increase organic visibility, and drive more traffic from search results.
Comments are closed, but trackbacks and pingbacks are open.