Edit All Server-Level Settings

MicroStrategy ONE (September 2024) adds the Unload cube caches not used for (minutes) setting.

You can search, view, and edit server-level settings. Administrators can export the server settings in this tab to a .csv file to keep a record of their settings, and import a previously saved file to apply settings to an environment.

The ability to view or edit certain settings is determined by a user's privileges. All necessary privileges are included in the Administrator role by default. You must belong to the System Administrators group to use this feature.

Open the Workstation window.
In the Navigation pane, click Environments.
Right-click a connected environment and choose Properties.
In the left pane, click All Settings.

Fields

Allow lockout duration (Minutes) Set a the amount of time in minutes to lock an account after a user fails to log in a certain number of times, as specified in Lock after (failed attempts). The minimum is 15. The maximum is 525960. The default is No Limit and indicates there is no time limit to account lockout.

Allow rotating characters from last password When this option is disabled, Intelligence Server prevents users from using a password that is backwards from the old password. This option is enabled by default.

Allow user login and full name in password When this option is disabled, Intelligence Server ensures that new passwords do not contain the user's login or part of the user's name. This option is enabled by default.

Allow user to log on if Web Single Sign-on - MicroStrategy user link not found Enable this option to allow users that are not linked to a MicroStrategy user, to log in to MicroStrategy Web as a guest. This option is disabled by default.

Import user at logon Enables this option to import a single sign-on user into the MicroStrategy metadata when the user logs on to MicroStrategy Web for the first time.

Always open dashboards/documents with the last saved view in Library This option ensures all content in the environment opens with the last saved view that the author intended (base view). The dashboard or document is always reset upon execution. This option is disabled by default, meaning content is opened with the last viewed state of the user. This option can be overwritten by the project or individual content level setting.

Backup Frequency (minutes) Controls the frequency (in minutes) at which cache, History List messages, and Intelligent Cubes are backed up to disk. A value of 0 means that cache, History List messages, and Intelligent Cubes are backed up immediately after they are created. The default is 0.

Balance MicroStrategy Server threads Controls whether threads within the Intelligence Server are allocated to processes such as object serving, element serving, SQL generation, and so forth that need them most, while less loaded ones can return threads to the available pool. This option is disabled by default.

Cache lookup cleanup frequency (sec) Cleans up the cache lookup table at the specified frequency (in seconds). This reduces the amount of memory it consumes and the time it takes to back up the lookup table to disk. The default is 0.

Clients session idle time (sec) Controls session idle time for Web, Library, Workstation, Command Manager, and Integrity Manager. The maximum is 999,999. The minimum is 0. You can also select No Limit. The default is 600.

Enable background execution of documents after their caches hit If this option is enabled, when a document cache is hit, Intelligence Server displays the cached document and re-executes the document in the background. If this option is disabled, when a document cache is hit, Intelligence Server displays the cached document and does not re-execute the document until a manipulation is performed. This option is disabled by default. Selecting this option speeds up document manipulation, but may increase the load on Intelligence Server if users frequently load documents without manipulating them.

Enable custom HTML and JavaScript content in dashboards Enabling this option allows users with the appropriate access to display third-party Web applications or custom HTML and JavaScript directly in the dashboard. This option is enabled by default. Although the ability to display Web applications or custom HTML and JavaScript directly in a dashboard is governed by user privileges, MicroStrategy recommends disabling these features to ensure a secure environment.

Enable performance monitoring Enables Intelligence Server logging in to Microsoft Windows Performance Monitor. Select this option to enable the ability to add counters to the Performance Monitor, specifically for MicroStrategy Server Jobs and MicroStrategy Server Users. If you clear this option, you cannot select these options within the Performance Monitor. This option is enabled by default.

Enable web user session recovery on Logout Select this option to allow users to recover the report, document, or dashboard they were in when their session ended. This option is enabled by default.

Session Recovery backup expiration (hrs) How many hours a session backup can remain on disk before it is considered expired. After it is expired, the user cannot recover the session. The default is 168.

For job and History List governing, exclude reports embedded in Report Services Documents If this option is enabled, reports executed as part of a Report Services Document are not counted against the server-level job limits above and the project-level job limits set in the All Settings section of the project's Properties dialog. This option is disabled by default.

Hash iterations for password encryption Select the number of iterations that a password is hashed. This provides even greater security on top of the algorithm by iteratively hashing the hash a configurable number of times. The minimum is 1000. The maximum is 1000000. The default is 10000.

History list repository type Select the location for storing history list messages.

Starting in MicroStrategy ONE (June 2024), file and database-based options for history list storage are deprecated. MicroStrategy recommends a hybrid configuration since it improves history list performance.

