<?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 row_number over partition sql server - error and performance in PowerBi in DAX Commands and Tips</title>
    <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2622756#M76471</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;Having a view containing this command :&amp;nbsp;&lt;A href="https://stackoverflow.com/questions/72884591/row-number-over-partition-performance-from-powerbi" target="_blank" rel="noopener"&gt;row_number over partition&lt;/A&gt;&amp;nbsp; results in timeout when executing the view from PowerBi. Its working fine if executed in SSMS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I got to know from a coallegue that this is due to usage of this command which is not good for PowerBi and after a test changing the view with a table, the issue dissapears. How is possible that usable of this command in sql server view an have performance issues when executed from PowerBi?&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jul 2022 14:02:59 GMT</pubDate>
    <dc:creator>galbo1993</dc:creator>
    <dc:date>2022-07-06T14:02:59Z</dc:date>
    <item>
      <title>row_number over partition sql server - error and performance in PowerBi</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2622756#M76471</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;Having a view containing this command :&amp;nbsp;&lt;A href="https://stackoverflow.com/questions/72884591/row-number-over-partition-performance-from-powerbi" target="_blank" rel="noopener"&gt;row_number over partition&lt;/A&gt;&amp;nbsp; results in timeout when executing the view from PowerBi. Its working fine if executed in SSMS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I got to know from a coallegue that this is due to usage of this command which is not good for PowerBi and after a test changing the view with a table, the issue dissapears. How is possible that usable of this command in sql server view an have performance issues when executed from PowerBi?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2022 14:02:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2622756#M76471</guid>
      <dc:creator>galbo1993</dc:creator>
      <dc:date>2022-07-06T14:02:59Z</dc:date>
    </item>
    <item>
      <title>Re: row_number over partition sql server - error and performance in PowerBi</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2623087#M76499</link>
      <description>&lt;P&gt;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="355629" data-lia-user-login="galbo1993" class="lia-mention lia-mention-user"&gt;galbo1993&lt;/a&gt; , In can direct query it can impact the visuals display time.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In case of import mode, if can only slow download time and the visual display time&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2022 16:19:53 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2623087#M76499</guid>
      <dc:creator>amitchandak</dc:creator>
      <dc:date>2022-07-06T16:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: row_number over partition sql server - error and performance in PowerBi</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2623139#M76507</link>
      <description>&lt;P&gt;Thanks, I dont understand what do you mean, can you please describe more?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BTW, I found out its "Import"&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 07:31:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2623139#M76507</guid>
      <dc:creator>galbo1993</dc:creator>
      <dc:date>2022-07-07T07:31:35Z</dc:date>
    </item>
    <item>
      <title>Re: row_number over partition sql server - error and performance in PowerBi</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2635913#M77269</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="355629" data-lia-user-login="galbo1993" class="lia-mention lia-mention-user"&gt;galbo1993&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to your description, your connection mode is "import", first of all, for this method, you need to know that it will import the data into power bi desktop. It means the data will be loaded into power bi desktop from data source and will consume memory and disk space. Then upon load, all of the data defined by those queries will be imported into the Power BI cache. Upon building a visual within Power BI Desktop, the imported data will be queried.&amp;nbsp;Therefore, if your query is complex and involves a large amount of data, it may cause a slow query and thus timeout failure for power bi desktop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So maybe your command are too complex so that it causes timing out and failing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you want to get a clear picture of what's going wrong, I suggest you click “performance analyzer” , it can help you identify visuals that are impacting the performance of your reports, and identify the reason for the impact.&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;&lt;A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-bi%2Fcreate-reports%2Fdesktop-performance-analyzer&amp;amp;data=05%7C01%7Cv-mengzhu%40microsoft.com%7Cf930dcb73b80430731ec08da64b0d9db%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637933007988619487%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;amp;sdata=xyapiS%2BIwborZpi9axjRYrAMdx2Ws9iKkG4aEygERAA%3D&amp;amp;reserved=0" target="_blank"&gt;Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Microsoft Docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or you can use “Diagnostic options”, it can help you achieve a better understanding of what Power Query is doing at authoring and at refresh time in Power BI Desktop.&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-query%2Fquerydiagnostics&amp;amp;data=05%7C01%7Cv-mengzhu%40microsoft.com%7Cf930dcb73b80430731ec08da64b0d9db%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637933007988619487%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;amp;sdata=zD9Jil23AoYWooHFmY3QqjLTLRmVr3EjmivuyzVqgc8%3D&amp;amp;reserved=0" target="_blank"&gt;Query Diagnostics - Power Query | Microsoft Docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The above ways all can help you to check if it is a performance issues.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Community Support Team &lt;STRONG&gt;Selina&lt;/STRONG&gt;&lt;STRONG&gt; zhu&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If this post &lt;STRONG&gt;helps&lt;/STRONG&gt;, then please consider &lt;STRONG&gt;&lt;EM&gt;Accept it as the solution &lt;/EM&gt;&lt;/STRONG&gt;to help the other members find it more quickly&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2022 09:38:19 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2635913#M77269</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-07-13T09:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: row_number over partition sql server - error and performance in PowerBi</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2643105#M77693</link>
      <description>&lt;P&gt;Thankyou so much for nice response. But do you know anything specific for the mentioned command regarding more performance issues onPowerBi?&lt;/P&gt;</description>
      <pubDate>Sun, 17 Jul 2022 17:31:59 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2643105#M77693</guid>
      <dc:creator>galbo1993</dc:creator>
      <dc:date>2022-07-17T17:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: row_number over partition sql server - error and performance in PowerBi</title>
      <link>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2646253#M77859</link>
      <description>&lt;P&gt;Hi &lt;a href="javascript:void(0)" data-lia-user-mentions="" data-lia-user-uid="355629" data-lia-user-login="galbo1993" class="lia-mention lia-mention-user"&gt;galbo1993&lt;/a&gt;&amp;nbsp;，&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Generally speaking, I think most commands should be supported. What easily affects performance is the amount of data, and if you have very large data, a simple command may also cause slow queries.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Community Support Team&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Selina&lt;/STRONG&gt;&lt;STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;zhu&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;If this post&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;helps&lt;/STRONG&gt;, then please consider&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;&lt;EM&gt;Accept it as the solution&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/EM&gt;&lt;/STRONG&gt;to help the other members find it more quickly&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jul 2022 03:03:15 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/DAX-Commands-and-Tips/row-number-over-partition-sql-server-error-and-performance-in/m-p/2646253#M77859</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-07-19T03:03:15Z</dc:date>
    </item>
  </channel>
</rss>

