<?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 Lakehouse SQL endpoint performance tuning in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3580390#M326</link>
    <description>&lt;P&gt;Hi - I'm curious to know if there is any way to see an "explain plan" or otherwise determine why a SQL query against a Lakehouse is taking a long time, and what could be done to help it. In my case I tried a sample query that queried a table with about 1 billion rows by it's primary key column, sorting the keys in ascending order. I realize sorting 1 billion values should take "a long time" - but I'm unsure that 11 minutes is expected / acceptable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note: yes this is an extreme and unrealistic case, in my case this was a proxy query that should have similar costs to the query the user actually wanted to run (but couldn't due to me not having the needed column)...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Long and short - what tools are available to understand the performance and potentially help it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
    <pubDate>Tue, 12 Dec 2023 18:16:11 GMT</pubDate>
    <dc:creator>Scott_Powell</dc:creator>
    <dc:date>2023-12-12T18:16:11Z</dc:date>
    <item>
      <title>Lakehouse SQL endpoint performance tuning</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3580390#M326</link>
      <description>&lt;P&gt;Hi - I'm curious to know if there is any way to see an "explain plan" or otherwise determine why a SQL query against a Lakehouse is taking a long time, and what could be done to help it. In my case I tried a sample query that queried a table with about 1 billion rows by it's primary key column, sorting the keys in ascending order. I realize sorting 1 billion values should take "a long time" - but I'm unsure that 11 minutes is expected / acceptable.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note: yes this is an extreme and unrealistic case, in my case this was a proxy query that should have similar costs to the query the user actually wanted to run (but couldn't due to me not having the needed column)...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Long and short - what tools are available to understand the performance and potentially help it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
      <pubDate>Tue, 12 Dec 2023 18:16:11 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3580390#M326</guid>
      <dc:creator>Scott_Powell</dc:creator>
      <dc:date>2023-12-12T18:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: Lakehouse SQL endpoint performance tuning</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3582339#M327</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/535913"&gt;@Scott_Powell&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for using Microsoft Fabric Community.&lt;/P&gt;
&lt;P&gt;Apologies for the issue you are facing here.&lt;/P&gt;
&lt;P data-sourcepos="1:1-1:161"&gt;&lt;SPAN&gt;Microsoft Fabric Data Warehouse currently &lt;/SPAN&gt;doesn't offer native "explain plan" functionality&lt;SPAN&gt; like SHOWPLAN_XML or EXPLAIN for SQL queries&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN&gt;and there are plans to expose the query plan in a "Query Insights" view.&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;However,&lt;/SPAN&gt;&lt;SPAN&gt; there are still ways to understand the performance of your query and potentially improve it:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-sourcepos="1:1-1:161"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-sourcepos="3:1-3:39"&gt;&lt;STRONG&gt;1. Data Preview and Query Insights:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-sourcepos="5:1-5:112"&gt;
&lt;LI data-sourcepos="5:1-5:112"&gt;&lt;STRONG&gt;Data Preview:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;This feature provides basic statistics about the queried table,&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;including the number of rows,&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;distinct values in each column,&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;and data types.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;This can help identify potential issues like missing indexes or skewed data distributions.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI data-sourcepos="6:1-6:26"&gt;&lt;STRONG&gt;Query Insights:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;This feature is still in development but is planned to offer insights into query performance,&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;including the estimated time and cost.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;While not a full explain plan,&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;it can provide valuable hints about the chosen execution strategy and potential bottlenecks.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;You can refer to this &lt;A href="https://learn.microsoft.com/en-us/fabric/data-warehouse/query-insights" target="_blank" rel="noopener"&gt;link&lt;/A&gt; for more information.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-sourcepos="8:1-8:30"&gt;&lt;STRONG&gt;2. Monitoring and Metrics:&lt;/STRONG&gt;&lt;/P&gt;
&lt;UL data-sourcepos="10:1-12:18"&gt;
&lt;LI data-sourcepos="10:1-10:192"&gt;&lt;STRONG&gt;Resource Utilization:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;Monitor CPU,&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;memory,&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;and disk utilization during query execution.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;High utilization in any of these areas could indicate a resource bottleneck impacting performance.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI data-sourcepos="11:1-11:210"&gt;&lt;STRONG&gt;Query Duration:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;Track the actual execution time of the query.&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;Compare it to the estimated time in Query Insights or the expected time for similar queries on your system to identify significant deviations.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;SPAN&gt;Appreciate if you could share the feedback on our&amp;nbsp;&lt;A href="http://appreciate%20if%20you%20could%20share%20the%20feedback%20on%20our%20feedback%20channel.%20which%20would%20be%20open%20for%20the%20user%20community%20to%20upvote%20&amp;amp;%20comment%20on.%20this%20allows%20our%20product%20teams%20to%20effectively%20prioritize%20your%20request%20against%20our%20existing%20feature%20backlog%20and%20gives%20insight%20into%20the%20potential%20impact%20of%20implementing%20the%20suggested%20feature.%20hope%20this%20helps.%20please%20let%20me%20know%20if%20you%20have%20any%20further%20queries./" target="_blank" rel="noopener nofollow noreferrer"&gt;feedback channel&lt;/A&gt;. Which would be open for the user community to upvote &amp;amp; comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Please let me know if you have any further queries.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Dec 2023 16:32:22 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3582339#M327</guid>
      <dc:creator>v-cboorla-msft</dc:creator>
      <dc:date>2023-12-13T16:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: Lakehouse SQL endpoint performance tuning</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3588845#M328</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/535913"&gt;@Scott_Powell&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.&lt;BR /&gt;In case if you have any resolution please do share that same with the community as it can be helpful to others.&lt;BR /&gt;Otherwise, will respond back with the more details and we will try to help.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Dec 2023 12:21:37 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3588845#M328</guid>
      <dc:creator>v-cboorla-msft</dc:creator>
      <dc:date>2023-12-18T12:21:37Z</dc:date>
    </item>
    <item>
      <title>Re: Lakehouse SQL endpoint performance tuning</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3594599#M329</link>
      <description>&lt;P&gt;hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/608020"&gt;@v-cboorla-msft&lt;/a&gt;&amp;nbsp;in my case I was specifically talking about a Lakehouse not a Warehouse (using the SQL endpoint). I'll try a similar test on a Warehouse to see if that makes a difference. Overall I'm just really trying to judge the performance to see if it's reasonable or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;</description>
      <pubDate>Wed, 20 Dec 2023 17:49:53 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3594599#M329</guid>
      <dc:creator>Scott_Powell</dc:creator>
      <dc:date>2023-12-20T17:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: Lakehouse SQL endpoint performance tuning</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3617744#M330</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/535913"&gt;@Scott_Powell&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Following up to see on the last response and was just checking back to see if you have a resolution yet.&lt;BR /&gt;In case if you have any resolution please do share that same with the community as it can be helpful to others.&lt;BR /&gt;Otherwise, will respond back with the more details and we will try to help.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jan 2024 11:40:50 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Lakehouse-SQL-endpoint-performance-tuning/m-p/3617744#M330</guid>
      <dc:creator>v-cboorla-msft</dc:creator>
      <dc:date>2024-01-05T11:40:50Z</dc:date>
    </item>
  </channel>
</rss>