File-based (deprecated), in which the message information and message results are stored in a file on the Intelligence Server machine.
Database-based (deprecated), in which the message information and message results are stored in a database.
Hybrid, where the message information is stored in a database and the message results are stored in a file on the Intelligence Server machine.

This option only affects new history lists. Old history lists cannot be merged. Use the Configuration wizard to migrate existing history data. Once saved, you can't switch back to file or database-based history lists.

Database based repository type

Backup report history caches to database If this option is enabled, History caches are stored in the database without needing to be preserved in the file system. If this option is cleared, History caches are stored in the Intelligence Server file system. This option is enabled by default. MicroStrategy recommends leaving this option enabled for performance and reliability reasons.
History list database instance If you use a Database-Based History List repository, select the database instance that points to the History List repository in the database. The default is None.
External central storage directory for Database-based History List Specifies where file-based History List messages are stored if you are using a hybrid History List repository. When you choose hybrid storage, this setting is required. The default is empty.

File based repository type

History directory If you use a File-Based History List repository, you can store the History List in a file folder on the machine that hosts Intelligence Server. The default location of this folder is relative to the installation path of Intelligence Server: .\Inbox\<Server definition name>.

Import SAP users A user with the same SAP BW username is created in MicroStrategy, within the Warehouse Users group. This option is disabled by default.

Lock after (failed attempts) Specify the number of failed login attempts allowed. Once a user has this many failed login attempts in a row, the user is locked out of the MicroStrategy account until an administrator unlocks the account. Select No Limit so that users are never locked out of their accounts. The default is No Limit.

Web Request job throttling

Maximum Intelligence Server use of total memory (%) This sets the maximum amount of total system memory (RAM + Page File) that the Intelligence Server process can use compared to the total amount of memory on the machine. The default is 97.

Maximum memory for Working Set cache (%) This setting is only available in MicroStrategy Cloud Environment (MCE) containerized environments. Maximum RAM for the working set cache in terms of the percentage of total memory. The valid range is 1-100 and the default value is 10. This setting is only exposed in a container environment.

If you are using a MicroStrategy version prior to MicroStrategy ONE (September 2024), this setting is named Maximum RAM for Working Set Cache %.

Enable Dynamic Working Set Limit: Starting in MicroStrategy ONE (September 2024), allow the Intelligence server to automatically increase or decrease the working set limit based on user settings and available resources in the system. This option is disabled by default.

Maximum memory for working set cache (MB) This setting is only available in MicroStrategy Cloud Environment (MCE) non-containerized environments. Specifies the size of the pool of memory (in megabytes) allocated for creating and initially storing reports in the working set. This is also the size of the largest working set that can be created. The default is 2048 MB (2GB). The minimum is 200MB. The maximum is 4194303MB (4TB).

If you set this limit to more memory than the operating system can make available, Intelligence Server allocates approximately 10% of the available server memory and then fine-tunes the allocation based on performance monitor log data recorded over time.

Enable Dynamic Working Set Limit: Starting in MicroStrategy ONE (September 2024), allow the Intelligence server to automatically increase or decrease the working set limit based on user settings and available resources in the system. This option is disabled by default.

Maximum memory consumption for Excel files (MB)

Prior to MicroStrategy ONE (June 2024), this setting limits the memory consumption for Excel files generated from MicroStrategy Web. Set the limit according to the expected size of the Excel documents to be generated to avoid memory-related errors. To remove the limit, select No limit. The minimum is 0. The maximum is 2047 MB. The default is 512 MB.

Starting in MicroStrategy ONE (June 2024), this setting limits the memory consumption for Excel files generated from MicroStrategy Web. Set the limit according to the expected size of the Excel documents to be generated to avoid memory-related errors. The minimum value is 1. The maximum value is 2,097,151 MB. The default value is Use inherited value (-1). This means that when you upgrade to the latest build, you won't be affected by this setting and continue to use the value set at the server level.

Maximum memory consumption for HTML files (MB) Limits the memory consumption for HTML files. Set the limit according to the expected size of the HTML documents to be generated to avoid memory-related errors. To remove the limit, select no limit. The minimum is 0. The maximum is 2047 MB. The default is 512 MB.

Maximum memory consumption for Intelligent Cubes (%) Specifies the maximum percentage of system RAM that Intelligent Cubes are allowed to consume. The default is 50. This setting is only exposed in the container environment.

Maximum memory consumption for PDF files (MB) Limits the memory consumption for PDF files. Set the limit according to the expected size of the PDF documents to be generated to avoid memory-related errors. To remove the limit, select no limit. The minimum is 0. The maximum is 2047 MB. The default is 512 MB.

Maximum memory consumption for XML files (MB) Limits the memory consumption for XML files. Set the limit according to the size expected of the XML documents to be generated to avoid memory-related errors. The minimum is 0. The maximum is 2047 MB. The default is 512 MB.

