Overview of Intelligence Server Statistics

Intelligence Server can record a wide variety of statistics relating to user activity, data warehouse activity, report SQL, and system performance. These statistics are logged in the statistics database (see The Statistics Database).

The statistics that are logged for each project are set in the Project Configuration Editor, in the Statistics: General subcategory. The options are as follows:

Statistics logging option	Statistics logged
All basic statistics	User session and project session analysis. This option must be selected for any statistics to be logged.
Report job steps	Detailed statistics on the processing of each report.
Document job steps	Detailed statistics on the processing of each document.
Report job SQL	The generated SQL for all report jobs. This option can create a very large statistics table. Select this option when you need the job SQL data.
Report job tables/columns accessed	Data warehouse tables and columns accessed by each report.
Mobile Clients	Detailed statistics on reports and documents that are executed on a mobile device.
Mobile Clients Manipulations This option is available if Mobile Clients is selected	Detailed statistics on actions performed by end users on a mobile client.
Only purge statistics logged from the current Intelligence Server.	Purge statistics from the database if they are from the Intelligence Server you are now using. This is applicable if you are using clustered Intelligence Servers.

You can log different statistics for each project. For example, you may want to log the report job SQL for your test project when tracking down an error. If you logged report job SQL for your production project, and your users are running many reports, the statistics database would quickly grow to an unwieldy size.

Recording Performance Counters in the Statistics Tables

Intelligence Server can be configured to collect performance information from the Diagnostics and Performance Logging Tool and record that information in the statistics database. For more information about logging performance counters, see Configure What is Logged.

Intelligence Server can collect and log information from the MicroStrategy Server Jobs and MicroStrategy Server Users categories. On UNIX or Linux, Intelligence Server can also collect and log information from the following categories:

Memory
System
Process
Processor
Network Interface
Physical Disk

This information is recorded in the STG_IS_PERF_MON_STATS table in the statistics database.

To Configure the Performance Counters to Record Information in the Statistics Repository

Open the Diagnostics and Performance Logging Tool.
- From Developer: From the Tools menu, select Diagnostics.
  If you are running MicroStrategy Developer on Windows for the first time, run it as an administrator.
  Right‑click the program icon and select Run as Administrator.
  This is necessary in order to properly set the Windows registry keys. For more information, see KB43491.
  If the Diagnostics option does not appear on the Tools menu, it has not been enabled. To enable this option, from the Tools menu, select MicroStrategy Developer Preferences. In the General category, in the Advanced subcategory, select the Show Diagnostics Menu Option check box and click OK.
- In Windows: From the Windows Start menu, point to All Programs, then MicroStrategy Tools, and then select Diagnostics Configuration.
- In Linux: Navigate to the directory ~/MicroStrategy/bin and enter mstrdiag.
From the Select Configuration drop-down list, select CastorServer Instance.
Select the Performance Configuration tab.
Make sure the Use Machine Default Performance Configuration check box is cleared so that your logging settings are not overridden by the default settings.
In the Statistics column, select the check boxes for the counters that you want to log to the statistics repository.
In the Statistics Properties group, in the Logging Frequency (min), specify how often (in minutes) you want the performance counters to log information.
From the Persist statistics drop-down list, select Yes.
From the File menu, select Save. The changes that you have made to the logging properties are saved.

The Statistics Database

Intelligence Server logs the specified statistics to the staging tables in the statistics repository. For a detailed examination of the staging tables in the statistics repository, see the Statistics Data Dictionary in the System Administration Help.

If you are using Enterprise Manager to monitor your statistics, the database that hosts the staging tables also contains the Enterprise Manager data warehouse. The information in the staging tables is processed and loaded into the data warehouse as part of the data load process. For information about the structure of the Enterprise Manager data warehouse, see the Enterprise Manager Data Dictionary. For steps on configuring Enterprise Manager and scheduling data loads, see the Enterprise Manager Help.

Intelligence Server may open up to one database connection for each project that is configured to log statistics. For example, in a project source with four projects, each of which is logging statistics, there may be up to four database connections opened for logging statistics. However, the maximum number of database connections is typically seen in high-concurrency environments.

In a clustered environment, each node of the cluster requires a database connection for each project loaded onto that node. For example, a two-node cluster with 10 projects loaded on each node has 20 connections to the warehouse (10 for each node). Even if the same 10 projects are loaded on both nodes, 20 database connections exist.

Supported Database Platforms

MicroStrategy supports the following database platforms for use with Intelligence Server statistics:

SQL Server
Oracle
Teradata
IBM DB2 UDB
Sybase ASE

For information about the specific versions of each database that are supported, see the Readme.

Logging All Statistics from a Project Source to the Same Database

By default, all projects for a project source must be configured to log statistics individually. This configuration is called Complete Session Logging. It allows some projects to log statistics to a database and some projects to log to another database.

The Enterprise Manager data warehouse must be in the same database as the statistics repository for a project. If you are using Enterprise Manager in a complete session logging configuration, there are as many Enterprise Manager data warehouses as there are statistics repositories. A separate Enterprise Manager project must be configured for each statistics repository.

MicroStrategy recommends that you configure all projects in your project source to log statistics to the same database. This is accomplished by configuring your system to use Single Instance Session Logging. This can minimize session logging and optimize system performance.

Under single instance session logging, you must still specify which statistics are logged for each individual project in the project source, as described in Overview of Intelligence Server Statistics.

To use single instance session logging successfully, the selected single instance session logging project must be loaded onto the Intelligence Server at startup. If clustered Intelligence Servers are being used, the project must be loaded onto all the clustered Intelligence Servers. Failing to load this project on all servers at startup results in a loss of session statistics for any Intelligence Server on which the project is not loaded at startup. For details on the possible side effects of not loading all projects, see MicroStrategy Tech Note TN14591.

To Log All Statistics from a Project Source to the Same Database

In Developer, right-click the project source and select Configure MicroStrategy Intelligence Server.
On the left, expand Statistics, then select General.
Select the Single Instance Session Logging option.
Select a project from the drop-down list.
Click OK.