Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Is there a way to disable a table from loading using XMLA endpoints ( either in SQL Server Management Studio Analysis Services or Tabular Editor 2.0) ?
Background:
My issue is I have a giant static historical data table I append a current data table to.
I have to load the giant table using XMLA endpoints as it is too large to publish to Power BI Serviceand the regular refresh in Power BI Service times out. So I parameterize the table to use a dev data source which I can switch to prod once published, and also use incremental refresh to create partitions I can load using XMLA endpoints in SQL Server Management Studio (SSMS). I would like to disable the load of the tables used to create the append, but I cannot do so before publishing to Power BI Service as the tables are innaccessible via XMLA endpoints in SSMS as far as I can tell, and I can't load data to them.
Solved! Go to Solution.
@oneraj4u While I may be wrong, I don't believe so. I believe that setting is actually metadata associated with a query, and the XMLA endpoint doesn't give you access to that.
@oneraj4u Not that I am aware of. The Power BI Rest API isn't going to do it. And editing the data model in the Service doesn't give you access to the queries either. Maybe something tricky with a dataflow? Probably not going to happen either. Perhaps it would be possible to cut your original history table down to just a year or two, publish to the Service and then activate incremental refresh on the table, something like that?
@oneraj4u While I may be wrong, I don't believe so. I believe that setting is actually metadata associated with a query, and the XMLA endpoint doesn't give you access to that.
Thank you Greg
Are you aware of any way to disable load of a table once the report is in Power BI Service aside from XMLA endpoints?
@oneraj4u Not that I am aware of. The Power BI Rest API isn't going to do it. And editing the data model in the Service doesn't give you access to the queries either. Maybe something tricky with a dataflow? Probably not going to happen either. Perhaps it would be possible to cut your original history table down to just a year or two, publish to the Service and then activate incremental refresh on the table, something like that?
Thank you very much for your insights. 😊
End note for other users looking at this:
While I can do various methhods to load the data, and I do use dataflows with parametrized queries for the initial publishing - it appears that I will be unable to disable the load of a table in Power Query once published as of 9-19-2023
Check out the September 2024 Power BI update to learn about new features.
Learn from experts, get hands-on experience, and win awesome prizes.
User | Count |
---|---|
41 | |
4 | |
4 | |
3 | |
3 |