<?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 Best practices for Direct Query Scaling in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/Best-practices-for-Direct-Query-Scaling/m-p/3349479#M43607</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have developed some Direct Query Power BI reports which connect to our AWS SQL Server database and refresh every 5 minutes. Leadership loved the POC and wanted to scale to multiple locations, but now we are finding it creates to heavy a load on the server so have paused the project.&lt;/P&gt;&lt;P&gt;The query is not terribly complex. It has a few subqueries, many joins on 10 tables, some of which are &amp;gt; 1 million rows and outputs only ~5k rows.&lt;/P&gt;&lt;P&gt;What are some potential solutions and best practices given this situation? Here are some things I am considering&lt;BR /&gt;-Use staging tables with SQL Server Agent job&lt;BR /&gt;-Send data to our datalake in Snowflake instead of querying the production database (not sure how to productionalize this, I made a Python demo which sends the data to Snowflake, so in theory this could work). Maybe use third party service for this?&lt;BR /&gt;-Enable CDC in database (again not sure which product(s) we would use after this is enabled)&lt;BR /&gt;-Use Azure Synapse Analytics since it is purpose built to handle Direct Query at scale (what would be the best practice to get the data in Azure?)&lt;/P&gt;&lt;P&gt;Any help, ideas, suggestions are greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks for your time,&lt;BR /&gt;Joe&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jul 2023 19:27:29 GMT</pubDate>
    <dc:creator>jgmendez</dc:creator>
    <dc:date>2023-07-25T19:27:29Z</dc:date>
    <item>
      <title>Best practices for Direct Query Scaling</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Best-practices-for-Direct-Query-Scaling/m-p/3349479#M43607</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have developed some Direct Query Power BI reports which connect to our AWS SQL Server database and refresh every 5 minutes. Leadership loved the POC and wanted to scale to multiple locations, but now we are finding it creates to heavy a load on the server so have paused the project.&lt;/P&gt;&lt;P&gt;The query is not terribly complex. It has a few subqueries, many joins on 10 tables, some of which are &amp;gt; 1 million rows and outputs only ~5k rows.&lt;/P&gt;&lt;P&gt;What are some potential solutions and best practices given this situation? Here are some things I am considering&lt;BR /&gt;-Use staging tables with SQL Server Agent job&lt;BR /&gt;-Send data to our datalake in Snowflake instead of querying the production database (not sure how to productionalize this, I made a Python demo which sends the data to Snowflake, so in theory this could work). Maybe use third party service for this?&lt;BR /&gt;-Enable CDC in database (again not sure which product(s) we would use after this is enabled)&lt;BR /&gt;-Use Azure Synapse Analytics since it is purpose built to handle Direct Query at scale (what would be the best practice to get the data in Azure?)&lt;/P&gt;&lt;P&gt;Any help, ideas, suggestions are greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks for your time,&lt;BR /&gt;Joe&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jul 2023 19:27:29 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Best-practices-for-Direct-Query-Scaling/m-p/3349479#M43607</guid>
      <dc:creator>jgmendez</dc:creator>
      <dc:date>2023-07-25T19:27:29Z</dc:date>
    </item>
  </channel>
</rss>

