Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello,
since yesterday I cannot retrieve any data from any warehouse. There is no error message. I checked the capacity app and there are CU(s) left. Do you have any idea, it is urgent for my client.
Inserting data into the warehouse works well.
There are about 400 open sessions, some of them older than 2 days. Unfortunately, I cannot kill them with the KILL command.
Solved! Go to Solution.
Can you try to Cancel the running queries from the warehouse and try again? You can Cancel the queries by selecting the three dots from the Warehouse and click on Query activity.
Hi @ChristophSDX,
Here's are some troubleshooting guide to help you identify and fix the problem: Having 400 open sessions can exhaust resources or cause contention, even if insertion works.
Run the following query to inspect all open sessions:
SELECT
session_id,
login_name,
host_name,
status,
start_time,
last_request_start_time,
last_request_end_time
FROM sys.dm_exec_sessions
WHERE status != 'background';
Focus on sessions that have been idle for long periods (status = 'sleeping'), as they may hold resources unnecessarily.
Blocked sessions can prevent data retrieval. Use this query to identify blocked and blocking sessions:
SELECT
blocking_session_id AS Blocker,
session_id AS Blocked,
wait_time,
wait_type,
resource_description
FROM sys.dm_exec_requests
WHERE blocking_session_id != 0;
Address the blocking sessions first.
Attempt to Kill Sessions: If KILL does not work, the issue might be related to permissions or system constraints. Alternatives:
Check for Table Locks: Insertion may work while retrieval fails due to locks. Identify locked tables with this query: Resolve locks by addressing the session causing them.
SELECT
t.name AS TableName,
l.request_mode,
l.resource_type
FROM sys.dm_tran_locks l
JOIN sys.tables t ON l.resource_associated_entity_id = t.object_id;
Review Query Performance Settings:
If no blocking or locking issues exist, the issue may be due to resource allocation or query execution limits:
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution helps you? or let us know if you need any further assistance here?
Your feedback is important to us, Looking forward to your response.
Thanks,
Prashanth Are
MS Fabric community support.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos"
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution helps you? or let us know if you need any further assistance here?
Your feedback is important to us, Looking forward to your response.
Thanks,
Prashanth Are
MS Fabric community support.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos"
Hi @ChristophSDX,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution helps you? or let us know if you need any further assistance here?
Your feedback is important to us, Looking forward to your response.
Thanks,
Prashanth Are
MS Fabric community support.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos"
Hi @ChristophSDX,
Here's are some troubleshooting guide to help you identify and fix the problem: Having 400 open sessions can exhaust resources or cause contention, even if insertion works.
Run the following query to inspect all open sessions:
SELECT
session_id,
login_name,
host_name,
status,
start_time,
last_request_start_time,
last_request_end_time
FROM sys.dm_exec_sessions
WHERE status != 'background';
Focus on sessions that have been idle for long periods (status = 'sleeping'), as they may hold resources unnecessarily.
Blocked sessions can prevent data retrieval. Use this query to identify blocked and blocking sessions:
SELECT
blocking_session_id AS Blocker,
session_id AS Blocked,
wait_time,
wait_type,
resource_description
FROM sys.dm_exec_requests
WHERE blocking_session_id != 0;
Address the blocking sessions first.
Attempt to Kill Sessions: If KILL does not work, the issue might be related to permissions or system constraints. Alternatives:
Check for Table Locks: Insertion may work while retrieval fails due to locks. Identify locked tables with this query: Resolve locks by addressing the session causing them.
SELECT
t.name AS TableName,
l.request_mode,
l.resource_type
FROM sys.dm_tran_locks l
JOIN sys.tables t ON l.resource_associated_entity_id = t.object_id;
Review Query Performance Settings:
If no blocking or locking issues exist, the issue may be due to resource allocation or query execution limits:
Can you try to Cancel the running queries from the warehouse and try again? You can Cancel the queries by selecting the three dots from the Warehouse and click on Query activity.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
3 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |