<?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 Understanding Performance dashboard vs. capacity metric dashboard in SQL database</title>
    <link>https://community.fabric.microsoft.com/t5/SQL-database/Understanding-Performance-dashboard-vs-capacity-metric-dashboard/m-p/4585887#M201</link>
    <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;since the 1st of Feb 2025 the SQL database compute and storage is being charged to the Fabric capacity. This let to a lot of throttling in our capacity. We were at a F16 capacity, but upgraded to F32 to prevent the throttling.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I was wondering how the SQL database was operating so I checked the Performance Dashboard (Fabric SQL database) and there I see that we are not even using 0.3 CPU, with a status of normal.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While the capacity metrics show that we are exceeding our SKU. How is it possible?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards,&lt;BR /&gt;Mark&lt;/P&gt;</description>
    <pubDate>Wed, 26 Feb 2025 09:53:29 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2025-02-26T09:53:29Z</dc:date>
    <item>
      <title>Understanding Performance dashboard vs. capacity metric dashboard</title>
      <link>https://community.fabric.microsoft.com/t5/SQL-database/Understanding-Performance-dashboard-vs-capacity-metric-dashboard/m-p/4585887#M201</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;since the 1st of Feb 2025 the SQL database compute and storage is being charged to the Fabric capacity. This let to a lot of throttling in our capacity. We were at a F16 capacity, but upgraded to F32 to prevent the throttling.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I was wondering how the SQL database was operating so I checked the Performance Dashboard (Fabric SQL database) and there I see that we are not even using 0.3 CPU, with a status of normal.&amp;nbsp; &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While the capacity metrics show that we are exceeding our SKU. How is it possible?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards,&lt;BR /&gt;Mark&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 09:53:29 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/SQL-database/Understanding-Performance-dashboard-vs-capacity-metric-dashboard/m-p/4585887#M201</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-02-26T09:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding Performance dashboard vs. capacity metric dashboard</title>
      <link>https://community.fabric.microsoft.com/t5/SQL-database/Understanding-Performance-dashboard-vs-capacity-metric-dashboard/m-p/4586798#M202</link>
      <description>&lt;P&gt;Hello&amp;nbsp;Anonymous&lt;/LI-USER&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;could you please confirm if Sql database is the only workload utilising the F16?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SQL Database uses only a portion of Fabric’s total capacity (1 Fabric CU = 0.383 SQL vCores). A Fabric F64 SKU (64 CUs) provides ~24.5 SQL vCores, leaving ~39.5 CUs for other workloads like Power BI, Data Engineering, or KQL databases&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Throttling occurs at the capacity level, not per workload. Even with low SQL CPU usage, concurrent workloads (e.g., Spark jobs, Power BI reports) can collectively exceed capacity limits&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Most SQL operations are classified as interactive in Fabric and smoothed over 5-minute windows. Short, frequent queries or system tasks (e.g., metadata updates) can spike CU usage without significantly impacting SQL CPU&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;this is mainly for guidance.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 22:41:47 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/SQL-database/Understanding-Performance-dashboard-vs-capacity-metric-dashboard/m-p/4586798#M202</guid>
      <dc:creator>nilendraFabric</dc:creator>
      <dc:date>2025-02-26T22:41:47Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding Performance dashboard vs. capacity metric dashboard</title>
      <link>https://community.fabric.microsoft.com/t5/SQL-database/Understanding-Performance-dashboard-vs-capacity-metric-dashboard/m-p/4587480#M203</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="913195" data-lia-user-login="nilendraFabric" class="lia-mention lia-mention-user"&gt;nilendraFabric&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the screenshots are from the F32 SKU. However the question remains the same.&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are other processes running on the capacity. However between 3 am and 4 am, SQL is the only activity classified as interactive. The capacity is processing around &amp;lt;20% on background activities at that time.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Feb 2025 08:32:31 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/SQL-database/Understanding-Performance-dashboard-vs-capacity-metric-dashboard/m-p/4587480#M203</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2025-02-27T08:32:31Z</dc:date>
    </item>
  </channel>
</rss>

