SQLServerCentral Article

What Power BI DirectQuery does to your SQL Server (and how to fix it)

Power BI DirectQuery can quietly overwhelm your SQL Server. Unlike Import mode, DirectQuery sends live T-SQL for every visual interaction, multiplying queries and placing heavy analytical load on the database. This article explains how to identify the worst offending DirectQuery queries, why the generated SQL is often inefficient, and what you can do from the database side, including indexing, Query Store, and reporting views, to improve performance. It also outlines practical changes on the Power BI side and when DirectQuery is simply the wrong architectural choice.

Blogs

How to Connect to SQL Server When Nothing Else Works – DAC

By

It's 2 AM. Your phone is going off. Users can't connect to the application,...

Get a Range of Sequence Values: #SQLNewBlogger

By

I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...

The Agent Era: When “How do I…?” Replaces “Where do I click?”

By

After a year away getting to grips with AI and its application across the...

Read the latest Blogs

Forums

Local Agents

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Local Agents

Detecting Deadlocks

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Detecting Deadlocks

Introducing the Relational Embedding Retrieval Pattern: Storing and Querying Vector Embeddings in SQL Server

By SQL Expert

Comments posted to this topic are about the item Introducing the Relational Embedding Retrieval...

Visit the forum

Question of the Day

Detecting Deadlocks

By default, how often is the SQL Server Database Engine checking for deadlocks?

See possible answers