Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Optimal configuration settings for high concurrency in SSAS

Optimal configuration settings for high concurrency in SSAS

Summary

When multiple users access SQL Server Analysis Services concurrently, an expensive query that needs to scan large number of partitions can monopolize the system and block other users. To avoid this problem and achieve high concurrency, it is recommended to set CoordinatorQueryBalancingFactor to 1 and CoordinatorQueryBoostPriorityLevel to 0.

↑ Back to the top

More Information

For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:

Rule softwareRule titleRule descriptionProduct versions against which the rule is evaluated 
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)




Server not configured for optimal concurrent query throughput




The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to check the current value for CoordinatorQueryBalancingFactor and CoordinatorQueryBoostPriorityLevel in msmdsrv.ini. If you run the BPA tool and encounter a warning message "Server not configured for optimal concurrent query throughput", you should check the current CoordinatorQueryBalancingFactor and CoordinatorQueryBoostPriorityLevel value in msmdsrv.ini and set them accordingly as recommended by BPA.

The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2.		SQL Server 2008
SQL Server 2008 R2






SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)
Server not configured for optimal concurrent query throughput
The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to check the current value for CoordinatorQueryBalancingFactor and CoordinatorQueryBoostPriorityLevel in msmdsrv.ini. If you run the BPA tool and encounter a warning message "Server not configured for optimal concurrent query throughput", you should check the current CoordinatorQueryBalancingFactor and CoordinatorQueryBoostPriorityLevel value in msmdsrv.ini and set them accordingly as recommended by BPA.SQL Server 2012

 




↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 2135031
Revision : 1
Created on : 1/7/2017
Published on : 4/2/2012
Exists online : False
Views : 405