When we got back from FABCON // SQLCON Atlanta 2026, one thing was made immediately clear: the market is not short on interest. But it is short on certainty.
This year’s combined event brought Microsoft Fabric and Microsoft SQL audiences together under one roof, with Microsoft positioning the conference around a more unified data platform story across SQL, Azure SQL and Fabric. This was the first time that SQLCon was colocated with FabCon; with sessions spanning SQL Server, Azure SQL, SQL in Fabric, migration, modernization, optimization, security and, of course, AI.
Microsoft’s own post-event recap said the event was all about bringing the power of Microsoft SQL and Microsoft Fabric together on a single platform.
From our perspective at WhereScape, that framing matched what we heard too; in conversation after conversation. People are very much interested in modernization. They are thinking seriously about Microsoft Fabric. They are preparing data foundations for AI. But many are still trying to work out the timing, the migration path and vitally, the safest way to move … without breaking what already works.
That made this year’s event especially valuable for us. Our booth messaging focused on a practical idea: modernize your data environment by evolving it, not by ripping it out and starting again. Judging by the conversations we had in Atlanta, that idea landed.
Our Big Takeaway: Many Teams Are in the ‘Not Quite Yet’ Phase with Migrations
One of the most consistent talking points we heard at FabCon / SQLCon Atlanta was this: a lot of organizations know they are going to move, but many are not moving immediately.
Some attendees told us they expected to make a move in the next 6 to 12 months. Others were clearly doing early planning, gathering options and pressure-testing what their future architecture might look like. That matters to us because it tells us the market is cautious, when it comes to migrations.
We also noticed something else: there were still plenty of teams running on-premises SQL Server. That was one of the biggest contrasts with the mood we saw back at FabCon Vienna in 2025, where more attendees seemed already committed to Azure SQL or broader cloud-first patterns. In Atlanta, the SQL Server on-prem base felt much more visible. That helps explain why our SQL Server modernization angle resonated so strongly as a theme.
This also fits what we are seeing across our own content and product discussions. Our recent panel, How to Modernize SQL Server, Without Breaking What Already Works, was built around exactly this tension: organizations know modernization matters, but a full rip-and-replace approach is often too risky for production environments that still carry out business critical reporting and analytics workloads.
Microsoft Fabric Was Everywhere But The Conversation Has Matured
It would be impossible to write a FabCon debrief without talking about Microsoft Fabric, right? Fabric discussions were everywhere at the event, but the tone of them felt more grounded than at some earlier events we attended.
Instead of pure launch energy, more conversations were about implementation details: how Fabric fits into existing estates, how it supports warehouse modernization, how it interacts with semantic models and especially how teams can use it to build an environment that is more readable to AI systems and agents.
There was quite a buzz about Fabric IQ and what might come next there. Microsoft also continues to position semantic models as the logical business-facing representation of an analytical domain, typically built around facts and dimensions.
It’s worth noting that Microsoft’s own documentation now positions Fabric as an end-to-end analytics platform spanning ingestion, engineering, warehouse, science, real-time intelligence, and reporting over a shared compute and storage model. Fabric IQ, which is currently in preview, is described by Microsoft as a workload for unifying data across OneLake and organizing it according to the language of the business; so it can be exposed consistently to analytics, AI agents and applications – something that clearly piqued the interest of many in attendance.
That is important to shine a light on because it explains why so many conversations in Atlanta centered on preparation. Fabric is not just another destination platform. For many teams, it represents a chance to clean up the warehouse, standardize patterns, strengthen semantic consistency and make the environment more useful for both analytics and AI.
That is also why we think the Fabric conversation is increasingly tied to the AI-readiness conversation. If a team wants AI to work against governed, understandable, trusted business data, then the quality of the semantic layer, the quality of lineage and the quality of warehouse structure matter a lot more. That is exactly why we continue to emphasize AI-ready data, dependable data governance and lineage, and automated documentation as part of the modernization story, not as separate afterthoughts.
Business Intelligence Professionals Were a Big Part of the Story
Another noticeable feature of the event was how many business intelligence professionals were in the room.
That matters because BI audiences often ask a slightly different question than platform buyers or engineering teams. Sure, they’re still interested in modernization… but they tend to focus more quickly on practical outcomes e.g.:
- How do we keep reporting stable while the platform changes?
- How do we move without disrupting dashboards and semantic models?
- How do we improve trust and consistency in what business users see?
- How do we make the data estate easier to understand for more people?
These are not “soft” questions. They are exactly the questions that determine whether modernization efforts earn credibility or crash out internally. It is one thing to talk about lakehouses, semantic layers or medallion design. It is another thing to preserve the reliability of reporting while actually making those changes.
That is where we think metadata-driven automation has a really important advantage. It reduces the amount of manual rework required during transitions and it helps teams keep design, build, documentation and lineage aligned as the environment changes. That is a major part of why we continue to position our broader data warehouse automation capabilities as modernization tools, not just developer productivity tools.
Our Booth Positioning Worked Because the Market Is Tired of False Choices
This year, we chose to lead with modernization, particularly the idea that teams should evolve safely rather than throw away what still works.
That turned out to be a strong fit for the event.
A lot of migration messaging in the market still defaults to a false dichotomy: stay where you are and fall behind, or rip everything out and move wholesale. But most real-world teams do not work that way. They have legacy dependencies. They have reporting commitments. They have limited teams. They have political realities. And they often have more platform optionality than budget or time.
That is why our viewpoint was simple: modernization should create options, not force disruption.
Interestingly, we were not the only ones speaking about this topic. Other vendors and service providers were clearly leaning into adjacent themes around migration, modernization and future-proofing. But the WhereScape difference stood out in a useful way: many attendees understood quickly that we are not primarily asking them to buy a large block of services to get from A to B. We provide software that helps them accelerate the move themselves, or with lighter-touch support, while reducing dependency on slow, manual rebuilds.
That matters a lot in a market where service-heavy migration programs can become expensive, slow and hard to justify. Many are waking up to this reality.
One story from the event summed it up perfectly. In one conversation, our Head of Sales spoke to someone who had recently completed a five-year migration effort. Based on what he described, we believe that the same move could have taken closer to two months with WhereScape. We just met him too late.That is the type of frustration we exist to reduce.
Why Migration to Fabric Is Becoming a Bigger, More Practical Question
A lot of the Fabric discussion in Atlanta was not just about Fabric itself. It was about how to actually get there.
That aligns with what we have been seeing in our own content and customer conversations for some time. Back in 2024, we published our guide on streamlining data migration to Microsoft Fabric with WhereScape. Interestingly, this pain point that this guide set out to allay was one we heard again in Atlanta: migration complexity, manual coding overhead, governance and the need to build on Fabric in a way that is repeatable… rather than brittle.
We also think there is a useful lesson here for teams still planning their next move. Migration should not be treated as a one-time problem to ‘fix’. It is also a chance to improve how the environment is designed, governed, and maintained. If teams simply lift old patterns into a new platform, then they often carry old fragility with them.
That is why we often encourage people to think in terms of how to modernize now, migrate later – or, at the very least, stay flexible later.
If you yourself are planning a move from SQL Server toward Azure SQL or Fabric, our on-demand session Migrating from SQL Server to Azure & Microsoft Fabric: What Works, What Breaks, and How to Avoid Costly Mistakes, is a useful companion resource. Microsoft’s own migration guidance forAzure SQL Managed Instance and broader Azure SQL migration guides are also worth reviewing if you are going into planning mode.
The Medallion and Semantic Layer Conversations Are Moving Closer Together
Another thread of conversations we heard repeatedly was the link between medallion architecture, semantic consistency and AI-readiness.
This came up in the context of Fabric specifically, but it has broader implications. Teams are increasingly thinking beyond raw ingestion and transformation. They want to know how Bronze, Silver and Gold layers connect to semantic models, reporting and AI consumption. They want to know whether the architecture can support governed meaning, not just governed storage.
That is one reason our upcoming (as of March 2026) Customer POV session with IT-Logix and the Solina Foundation is so relevant right now. It is focused on exactly this kind of real-world implementation, including Bronze, Silver, Gold structuring in Fabric, model-driven development, repeatable pipelines and how teams build a stronger foundation for AI-ready analytics.
We think this session is especially timely,as it moves the conversation from theory to evidence.
Our Own Session – Adding a LLM Button to WhereScape 3D Demo
One of the highlights of the event for us was our own session, hosted by Endika Pascual, Solutions Architect at WhereScape. From what we saw on the ground, it was the best-attended WhereScape event at the conference, which was encouraging because it confirmed there is strong appetite for practical, hands-on guidance.
While Endika’ full session was exclusively for event attendees, below you will find a short on-screen demo that was shared during it. It shows how a button can be added to WhereScape 3D, enabling LLM functionality.
Recap: What The Event Really Taught Us
If we step back, our biggest conclusion from FabCon / SQLCon Atlanta 2026 is this:
The market is not asking whether modernization matters, it is asking how to modernize without losing control.
That question showed up in different forms all week e.g.:
- How do we move from SQL Server to Azure SQL or Fabric without destabilizing reporting?
- How do we make our warehouse more useful for AI without starting from zero?
- How do we modernize architecture but keep the parts that still work?
- How do we migrate faster without buying years of services?
- How do we create a cleaner semantic foundation for analytics and agents?
Those are exactly the questions we want to help solve.
From our perspective, the answer is not a slogan. It is a delivery model that looks like this:
- Use automation to reduce manual rework.
- Use metadata to keep design, lineage and documentation aligned.
- Use modernization to create options, not dead ends.
- Use migration as a chance to strengthen governance and semantic consistency.
- Use platforms like Fabric as part of a broader architectural evolution, not as an excuse to repeat old mistakes on newer infrastructure.
Final Thoughts
FABCON // SQLCON Atlanta 2026 gave us a useful snapshot of where the market is right now.
Fabric is real now. AI preparation is accelerating. Semantic consistency matters more than ever. SQL Server is still deeply embedded in many organizations. Migrations are happening but often still on the near-term roadmap, rather than the immediate one. And teams want credible modernization paths that do not depend on high-risk rebuilds.
For us, that was encouraging. It confirmed that our core message still fits the moment: evolve your data environment safely, modernize with automation, and build a foundation that is ready for both analytics and AI.
And if you were in Atlanta and want to compare notes, or if you missed the event but are planning a move toward Fabric, Azure SQL or broader data warehouse modernization, we would be happy to talk.
