<?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: slow report - Splitting report in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/slow-report-Splitting-report/m-p/3245587#M42762</link>
    <description>&lt;P&gt;The number of pages is not really relevant as each page will only be rendered when the user looks at it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The number of visuals on a page does have an impact - so try to keep that down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The real impact is coming from your measure calculations.&amp;nbsp; Use Performance Analyzer and DAX Studio to identify the visuals that take the longest to render and then examine their queries to see which measures need to be optimized.&lt;/P&gt;</description>
    <pubDate>Sat, 20 May 2023 21:58:40 GMT</pubDate>
    <dc:creator>lbendlin</dc:creator>
    <dc:date>2023-05-20T21:58:40Z</dc:date>
    <item>
      <title>slow report - Splitting report</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/slow-report-Splitting-report/m-p/3241843#M42726</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i have stumbled accross an issue and i think i might need to split my report instead of having it all in one so it can run smoother, but not sure how.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i have about 7 pages in my report, all connected to a database. 6 direct queries, 1 excel connection. probably over 30 measures.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;what is the best way to split my report?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i think i should delete some pages and connections and save as a new report but i dont want to rush into something im going to regret.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;AI&lt;/P&gt;</description>
      <pubDate>Thu, 18 May 2023 08:51:52 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/slow-report-Splitting-report/m-p/3241843#M42726</guid>
      <dc:creator>AI14</dc:creator>
      <dc:date>2023-05-18T08:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: slow report - Splitting report</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/slow-report-Splitting-report/m-p/3245587#M42762</link>
      <description>&lt;P&gt;The number of pages is not really relevant as each page will only be rendered when the user looks at it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The number of visuals on a page does have an impact - so try to keep that down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The real impact is coming from your measure calculations.&amp;nbsp; Use Performance Analyzer and DAX Studio to identify the visuals that take the longest to render and then examine their queries to see which measures need to be optimized.&lt;/P&gt;</description>
      <pubDate>Sat, 20 May 2023 21:58:40 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/slow-report-Splitting-report/m-p/3245587#M42762</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2023-05-20T21:58:40Z</dc:date>
    </item>
  </channel>
</rss>

