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

KB17628: How to change the maximum database table chunking size used for data transfer between the database multiprocess component (M8MulPrc) and MicroStrategy Intelligence Server


Community Admin

Placeholder •


The M8MulPrc/M8MulPrc_32 process is a database connection process spawned from the MicroStrategy Intelligence Server 9.x that handles the execution of queries and management of the database connections. This functionality is run in a separate process to isolate MicroStrategy Intelligence Server from any unexpected conditions that may be returned from the database or ODBC driver.

The M8MulPrc/M8MulPrc_32 process is a database connection process spawned from the Strategy Intelligence Server that handles the execution of queries and management of the database connections. This functionality is run in a separate process to isolate Strategy Intelligence Server from any unexpected conditions that may be returned from the database or ODBC driver.
 
When the M8MulPrc process retrieves data from the database, the data is sent back to the Strategy Intelligence Server as a chunk of the data table. This may sometimes be observed in the memory contract manager logs as originating from the "MDb::Table" component. By default the maximum size of the chunked data is set to a value of 300 MB and any dataset larger than this value will be broken into multiple chunks. Note, however that a single database request may result in multiple smaller chunks (i.e. the database process will not attempt to buffer data into a single large chunk) but the maximum chunk size will be limited to 300 MB.
 
It is possible to change the maximum size by adding a new entry to the registry (on Unix\Linux systems, the MSIReg.reg file). Note, however, that such changes are not supported by Strategy Technical Support - users may incur performance penalties by modifying the default values.
 
Steps to modify the MaxCrossProcessTableSize parameter:

  1. Open the registry using the registry editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\DSS Suite.
    For a 64-bit operating system, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Strategy\DSS Suite
  2. Right click in this key and add a new DWORD value.
  3. Name this entry "MaxCrossProcessTableSize".
  4. The value of the registry entry should be set to the new re.quired chunk size in megabytes in hexadecimal

On Unix\Linux systems, simply edit the MSIReg.reg file and under the entry add a new entry:
 
"MaxCrossProcessTableSize"=dword:<value in hexadecimal>
Registry Modification:
WARNING:
Modifying registry values incorrectly may cause serious, system-wide problems that may require the re-installation of Microsoft Windows NT. Any edit of the registry is done at the user's own risk. Since these are user-initiated changes, they are not covered by any Strategy warranty. If using Microsoft Windows NT, the user should backup the registry and/or update an Emergency Repair Disk (ERD) prior to alterations.
 
Disclaimers and Limitation of Liabilities:
Disclaimer: The utility application is provided "as is" and without warranty of any kind. Strategy Expressly disclaims all warranties, express, implied or statutory, including, without limitation, the implied warranties of merchantability, fitness for a particular purpose, satisfactory quality and noninfringement.
 
Limitation of Liability: Strategy shall have no liability to licensee for any damages of any kind, including, but not limited to, liability for direct, indirect, special, incidental or consequential, damages (which shall include, but not be limited to, loss of data or information, loss of revenue or anticipated profits or lost business).
 


Comment

0 comments

Details

Knowledge Article

Published:

June 5, 2017

Last Updated:

February 13, 2024