<?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 Power Query always references the SQL db in Power Query</title>
    <link>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4263832#M141017</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a power query setup wherein the SQL query is contained in one query, and the transformations are done in a couple of child queries which talk back to it. I have then put in Table.Buffer custom functions in at the end of the Parent query, and also at the start of the child query - despite this, every time I change the M code, it is referringback to the SQL db and takes a long time.&lt;/P&gt;&lt;P&gt;How do i stop it from doing this? I'd rather the SQL query needed a manual push to refresh, and the child queries would only refer to the parent as a static table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below, you can see there's the Custom1 function [ Table.Buffer(Source) ] but the PostgreSQL is running in the progress bar anyway.&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated!&lt;/P&gt;</description>
    <pubDate>Wed, 30 Oct 2024 11:55:11 GMT</pubDate>
    <dc:creator>Timmy_Puddles</dc:creator>
    <dc:date>2024-10-30T11:55:11Z</dc:date>
    <item>
      <title>Power Query always references the SQL db</title>
      <link>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4263832#M141017</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a power query setup wherein the SQL query is contained in one query, and the transformations are done in a couple of child queries which talk back to it. I have then put in Table.Buffer custom functions in at the end of the Parent query, and also at the start of the child query - despite this, every time I change the M code, it is referringback to the SQL db and takes a long time.&lt;/P&gt;&lt;P&gt;How do i stop it from doing this? I'd rather the SQL query needed a manual push to refresh, and the child queries would only refer to the parent as a static table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below, you can see there's the Custom1 function [ Table.Buffer(Source) ] but the PostgreSQL is running in the progress bar anyway.&lt;/P&gt;&lt;P&gt;&lt;img /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any help would be greatly appreciated!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 11:55:11 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4263832#M141017</guid>
      <dc:creator>Timmy_Puddles</dc:creator>
      <dc:date>2024-10-30T11:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: Power Query always references the SQL db</title>
      <link>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4263992#M141032</link>
      <description>&lt;P&gt;Table.Buffer will not prevent a reload of data from source.&amp;nbsp; It does prevent chunking/streaming, so it does the opposite of what you want because now Power Query no longer can fetch previews.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 13:59:03 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4263992#M141032</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2024-10-30T13:59:03Z</dc:date>
    </item>
    <item>
      <title>Re: Power Query always references the SQL db</title>
      <link>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4264067#M141038</link>
      <description>&lt;P&gt;Okay that's not what I expected, thanks for oyur reply. Is there a way for me to set this up the way I described - so that the SQL query doesn't get involved every single time?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 14:36:52 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4264067#M141038</guid>
      <dc:creator>Timmy_Puddles</dc:creator>
      <dc:date>2024-10-30T14:36:52Z</dc:date>
    </item>
    <item>
      <title>Re: Power Query always references the SQL db</title>
      <link>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4264235#M141045</link>
      <description>&lt;P&gt;In your development phase apply a filter that severely limits the amount of data to just what you need to develop. Then in production remove that filter.&amp;nbsp; You can do that with parameters, similar to how Incremental Refresh is designed.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 15:51:19 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Power-Query/Power-Query-always-references-the-SQL-db/m-p/4264235#M141045</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2024-10-30T15:51:19Z</dc:date>
    </item>
  </channel>
</rss>

