A Fine Slice Of SQL Server
As companies adopt Microsoft Fabric, the distance between backend artifact and Semantic Model is smaller than ever, and it feels more obvious than ever to push some of those local transformations to your Fabric Storage item of choice.
The question is. How do you do that? There are many options:
Read on for those options. Jon focuses on one for people with less database experience.
Leave a CommentPradeep Srikakolapu says good riddance:
In our earlier announcement, we shared that newly created data warehouses, lakehouses and other items in Microsoft Fabric would no longer automatically generate default semantic models. This change allows customers to have more control over their modeling experience and to explicitly choose when and how to create semantic models.
Starting November 20, 2025, Power BI *default* semantic models are disconnected from their item and become independent semantic models.
Click through for an overview of those changes and how you can get rid of the default models you may still have hanging around.
Leave a CommentAndy Cutler begins a new series on Microsoft Fabric architecture:
Our Fabric Architecture journey starts with Azure Tenants (the kick-off blog in this series is here with a few jumping-off links to get started with thinking about Fabric Architecture). If you’re ready to spent time sketching out your Fabric Capacity planning, workspace strategy, domain topology, lakehouse/warehouse creation, data loading processes…you might want to stop for a minute and think about tenants. The question I’d like you to consider is “What do I need to know when working with a single or a multi-tenancy approach?” Let’s unpack this question because while it might sound like a simple list, it actually shapes your governance, scalability, and Fabric operational model. If you’re a seasoned Azure Architect veteran then you already know how to decide between single and multi-tenant cloud rollouts (also, please comment if you have anything to add please), if you work with Fabric/Data and don’t really dive into Azure architecture on a daily basis then please stick around. Hopefully this blog gets you thinking about single/multi-tenant architectures and the benefits/costs.
Read on for a dive into what tenants are, the benefits of single- versus multi-tenancy, and how it all ties into Fabric.
Leave a CommentGilbert Quevauvilliers scales it up:
This blog post is going to detail how I run the load test and then view the load testing results to determine how the capacity has coped when I increase the number of users.
Along with demonstrating how I automated the load testing without having to run it manually!
Read on for those details.
Leave a CommentJon Vöge finishes spring cleaning in November:
With the above assessments of Task Flows and Tags in mind – How could we go about implementing these different solutions to item labeling in practice today?
The answer? It depends on your Domain, Workspace and Workspace Folder strategy.
Read on to learn more about what Task Flows and Tags are, and how you can use them for organization.
Comments closedGuy Reginiano announces a new tool:
As your KQL database grows, tables gather data from several Eventstreams, functions connect different tables, update policies move and transform data, and materialized views quietly keep aggregated data up to date – all working together behind the scenes
It’s powerful, but it can also be hard to see the full picture.
That’s exactly why we built the Entity Diagram – to give you a simple, visual way to explore how everything in your database connects.
Click through to see how it works.
Comments closedThis month’s update delivers key advancements across Microsoft Fabric, including enhanced security with Outbound Access Protection and Workspace-Level Private Link, smarter data engineering features like Adaptive Target File Size, and new integrations such as Data Agent in Lakehouse. Together, these improvements streamline workflows and strengthen data governance for users.
The list doesn’t feel quite as long as the prior couple of months, but there’s still a lot of content on here.
Comments closedSunitha Muthukrishna makes an announcement:
The Fabric Core extension for Visual Studio Code is now officially open source. This milestone underscores our commitment to transparency, collaboration with the developer community, and providing robust tools to empower innovation with Microsoft Fabric.
Read on for the practical details around this announcement.
Comments closedGilbert Quevauvilliers continues a series on load testing a Microsoft Fabric lakehouse:
In today’s blog post I am going to show you how to set up the Lakehouse and Fabric notebooks so that you can then configure it to be ready to be used with the JSON file we created in the previous blog post.
Click through for links to the notebooks, as well as how all of the pieces fit together.
Comments closedFreddy Santos takes us through the latest with respect to security in OneLake:
OneLake Security centralizes fine-grained data access for Microsoft Fabric data items and enforces it consistently across engines.
Currently in Preview and opt-in per item, it lets you define roles over tables or folders and optionally add Row-Level Security (RLS) and Column-Level Security (CLS) policies. These definitions govern what users can see across Fabric experiences.
Read on to see what you can do.
Comments closed