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

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

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
Read more

Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks)

-
TITLE: Microsoft SQL Server Management Studio ------------------------------ Restore of database 'DataBase_Name' failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: Exclusive access could not be obtained because the database is in use. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=12.0.2000.8+((SQL14_RTM).140220-1752)&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Procedure 1: 1. Right click Databases 2. Restore Database... 3. [General] Source from Device, select the bak file 4. [General] Change the Destination database name to a new name 5. [Files] Change mdf and ldf Restore As paths to a different, new path 6. [Options] (unnecessary on the other computer) Check Overwrite the existing database (WITH_REPLACE) 7. [Options] (unnecessary on the other computer)
Read more

Get List of logins on SQL Server instance

-
-- List of logins select sp . name as login ,        sp . type_desc as login_type ,        sp . type ,        sp . create_date ,        sp . modify_date ,        case                when sp . is_disabled = 1 then 'Disabled'             else 'Enabled'           end as status from sys . server_principals sp left join sys . sql_logins sl on sp . principal_id = sl . principal_id order by sp . name ;   --Get the list of all Login Accounts in a SQL Server SELECT name AS Login_Name , type_desc AS Account_Type FROM sys . server_principals WHERE TYPE IN ( 'U' , 'S' , 'G' ) and name not like '%##%' ORDER BY name , type_desc   --Get the list of all SQL Login Accounts only SELECT name , type_desc AS Account_Type FROM sys . server_principals WHERE TYPE = 'S' and name not like '%##%'   --Get the list of all Windows Login Accounts only
Read more