Reply
avatar user
Anonymous
Not applicable
Partially syndicated - Outbound

Error: Transaction was deadlocked on lock

Hello, since a few days ago, I have been getting the error message above for different transactions.

Through my research so far, I've roughly understood what a deadlock is, but I don't understand what I as a Power BI user can do to fix it.

 

The error has been appearing on even the simplest transactions. For example: 

1. In Power BI Desktop, I connected to a SQL database through Direct Query and loaded two tables. I tried to display them as tables in Power BI and got the deadlock error message for one of the tables. For the other table, it worked but loading the different columns took a few minutes at least. This is something that always worked without an issue, before. 

2. I tried create a dataflow by first transforming some tables in Power Query that I also loaded from the same database. At first, the loading time was significantly longer than before. At some point in the transforming process, I always got the deadlock error message.

 

To my understanding, this has to do with the interaction between the database and Power BI. How do I approach a possible solution for this problem?

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

Syndicated - Outbound

Talk to the DBA and see if you are the issue (too many queries) or they are the issue (too much pessimistic locking)

View solution in original post

1 REPLY 1
lbendlin
Super User
Super User

Syndicated - Outbound

Talk to the DBA and see if you are the issue (too many queries) or they are the issue (too much pessimistic locking)

avatar user

Helpful resources

Announcements
March PBI video - carousel

Power BI Monthly Update - March 2025

Check out the March 2025 Power BI update to learn about new features.

March2025 Carousel

Fabric Community Update - March 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors (Last Month)
Top Kudoed Authors (Last Month)