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

KB207208: Cube size is slightly larger on the publishing node than on the remote node(s) in MicroStrategy 9.x after the first publication of a cube


Community Admin

• Strategy


In MicroStrategy Intelligence Server 9.x, the cube size is slightly bigger on the node which initially publishes the cube as compared to the cube size seen on remote node(s) of the clustered environment.

SUMMARY
This document outlines the reason for a cube size to be slightly bigger on the publishing node than on remote node(s) when the cube is published for the first time in Strategy 9.x.
 
SYMPTOM
In Strategy Intelligence Server 9.x, the cube size is slightly bigger on the node which initially publishes the cube as compared to the cube size seen on remote node(s) of the clustered environment. For example, the difference in size can be as small as 4KB. 
 
CAUSE
This is working as designed. The size difference is because of the cube index generation on the publishing node. This index is not the cube lookup index and is a different index generated by the Strategy Analytical Engine (AE).
AE index is not persisted to disk, so when the cube gets loaded by the remote node(s), it has a slightly smaller size.
 
 
WORKAROUND
Unload the cube from memory on the node which initially publishes the cube and reload it again. When the cube is unloaded, the generated AE indexes are discarded. 


Comment

0 comments

Details

Knowledge Article

Published:

June 7, 2017

Last Updated:

June 7, 2017