I've been encountering issues with Azure Synapse Serverless SQL. Every time I run a SQL query, I keep getting errors saying 'content cannot be listed.' Interestingly, I can still reference the data lake directly using a dataflow connector without any problems. Anyone else experiencing this issue, especially in the UK South region? I've also noticed that SQL queries that don't reference the data lake are completing successfully. As a workaround, I've been running SQL queries in Synapse pipelines and using the data lake as a sink for the results. In Power BI, I can then access the data through the lake connector. This issue has been ongoing for about 12 hours now, and Azure has categorized it as a warning event; the tracking ID is 2_10-HFZ.
3 Answers
Same here! Queries against our data lakes are failing as well. It's been super annoying trying to find a consistent solution.
Looks like this issue isn't isolated to just you. We’re seeing intermittent query timeouts across multiple regions, despite Synapse showing as 'healthy.' Serverless SQL pools rely on shared storage and metadata services, so when those are slow, it affects everyone. A good quick fix I’ve found is to run a `sys.dm_exec_requests` query to check for suspended pools and re-attach the external tables once the storage latency settles down. Have you tried connecting through Power BI pipelines? That's worked for some teams I know!
Yeah, we're also in the UK South region and facing SQL timeouts with Dynamics. It's a pain, especially when Microsoft claims everything's running smoothly. Glad to know I'm not alone in this!
It's frustrating, isn't it? You would think they would have better transparency when things go wrong.
I’m using Power BI dataflows too and running into the same issues with queries. Connecting through pipelines seems like a solid workaround for now.