pe:serverconfiguration:loggingactivities

Logging activities

There are three types of activities involved when running DSP Web Parts. Assembly and PTS activities on the SharePoint server and activities on Analysis Services.


To enable assembly logging you need to add entries to the web.config file. If you have multiple extended virtual servers you have to edit the web.config for each virtual server.

  • If not already exists add following xml elements to the <section group> section.
<sectionGroup name="DecisionSupportPanel">
    <section name="WebPart" 
type="DecisionSupportPanel.SharePoint.WebPart.ConfigurationHandler, 
DecisionSupportPanel.SharePoint.WebPart, Version=4.0.0.0, Culture=neutral, 
PublicKeyToken=4e98b37828e9cbce" />
</sectionGroup>
  • Add following xml elements to the <configuration> section.
<DecisionSupportPanel>
    <WebPart>
         <Log Path="<file path>" Level="<level>" />
    </WebPart>
  </DecisionSupportPanel>
  1. Parameter <file path> is the path to the file were to write the logging information. All users must have write access to specified file.
  2. Parameter <level> decides which information to log, see following table for possible values:
Level (bitwise combining) Name Description
1 DateTime Date and time
WebPartTitle Title of the Web Part
Html True/False if html content is fetched from the cache
Result True/false if Xml Result is fetched from the cache
ChkCube True/False if the component is checking if the cube timestamp is updated
Imperso True/False if impersonation is done when accessing the cube
ConPool Not in use
Performance Time in milliseconds to generate the content
ContentSize Size of the Web Part content in bytes
User Name of user account that access the Web Part
WebPartStorageKey Unique id of the Web Part
2 Error Generated errors
4 XmlDef Definition of the Web Part

Examples of values for the Level attribute:

  • Level = “1” will log all level 1 items.
  • Level = “3” will log all level 1 items and Error
  • Level = “7” will log all level 1 items, Error and XmlDef.


To log 2005 MDX queries you can use the SQL Profiler tool.

To log Analysis 2000 MDX queries you have to add a following parameter to the connection string “Log File=filepath”. You add this parameter from the Data Source step in the Web Part Wizard.

Example:

Provider=MSOLAP;MDX Unique Name Style=3;MDX Compatibility=2;
Persist Security Info=False;Connect Timeout=60;Client Cache Size=25;
Auto Synch Period=10000;Log File=c:\log\mdx.txt;

NB! The file will only hold MDX statement for the latest made query.


First of all you have to activate query activities on your Analysis Sevices. You do that by opening Analysis Manager and right click on the server and select Properties. Then click on tab Logging and select Log queries sent to server and set Write to log once per queries to 1.

Each query will now be logged to an access file named msmdqlog.mdb located in the /Program Files/Microsoft Analysis Server/Bin folder.

List of fields in the table storing logged activities:

Field Description
MSOLAP_Database The name of the database used in the query
MSOLAP_Cube The name of the cube used in the query
MSOLAP_User The name of the user that ran the query
Dataset A numeric string indicating the level from each dimension used to satisfy the query
Slice A string indicating the data slice for the query
StartTime The time the query began
Duration The length of time (in seconds) of the query execution
MOLAPPartitions The number of different multidimensional OLAP (MOLAP) partitions that were used to satisfy the query
ROLAPPartitions The number of different relational OLAP (ROLAP) partitions that were used to satisfy the query
SamplingRate The sampling rate at the time the query was executed
  • pe/serverconfiguration/loggingactivities.txt
  • Last modified: 2014/02/27 10:59
  • by pcevli