Maximum number of XML cells Limits the size of reports (rows x columns) when they are executed from MicroStrategy Web. When this limit is met, incremental fetch is used. The maximum is 9999999. The default is 500000.

Maximum number of XML drill paths Limits the number of attributes to which users can drill in MicroStrategy Web. Attributes appear under the hierarchy to which they belong, and hierarchies appear in alphabetical order by the name of the hierarchy. If this setting is set to a low number, the available drill attributes may not appear to the user. However, if it is set too high, performance may be affected because reports will consume more memory. The maximum is 3000. The default is 100.

Maximum number of history list messages per user Controls how many messages can exist in a user's History List. The default is 10000.

Maximum number of jobs Limits the number of concurrent jobs that may exist on this Intelligence Server. Concurrent jobs include report, element, and autoprompt requests that are executing or waiting to execute. Finished (open) jobs, cached jobs, or jobs that returned errors are not counted. To remove the limit, select no limit. The default is 10000.

Maximum number of interactive jobs Limits the number of concurrent interactive (non-scheduled) jobs that may exist on this Intelligence Server. To remove the limit, select no limit. The default is no limit.

Maximum number of user sessions Limits the number of user sessions (connections) for an Intelligence erver. A single user account may establish multiple sessions to an Intelligence Server. Each session connects once to the Intelligence Server and once for each project the user accesses. Project sessions are governed separately with a project-level setting. When the maximum number of user sessions is reached, users cannot log in, except for the administrator, who may wish to disconnect current users or increase the governing setting. To remove the limit, select no limit. The default is 320.

Maximum single allocation size (MB) If the request exceeds this limit, the request is denied. Each request is treated in the order it is received, so each is subject to the original memory limit. This prevents a few large jobs or reports from consuming large portions of memory at the expense of smaller jobs. To disable single allocation governing, select Disabled from the drop-down.

Maximum use of catalog cache memory (MB) Limits the maximum amount of memory, in megabytes, used by the catalog cache. The default is 25 MB. To disable the catalog cache, select Disabled.

Memory Contract Management: Memory Contract Manager is an Intelligence Server component that is controlled by the following settings.

Maximum use of virtual address space (%) If the Intelligence Server machine uses a 32-bit operating system, specify the maximum amount of the virtual address space that Intelligence Server can use, as a percentage of the total virtual address space. Memory requests that would cause Intelligence Server to exceed this limit are denied. The default setting is 90.

Maximum use of virtual space is only used in 32-bit operating systems. In a 64-bit operating system, the amount of memory that can be reserved with this setting is so large, it is meaningless. Use Minimum reserved memory to control the amount of memory available for Intelligence Server.

Memory request idle time (sec) The amount of time Intelligence Server denies requests while operating in memory request idle mode. The default is 600.
Minimum reserved memory for external processes (%) Specify the amount of memory (as a percentage of the total system memory) that Intelligence Server cannot use. This may be useful if the machine is also used to run software from other parties and is not solely dedicated to Intelligence Server. The recommended value is 10.

Intelligence Server always reserves a minimum of 500 MB for its own operation. If the machine does not have this much memory, or if the Minimum reserved memory would leave less than 500 MB available for Intelligence Server, no memory is reserved for other processes.
Minimum reserved memory for external processes (MB) Specify the amount of memory (in MB) that cannot be used by Intelligence Server. This may be useful if the machine is also used to run software from other parties and is not solely dedicated to Intelligence Server. The maximum is 10239 MB. This option is enabled and the field is set to 0 by default.

Message lifetime (days) Controls how many days messages can exist in a user's History List. The default no limit leaves messages in the system until the user deletes them.

Minimum machine free physical memory (%) This sets the minimum amount of RAM that must be available compared to the total amount of physical memory on the machine. The default is 0.

Minimum number of character changes in password The minimum number of character changes. The minimum is 0. The maximum is 999. The default is 3.

Minimum password length The minimum password length. The minimum is 0. The maximum is 999. The default is 0.

Minimum lower case characters in password The minimum number of lower case (a-z) characters that must be present in users' passwords. The default is 0.
Minimum numeric characters in password The minimum number of numeric (0-9) characters that must be present in users' passwords. The default is 0.
Minimum special characters in password The minimum number of non-alphanumeric (symbol) characters that must be present in users' passwords. The default is 0.
Minimum upper case characters in password The minimum number of upper case (A-Z) characters that mist be present in users' passwords. The default is 0.

Mobile APNS and GCM session idle time (sec) Limits the time, in seconds, that mobile client connections remain open to download Newsstand subscriptions. A value of -1 indicates no limit. The default is 1800.

Number of high priority connections Specify the maximum number of high connection threads that are used to import data into the data warehouse. The minimum is 0. The maximum is 999. The default is 1.

