Forum Discussion
Helper VPower BI Premium with Composite Models
I had a user recently publish a composite model into our Premium Workspace. it was AAS (usually we use live connection but since it is composite its direct connection) also imported a small Azure SQL Table.
Our Premium Capacity hit an all time high over 500%- I am assuming the DAX is causing this issue but if the DAX is applying to both the AAS-Direct query and Azure SQL import--- shouldnt the Premium not be effected instead the load be on AAS?
hello powerbihelp87
When using a composite model that combines DirectQuery and Import data sources, Power BI Premium handles the integration of these data sources. While DirectQuery queries are executed on the source system (e.g., AAS), Power BI must process and combine the results with data from imported tables locally. This integration, including any DAX calculations or relationships between the sources, occurs within the Power BI Premium Capacity and contributes to its resource usage
While AAS handles its own query execution for DirectQuery models, Power BI’s composite model architecture requires additional processing within Power BI itself:
• The results from AAS queries are fetched into Power BI for further processing (e.g., combining with imported data). This processing happens within the Premium Capacity and contributes to its load.
• Any inefficiencies in DAX measures or relationships in the Power BI model will amplify resource usage on the Premium Capacity rather than offloading entirely to AASHope this clarifies why high capacity usage.
if this is helpful please accept the answer
2 Replies
- nilendraFabric
Super User
hello powerbihelp87
When using a composite model that combines DirectQuery and Import data sources, Power BI Premium handles the integration of these data sources. While DirectQuery queries are executed on the source system (e.g., AAS), Power BI must process and combine the results with data from imported tables locally. This integration, including any DAX calculations or relationships between the sources, occurs within the Power BI Premium Capacity and contributes to its resource usage
While AAS handles its own query execution for DirectQuery models, Power BI’s composite model architecture requires additional processing within Power BI itself:
• The results from AAS queries are fetched into Power BI for further processing (e.g., combining with imported data). This processing happens within the Premium Capacity and contributes to its load.
• Any inefficiencies in DAX measures or relationships in the Power BI model will amplify resource usage on the Premium Capacity rather than offloading entirely to AASHope this clarifies why high capacity usage.
if this is helpful please accept the answer
powerbihelp87thank you! so in a sense in runs a Dax query in AAS and if it has an imported table it also processes in Premium since its utilizing both sources---hence the high premium spike