Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

HSpeelman

TOM property not deployed to Semantic model (dataCoverageDefinition) - Hybrid table setup

Submitted by on ‎03-06-2024 07:51 AM

I'm trying to deploy a property dataCoverageDefinition in my semantic model's partition.

I need this for a hybrid model setup, where one partition is set to direct query, and the other one to Import.

 

According to the documentation, an additional property needs to be deployed to the directquery partition to make sure Power BI does not perform any unnecessary queries in direct query mode.

https://learn.microsoft.com/en-us/analysis-services/tom/table-partitions?view=asallproducts-allversi...

 

Compatibility has been set to 1604.

Property has been set into the DirectQuery partition.

Script runs succesfully, but the property cannot be found when re-opening the script of the datamodel.

When reviewing the performance analyzer, Power BI still performs unnecessary direct queries when the requested data is clearly data stored in the import partition.

Status: Investigating

Hi @HSpeelman ,

 

It seems like you’re doing everything correctly according to the documentation. The property should indeed provide a hint regarding the data that is covered by the partitionDataCoverageDefinition. This property is supported when the compatibility level of the database is at 1603 or above, which is the case in your situation (1604).

However, if the property is not found when re-opening the script of the data model, it might be due to some issues with the deployment process. You could try using the Deployment Wizard for deploying model solutions. It uses JSON output files generated from an SQL Server Analysis Services project as input files, which are easily modifiable to customize the deployment.

 

You may refer to Deploy model solutions by using the Deployment Wizard | Microsoft Learn

 

Best regards.
Community Support Team_Caitlyn

See more ideas labeled with:
2 Comments (2 New)
Comments
v-xiaoyan-msft
Community Support
Community Support
‎03-07-2024 01:20 AM
Status changed to: Investigating

Hi @HSpeelman ,

 

It seems like you’re doing everything correctly according to the documentation. The property should indeed provide a hint regarding the data that is covered by the partitionDataCoverageDefinition. This property is supported when the compatibility level of the database is at 1603 or above, which is the case in your situation (1604).

However, if the property is not found when re-opening the script of the data model, it might be due to some issues with the deployment process. You could try using the Deployment Wizard for deploying model solutions. It uses JSON output files generated from an SQL Server Analysis Services project as input files, which are easily modifiable to customize the deployment.

 

You may refer to Deploy model solutions by using the Deployment Wizard | Microsoft Learn

 

Best regards.
Community Support Team_Caitlyn

HSpeelman
Frequent Visitor
‎03-07-2024 11:56 PM

Hi v-xiaoyan-msft,

 

We are currently not using SSAS, but Power BI premium capacity. When opening the Deployment Wizard I see no option to connect to the premium workspace. We don't have an '.asdatabase' file which is needed for this tool. Do you have any other suggestions or tools that can deploy an xmla file to a power bi premium workspace?

 

Thanks in advance.

 

Henny

Idea Statuses