Skip to main content

New cache refresh settings available in Power BI Premium

Earlier this year, we announced the additional Analysis Services server properties that are now supported in Power BI Premium and Power BI Embedded. With this capability, Power BI administrators can modify XMLA-based Analysis Services server properties to optimize, govern, and alter query behavior in their workspaces. Today, we are adding another familiar server property that will be supported in Power BI! We are happy to announce that ClientCacheRefreshPolicy is now a configurable property for your Power BI Premium workspaces. Admins can override scheduled cache refresh settings for an entire workspace, improving the performance of their semantic models.

The default behavior in the Power BI service is to automatically cache dashboard, tile, and report queries upon refresh to provide an optimal report viewing experience. For enterprise semantic model deployments, where hundreds of reports and artifacts are built from a single Power BI dataset, automatic caches may cause performance issues. For example, queuing a high number of queries after every refresh, results in longer refresh times as well as unnecessary loads on the dataset. With the ClientCacheRefreshPolicy property, admins can disable the automatic cache refresh setting to optimize the behavior of their Power BI datasets.

Note that datasets with refresh operations performed by the XMLA endpoint or the enhanced refresh Power BI REST API, do not automatically refresh tile caches. The ClientCacheRefreshPolicy only applies to datasets with refresh operations performed by the Power BI service (e.g., scheduled or on-demand refreshes). Check out Server properties in Analysis Services for more details on ClientCacheRefreshPolicy and other server properties available for Power BI Premium.

 

How do I enable or disable ClientCacheRefreshPolicy for my workspace?

You can enable XMLA-based Analysis Services server properties in your workspace by turning on the toggle to Observe XMLA-based workspace settings. To enable navigate to datasets workload in the Capacity Settings page under Admin Portal.

How do I modify a ClientCacheRefreshPolicy for a workspace?

  1. Follow these steps to get your workspace connection URL
  2. Open SQL Server Management Studio (SSMS)
  3. Connect to your Premium workspace in SSMS
  4. In Object Explorer, right click on the Premium workspace and select Properties 
                           
  5. In the Analysis Services Properties panel select General                                                       
  6. Check the Show Advanced (All) Properties box

  7. Modify the Value column. The default value for this property is -1, which allows all background cache refreshes for the dataset. To discourage all background cache refreshes, specify zero (0)
  8. Select OK
Labels:

Comments

Post a Comment

Hi User,
Thanks for visiting My Blog and please provide your valuable feedback and subscribe for more updates. Please don't post any spam content or comments.
Thank You

Popular posts from this blog

SSRS INTERVIEW QUESTIONS

Q: What is SSRS? Ø   SSRS or SQL Server Reporting Service is a server-based report generation software systems from Microsoft and is part of Microsoft BI. Ø   It is used for preparing and delivering interactive and variety of reports. Ø   It is administered through an web based interface. Ø   Reporting services utilizes a web service interface for supporting and developing of customized reporting applications. Ø   SSRS lets you create very rich reports (Tabular/Graphical/Interactive) from various datasources with rich data visualization (Charts, Maps, sparklines) Ø   SSRS allows are reports to be exported in various formats (Excel, PDF, word etc) Q: Explain SSRS Architecture? Reporting services architecture comprises of integrated components. It is a multi-tiered, included with application, server and data layers. This architecture is scalable and modular. A single installation can be used across multiple computers. It includes the fo...
3 comments
Read more

Exception deserializing the package "The process cannot access the file because it is being used by another process."

TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got...
58 comments
Read more

Failed to execute the package or element. Build errors were encountered

Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package
31 comments
Read more