Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Planning to implement Medallion with Fabric warehouse as the good layer. What's limit of concurrent users trying to access the Fabric warehouse tables? Got F64 capacity in place.
Solved! Go to Solution.
Hi @animeshdada there are currently no published numbers from Microsoft in terms of concurrent connections. But the SQL engine that backends the Fabric Warehouse service is based on the Synapse Serverless engine, that engine could support up to 1,000 concurrent active sessions with users running "lightweight" queries.
In the world of Fabric, it's going to depend on how much capacity each user request is going to use. I would say that capacity would run out and bottelneck way before any SQL concurrency limits would be hit.
In conclusion the more "lightweight" each user workload and few capacity units used, the more concurrent workloads can be run. Once users are running more CU intensive workloads, if the CU usage bursts significantly past the F64 capacity limits, then throttling will occur.
Hi @animeshdada there are currently no published numbers from Microsoft in terms of concurrent connections. But the SQL engine that backends the Fabric Warehouse service is based on the Synapse Serverless engine, that engine could support up to 1,000 concurrent active sessions with users running "lightweight" queries.
In the world of Fabric, it's going to depend on how much capacity each user request is going to use. I would say that capacity would run out and bottelneck way before any SQL concurrency limits would be hit.
In conclusion the more "lightweight" each user workload and few capacity units used, the more concurrent workloads can be run. Once users are running more CU intensive workloads, if the CU usage bursts significantly past the F64 capacity limits, then throttling will occur.