<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Concurrent User Limitations in Warehouse in Data Warehouse</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Warehouse/Concurrent-User-Limitations-in-Warehouse/m-p/4284154#M2089</link>
    <description>&lt;P&gt;Hi&amp;nbsp;Anonymous&lt;/LI-USER&gt;&amp;nbsp;there are currently no published numbers from Microsoft in terms of concurrent connections.&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the world of Fabric, it's going to depend on how much capacity each user request is going to use.&amp;nbsp; I would say that capacity would run out and bottelneck way before any SQL concurrency limits would be hit.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In conclusion the more "lightweight" each user workload and few capacity units used, the more concurrent workloads can be run.&amp;nbsp; Once users are running more CU intensive workloads, if the CU usage bursts significantly past the F64 capacity limits, then throttling will occur.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Nov 2024 14:22:11 GMT</pubDate>
    <dc:creator>AndyDDC</dc:creator>
    <dc:date>2024-11-14T14:22:11Z</dc:date>
    <item>
      <title>Concurrent User Limitations in Warehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Warehouse/Concurrent-User-Limitations-in-Warehouse/m-p/4284103#M2088</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Nov 2024 13:52:03 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Warehouse/Concurrent-User-Limitations-in-Warehouse/m-p/4284103#M2088</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2024-11-14T13:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: Concurrent User Limitations in Warehouse</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Warehouse/Concurrent-User-Limitations-in-Warehouse/m-p/4284154#M2089</link>
      <description>&lt;P&gt;Hi&amp;nbsp;Anonymous&lt;/LI-USER&gt;&amp;nbsp;there are currently no published numbers from Microsoft in terms of concurrent connections.&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the world of Fabric, it's going to depend on how much capacity each user request is going to use.&amp;nbsp; I would say that capacity would run out and bottelneck way before any SQL concurrency limits would be hit.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In conclusion the more "lightweight" each user workload and few capacity units used, the more concurrent workloads can be run.&amp;nbsp; Once users are running more CU intensive workloads, if the CU usage bursts significantly past the F64 capacity limits, then throttling will occur.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Nov 2024 14:22:11 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Warehouse/Concurrent-User-Limitations-in-Warehouse/m-p/4284154#M2089</guid>
      <dc:creator>AndyDDC</dc:creator>
      <dc:date>2024-11-14T14:22:11Z</dc:date>
    </item>
  </channel>
</rss>