Number of low priority connections Specify the maximum number of low connection threads that are used to import data into the data warehouse. The minimum is 0. The maximum is 999. The default is 20.

Number of medium priority connections Specify the maximum number of medium connection threads that are used to import data into the data warehouse. The minimum is 0. The maximum is 999. The default is 1.

Number of messages deleted to reclaim History List space When the History List is full and another message is added, Intelligence Server automatically deletes the specified number of messages, beginning with the oldest messages. If this number is set to zero, new messages are not added to the History List until messages are manually removed. The default is 0.

Delete error message first If this option is enabled, error messages are deleted (oldest first) before regular History List messages. This option is enabled by default.
Delete oldest messages by Select the criterion to be used for deleting messages. The available options are Creation Time, Modification Time, Start Time, and Finish Time. The default is Creation Time.

Number of past passwords remembered The number of each user's previous passwords that Intelligence Server stores. Intelligence Server prevents users from using a password that is identical to one they have previously used. The minimum is 0. The maximum is 999. The default is 0.

Number of threads for client-server communication Controls the number of network connections available for communication between Intelligence Server and the client, such as Developer or MicroStrategy Web. The minimum is 1. The maximum is 80. The default is 5.

Scheduler session time out (sec) Controls how long the Scheduler attempts to communicate with Intelligence Server before timing out. The default is 300 seconds.

Session recovery and deferred inbox storage directory Specifies where the session information is written to disk. The default is .\TmpPool.

Smart Memory Usage for Intelligence Server Controls usage of the Memory Mapped File Buffer for In-memory cubes. The available options are Apply best strategy to maximize performance with given resources, Turn-off the capability without exceptions, Disable the capability, and Enable the capability. This setting can be overwritten at the project level unless the Turn-off the capability without exceptions option is selected.

Synch Web Single Sign-on user at logon Enable this option to sync Web single sign-on users when they log in.

Server Level Session Statistics

Complete Session Logging - Projects log statistics to different databases and need to ensure complete data in all of them Different projects log statistics to different databases. This ensures complete data for all these projects. This option is enabled by default.
Single Instance Session Logging - log statistics to a single project's database defined by: (This will overwrite Project Level settings) Statistics for all projects on this Intelligence Server are logged to a single database. From the drop-down list, select the project name whose database you want to log statistics to. The default is None.

Synchronize SAP groups The MicroStrategy groups assigned to a MicroStrategy user are synchronized with the SAP BW roles assigned to the SAP BW user. This means that if SAP BW roles have been added or removed for an SAP BW user, the associated MicroStrategy user is added or removed from the MicroStrategy groups that represent the SAP BW roles. This option is disabled by default.

Import SAP groups Import SAP BW roles as groups in MicroStrategy. This option is disabled by default.

Time to run license check (24 hr format) Sets the specific time at which Intelligence Server checks licenses daily. The default is 23:59.

Include LDAP users Select this option to include LDAP users in the license check. This option is disabled by default.

Token Lifetime (Minutes) The lifetime, in minutes, of the token. The minimum is 1. The maximum is 99999. The default is 1440.

Tools session idle time (sec) Controls session idle time for Developer and Object Manager. The maximum is 999,999. The minimum is 0. You can also select No Limit. The default is 1800.

Unload cube caches not used for (minutes) Starting in MicroStrategy ONE (September 2024), the cube cache can be released from memory if not accessed by the specified amount of time. The value is set to No Limit by default. To activate this setting, set it to a value based on your business needs. You can specify a value between 1 minute and 525600 minutes (equivalent to one year).

Update pass-through credentials on successful login Select to update or disable updating the user's database credentials, LDAP credentials, on a successful MicroStrategy login. The default is Database credentials.

Use MicroStrategy Scheduler Enables the scheduling features in the MicroStrategy environment. If this option is disabled, neither the reports nor administration tasks can be scheduled. This option is enabled by default.

Use public/private key to sign/verify authentication token Check this toggle button to use a public or private key to sign or verify a token. This requires the setup of a public or private key. This option is disabled by default.

User Affinity Cluster In a clustered system, causes Intelligence Server to connect all sessions for a given user to the same node of the cluster. This improves performance by reducing the resources necessary for the user's History List. This option is disabled by default. If the User Affinity Cluster option is enabled, Subscription load balancing causes Intelligence Server to load-balance subscriptions across all nodes of the cluster.

Subscription load balancing Causes Intelligence Server to load-balance subscriptions across all nodes of the cluster. One subscription job is created for each user or user group in the subscription. This option is disabled by default.

Working set file directory Specifies the location where the user's active working sets are written to disk if they have been forced out of the pool of memory allocated for the Maximum RAM for working set cache. The default is .\TmpPool.