Monitoring and Modifying Intelligent Cube Status

The status of an Intelligent Cube tells you how the Intelligent Cube is currently being used and whether reports can access the Intelligent Cube. To modify the status of an Intelligent Cube, right-click the Intelligent Cube in the Intelligent Cube Monitor, and select one of the actions listed below:

Action	Required Status to Perform Action	Description
Activate	Filed, but not Active	Loads a previously deactivated Intelligent Cube as an accessible set of data for multiple reports.
Deactivate	Active	Removes an Intelligent Cube instance from Intelligence Server memory, but saves it to secondary storage, such as a hard disk.
Update	Active	Re-executes and publishes an Intelligent Cube. When the data for an Intelligent Cube is modified and saved, the Update action updates the Intelligent Cube with the latest data.
Save to disk	Loaded	Saves an Intelligent Cube to secondary storage, and keeps the Intelligent Cube in Intelligence Server memory. If you have defined the backup frequency as zero minutes, Intelligent Cubes are automatically saved to secondary storage, as described in Storing Intelligent Cubes in Secondary Storage.
Delete	Always available	Removes a published Intelligent Cube as an accessible set of data for multiple reports. This action does not delete the Intelligent Cube object saved in a MicroStrategy project. To delete an Intelligent Cube object, you must log into the project containing the Intelligent Cube and delete it there. For information on whether you should deactivate or unpublish an Intelligent Cube, see Deactivating or Unpublishing an Intelligent Cube.
Load in memory	Active, but not Loaded	Moves an Intelligent Cube from your machine's secondary storage to Intelligence Server memory. For information on when to load and unload Intelligent Cubes, see Loading and Unloading Intelligent Cubes. If the memory limit is reached, this action unloads a previously loaded Intelligent Cube from Intelligence Server memory.
Unload from memory	Loaded	Moves an Intelligent Cube from Intelligence Server memory to your machine's secondary storage, such as a hard disk. For information on when to load and unload Intelligent Cubes, see Loading and Unloading Intelligent Cubes.

Additional statuses such as Processing and Load Pending are also used by the Intelligent Cube Monitor. These statuses denote that certain tasks are currently being completed.

Additionally, if you have defined the backup frequency as greater than zero minutes (as described in Storing Intelligent Cubes in Secondary Storage), the following additional statuses can be encountered:

• Dirty: This status occurs if the copy of an Intelligent Cubes data in secondary storage is not up to date with data in Intelligence Server memory. This can occur if an Intelligent Cube is updated in Intelligence Server memory but the new data is not saved to secondary storage.
• Monitoring information dirty: This status occurs if Intelligent Cube monitoring information changes, and this information is not updated in secondary storage. Monitoring information includes details such as the number of reports that have accessed the Intelligent Cube.

In both scenarios listed above, the data and monitoring information saved in secondary storage for an Intelligent Cube is updated based on the backup frequency. You can also manually save an Intelligent Cube to secondary storage using the Save to disk action listed in the table above, or by using the steps described in Storing Intelligent Cubes in Secondary Storage.

Deactivating or Unpublishing an Intelligent Cube

Both deactivating and unpublishing an Intelligent Cube prevent reports that access an Intelligent Cube from being able to load the Intelligent Cube into Intelligence Server memory. This gives you more administrative control of when to make an Intelligent Cube available to reports.

However, each of these actions provides this administrative control in slightly different ways that can fit different scenarios.

Deactivating an Intelligent Cube saves the Intelligent Cube to secondary storage, such as a hard disk. When you reactivate the Intelligent Cube, the copy in secondary storage is loaded back into Intelligence Server memory. This option is ideal when an Intelligent Cube should not be used for some length of time, but after that should be available again in its current form.

Unpublishing an Intelligent Cube deletes the copy of data from Intelligence Server memory without making a copy of the data. To make the Intelligent Cube accessible to reports, the Intelligent Cube must be re-executed against the data warehouse and published to the Intelligent Cube Monitor. This option is ideal if the current Intelligent Cube should not be reported on until it is re-executed against the data warehouse.

Loading and Unloading Intelligent Cubes

When an Intelligent Cube is published, by default, it is automatically loaded into Intelligence Server memory.

