March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
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?
Solved! Go to Solution.
Talk to the DBA and see if you are the issue (too many queries) or they are the issue (too much pessimistic locking)
Talk to the DBA and see if you are the issue (too many queries) or they are the issue (too much pessimistic locking)
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
125 | |
85 | |
69 | |
54 | |
45 |
User | Count |
---|---|
204 | |
106 | |
98 | |
65 | |
54 |