EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB9481: Why is the session information available for projects that have statistics logging disabled in MicroStrategy Enterprise Manager?


Community Admin

• Strategy


Why is the session information available for projects that have statistics logging disabled in MicroStrategy Enterprise Manager?

While the statistics logging is configured at the project level in Strategy Intelligence Server, the server level login and logout information are also recorded in the IS_SESSION_STATS table.
 
Depending on the server level session statistics setting configured under the Strategy Intelligence Server Configuration > Statistics (see KB6400-8X-0523 for a detailed description), server level session information may be recorded in the IS_SESSION_STATS table while logging into a project even though the statistics are disabled for the project.
 
NOTE: Statistics can be manually disabled by the user or they may be disabled if there is a problem during the initialization process of the statistics manager. For the latter case, users can detect that the statistics logging is disabled from the DSSErrors.log messages during the start-up.
 
Consider that there are two projects, pA and pB, under the same Strategy Intelligence Server project source. Also consider, for simplicity, that sAB is the single database instances for statistics logging used by both projects pA and pB.
 
NOTE: Even though the projects within the same Strategy Intelligence Server source can be configured to log to different database instances, Strategy Enterprise Manager requires that all statistics logging is collected within the same database. Thus, it is usually impractical to maintain separate statistics databases for the different projects under the same Strategy Intelligence Server.
 


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry


 Login to pALogin to pB (statistics is disabled for pB)Complete Session Logging2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pA is the designated project)2 entries; 1 for login to server for pA + 1 for login to pA1 entry; 1 for login to server for pBSingle Instance Session Logging (pB is the designated project)1 entry; 1 for login to pANo entry

The logout actions are similar to the actions for the logins above. If there is a login to the server entry for a project, that session will be counted in the session analysis in Strategy Enterprise Manager. If there is no login to the server entry for a project, the project session will be lost even if there is an entry for the project login.
 
In summary:

  • if Single Instance Session logging is configured against a project whose statistics logging is disabled, the statistics data cannot be transferred into the Strategy Enterprise Manager tables for analysis.
  • if Complete Session Logging or Single Instance Session Logging against a project with enabled statistics is configured, the session analysis for the project whose statistics is disabled can be carried out at the server level.

 
The described behavior is by design and administrators should be careful while specifying the Server Level Statistics Logging options to avoid loss of data.
 
A similar situation may occur if asymmetric clustering is used in Strategy 8.1.x or 9.0.x. Refer to the following Strategy Technical Note for further details.
 
KB14591 (KB6400-80X-0422) - Statistics for one or more Intelligence Servers are not migrated during the Strategy Enterprise Manager data load in Strategy Enterprise Manager.  


Comment

0 comments

Details

Knowledge Article

Published:

June 14, 2017

Last Updated:

June 14, 2017