Intelligent Cubes must be loaded in Intelligence Server memory to allow reports to access the data in the Intelligent Cube. If an Intelligent Cube is constantly in use, it should be loaded in Intelligence Server memory.

Using the Intelligent Cube Monitor you can load an Intelligent Cube into Intelligence Server memory, or unload it to secondary storage, such as a disk drive.

By default, Intelligent Cubes are loaded when Intelligent Cubes are published and when Intelligence Server starts. To change these behaviors, see:

• Publishing Intelligent Cubes Without Loading Them into Intelligence Server Memory
• Loading Intelligent Cubes when Intelligence Server Starts

One way to free memory on Intelligence Server, which can improve Intelligence Server performance, is to temporarily unload an Intelligent Cube from memory. This can be a good option for Intelligent Cubes that are not constantly in use, because when a report accessing an active but unloaded Intelligent Cube is executed, that Intelligent Cube is automatically loaded into Intelligence Server memory. Be aware that if the Intelligent Cube is very large there may be some delay in displaying report results while the Intelligent Cube is being loaded into memory. For more suggestions on how to manage Intelligence Server's memory usage, see Tune Your System for the Best Performance.

Publishing Intelligent Cubes Without Loading Them into Intelligence Server Memory

By default, Intelligent Cubes are automatically loaded into Intelligence Server memory so that reports can access and analyze their data.

To conserve Intelligence Server memory, you can define Intelligent Cubes to only be stored in secondary storage when the Intelligent Cube is published. The Intelligent Cube can then be loaded into Intelligence Server memory manually, using a schedule, or whenever a report attempts to access the Intelligent Cube.

The steps below show you how to define whether publishing Intelligent Cubes loads them into Intelligence Server memory. You can enable this setting at the project level, or for individual Intelligent Cubes.

To Define Whether Publishing Intelligent Cubes Loads Them into Intelligence Server Memory, at the Project Level

1. In Developer, log in to a project using an account with administrative privileges.
2. Right-click the project and select Project Configuration.
3. Expand Intelligent Cubes, then select General.
4. You can select or clear the Load Intelligent Cubes into Intelligence Server memory upon publication check box:
   • Select this check box to load Intelligent Cubes into Intelligence Server memory when the Intelligent Cube is published. Intelligent Cubes must be loaded into Intelligence Server memory to allow reports to access and analyze their data.
   • To conserve Intelligence Server memory, you can clear this check box to define Intelligent Cubes to only be stored in secondary storage upon being published. The Intelligent Cube can then be loaded into Intelligence Server memory manually, using schedules, or whenever a report attempts to access the Intelligent Cube.

     If you are using multiple Intelligence Servers in a clustered environment, this setting applies to all nodes.

5. Click OK.
6. For any changes to take effect, you must restart Intelligence Server. For clustered environments, separate the restart times for each Intelligence Server by a few minutes.

To Define Whether Publishing Intelligent Cubes Loads Them into Intelligence Server Memory, at the Intelligent Cube Level

1. In Developer, log in to a project using an account with administrative privileges.
2. In the Folder List, browse to the folder that contains the Intelligent Cube you want to configure.
3. Right-click the Intelligent Cube, and choose Edit.
4. From the Data menu, select Configure Intelligent Cube.
5. Under the Options category, select General.
6. Clear Use default project-level settings.
7. Select or clear the Load Intelligent Cubes into Intelligence Server memory upon publication check box:
   • Select this check box to load the Intelligent Cube into Intelligence Server memory when the Intelligent Cube is published. Intelligent Cubes must be loaded into Intelligence Server memory to allow reports to access and analyze their data.
   • To conserve Intelligence Server memory, clear this check box to define Intelligent Cubes to only be stored in secondary storage upon being published. The Intelligent Cube can then be loaded into Intelligence Server memory manually, using schedules, or whenever a report attempts to access the Intelligent Cube.

   If you are using multiple Intelligence Servers in a clustered environment, this setting applies to all nodes.

8. Click OK.
9. In the Intelligent Cube Editor, click Save and Close.
10. Restart Intelligence Server. For clustered environments, separate the restart times for each Intelligence Server by a few minutes.