Forum Discussion
Append Query only refresh one table
In Power Query in the first steps, by clicking on the gear icon. If it's import, just by deselecting the option "Include in report refresh" should do it. On Power Query it queries frequently the data as it gets data previews in order for you to apply steps, but once published, that Table will never get updated.
Did you set the connection to TableA as Import or Direct Query?
Pretty sure I used Import, is there a way to double check?
In Power Query in the first steps, by clicking on the gear icon. If it's import, just by deselecting the option "Include in report refresh" should do it. On Power Query it queries frequently the data as it gets data previews in order for you to apply steps, but once published, that Table will never get updated.
Thank you.
So I could turn the SQL Server off when I am not editing the report and users are accessing the report and turn it back on when I need to edit the report. Is that correct?
The Append query would still update with the data from TableB (data not from the SQL DB) so the users would see the latest data from the scheduled refresh plus the historical data?
As to my knowledge, SQL Server needs to be turned on just for the connection to stay alive. Since you already indicated that you don't want that table to be refreshed, Power BI will not query against it once the refresh process comes up. If you won't ever need again to do anything with TableA then I would say that yes you can turn it off.
Hi ray_aramburo ,
Jumping in as i have an exact same case 🙂
Using power query on excel, i have two tables, one of which is historical data (CUT_Editions) and the second is Ongoin data (ONGOING). me data is coming for SAP HANA server.
i created an Append table that comprises the two queries, but the refresh time of the append seems to also refresh the CUT_Editions table. when refreshing the Apeend table, i want only to refresh the ONGOING table. is that possible?
thanks,
Dudi
Anonymous same case, you need to follow the same process for the historical data. If it was a huge table on Power Query in the desktop will surely take its time anyways as it loads the preview, but when published and refresh runs automatically should be fast(er).