Five new Power BI Premium Capacity settings are available in the portal , preloaded with default values. Admin can review and override the defaults with their preference to better protect their capacity from running into issues and avoid problems before they arise. With the release of these new settings, Power BI admins now have the ability to set limits on “Max Offline Dataset Size” with the allowable range from 0.1 to 10 GB and/or set limits on queries to prevent noisy reports from impacting others using the capacity and create a more predictable and performant capacity.
New capacity settings in the admin portal
As an admin, you can find these new settings on the Admin portal> Capacity settings page , expand the “Workload” chevron on the management tab of the capacity.
The table below lists out the detailed description of the settings and real- world scenario explaining the benefits of the settings.
|Max Offline Dataset Size (GB)||Maximum size of the offline dataset in memory. This is the compressed size on disk. Default value is set by SKU and the allowable range is from 0.1 – 10 GB||When users are experiencing slowness due to a large dataset taking up memory resources , admins would very often end up in the similar cycle of first identifying the culprit datasets, contacting the owner or migrating to a different capacity. With this new setting, admins can now configure the dataset size and prevent report creators from publishing a large dataset that could potentially take down the capacity and secondly save the admin from the painful cycle of identifying and mitigating.|
|Query Memory Limit (%)||Applies only to DAX measures and queries. Specified in % and limits how much memory can be used by temporary results during a query.||Some queries/calculations can result in intermediate results that use a lot of memory on the capacity. This can cause other queries to execute very slowly, cause eviction of other datasets from the capacity, and lead to out of memory errors for other users of the capacity. Without this setting, capacity administrators would find it challenging to identify which report/query is causing the problem, so that they could work with the report author to improve the performance. With this new setting, admins can better control impact of bad or expensive report on others using the capacity.|
|Query Timeout (seconds)||An integer that defines the timeout, in seconds, for queries. The default is 3600 seconds (or 60 minutes). Note that Power BI reports will already override this default with a much smaller timeout for each of its queries to the capacity. Typically, it is approximately 3 minutes.||When users are experiencing spinning on the report primarily due to another expensive report, admins would sometimes have to move the workspace to a different capacity. With the new settings, admins can better control expensive queries so that they have less impact on other users of the capacity.|
|Max Intermediate Row Set Count
|The max number of intermediate rows returned by DirectQuery. Default value is set to 1000000 and allowable range is between 100000 and 2147483647||When a query to a DirectQuery dataset results in a very large result from the source database, it can cause a spike in memory as well as a lot of expensive processing of data. This can lead to other users and reports running low on resources. This setting allows the capacity administrator to adjust how many rows can be fetched by an individual query to the data source in a dataset.|
|Max Result Row Set Count||Defines the maximum number of rows returned in a DAX query. Default value is set to -1(no limit) and allowable range is between 100000 and 2147483647||Sometimes, a user can execute an expensive DAX query that returns a very large number of rows. This can cause a lot of resource usage and affect other users and reports executing on the capacity. This setting allows the capacity administrator to limit how many rows should be returned for any individual DAX query.|