Configuration of MSSQLAMDXTest

This test monitors MDX query execution plans and reports the count of cell-by-cell, bulk-mode, and subcube evaluation nodes built by these plans. This way, administrators can figure out if there are any queries that use the expensive cell-by-cell mode, and may hence require fine-tuning. The test also tracks the hits and misses experienced by the caches of the cell-by-cell and bulk-mode evaluation nodes, and alerts administrators to poor cache usage. This way, by monitoring factors that may impact MDX query performance, this test provides administrators with useful pointers for improving query performance.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, the IP address of the host for which the test is to be configured has to be specified.

• Specify the port at which the specified HOST listens to in the PORT text box.

• The name of a specific SQL Analysis Services Server instance to be monitored. The default value of this parameter is default. However, if the Microsoft SQL Server hosting SSAS uses named instances, then do the following:

  • Configure the Instance parameter with the name of the SQL Server instance that hosts SSAS.
  • Do not change the default value of the Port parameter.

• Specify the SSAS version being monitored. By default, 11 is displayed here, indicating that version 11 of SSAS is monitored by default.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.