Select Page
The following article lists the settings that require MicroStrategy Intelligence Server 9.x to be restarted in order for the changes to take effect.
Server-level settings
At the server level, only a few settings from each category need a server restart. These are outlined below:
  1. Server Definition
    1. General
      1. Number of network threads
      2. Content Server Location Database Instance
    2. Advanced
      1. Backup Frequency
      2. Cache lookup cleanup frequency (minutes)
      3. Time to run license check (24 hr format)
      4. Use MicroStrategy Scheduler
      5. Scheduler session time out
      6. Enable Performance Monitoring
  2. Statistics
    1. General
      1. Complete Session Logging
      2. Single Instance Session Logging
      3. Single Instance Session Logging Project Selection
  3. Governing
    1. Default
      1. General
        1. User session idle time
        2. Web user session idle time
      2. Memory Settings
        1. Enable Web request job throttling
        2. Maximum Intelligence Server use of total memory
        3. Minimum machine free physical memory
        4. Enable single memory allocation governing
        5. Maximum single allocation size
        6. Enable memory contract management
        7. Minimum reserved memory (Mbytes)
        8. Minimum reserved memory (%)
        9. Maximum use of virtual address space
        10. Memory request idle time (sec)
      3. Working Set
        1. Working Set file directory
        2. Maximum RAM for working set cache (*Note 2)
  4. Projects
    1. General
      1. Apply startup configuration on save (*Note 6)
  5. History Settings
    1. General
      1. Maximum number of messages per user
      2. Repository Type (Switch from File to Database Based)
      3. History Directory
      4. Database Instance
Project-level settings
Only a few settings require a server restart for the changes to take effect. These are outlined below:
  1. Database instances
    1. Statistics
      1. Statistics database instance
  2. Caching
    1. Result Caches
      1. Cache File Directory
      2. Cache encryption level on disk
      3. Maximum RAM Usage (For both Datasets and Formatted Documents)
      4. Maximum number of caches (For both Datasets and Formatted Documents)
      5. RAM swap multiplier
      6. Maximum RAM for report cache index 
    2. Auxiliary Caches
      1. Objects
        1. Server -> Maximum RAM usage  
      1. Element cache
        1. Server -> Maximum RAM usage
        2. Create element caches per passthrough login
        3. Create caches per connection map
  3. Intelligent Cubes
    1. General
      1. Intelligent Cube file directory
      2. Maximum RAM usage
      3. Maximum number of cubes
      4. Create Intelligent Cubes by database connection
      5. Load Intelligent Cubes on startup
      6. Enabling or modifying Dynamic Sourcing options
  4. Security filter
          1.    General
                      1.    Creation of a security filter
Important Notes:
  1. Changes to a database instance or database connection do not require a restart of MicroStrategy Intelligence Server 9.x. However, for the new settings to take effect, all cached connections (appearing in the Database Connection Monitor) must be disconnected. After a setting change, any cached database connections will continue to use the old settings.
  2. Increasing the ‘Maximum RAM for Working Set cache’ setting does not require MicroStrategy Intelligence Server to be restarted. Only when the value is to be decreased is a restart required. This also applies to ‘Maximum RAM usage’ as well as ‘Maximum number of caches’ settings. (See TN7696 for additional details)
  3. When a setting is not a runtime setting, MicroStrategy Desktop prompts users to restart MicroStrategy Intelligence Server 9.x to effectively register the change.
  4. If changes are made to any objects in the Metadata from a 2-tier connection, those changes will not be reflected in any server connections unless the object cache in the server memory is updated. Restarting the server will clear the object cache and make the changes. Users can also purge the object cache manually, allowing new versions of objects to be retrieved from the metadata. Editing objects from within the 3-tier connection automates this process by keeping the updated version in memory.
  5. For project level settings that require a server restart, unloading and then reloading a project will not make project-level setting changes take effect.
  6. Apply startup configuration on save: This option allows changes to be reflected immediately across the cluster. If the check box is cleared, changes are saved on clicking OK, but are not put into effect until Intelligence Server is restarted.

TN39685: Setting changes which require MicroStrategy Intelligence Server 9.x to be restarted

Secured By miniOrange