When the Planning Analytics database generates security privileges from a security control cube, it reads every cell from that cube.

If the security control cube is sparsely populated, this results in unnecessary processing and a longer loading time. An example of a sparsely populated security cube would be one that has a greater ratio of default security settings compared to defined security settings.

Parameter type: optional, static

To address this issue, the PrivilegeGenerationOptimization parameter can be added to the Planning Analytics database configuration:


When this parameter is set to T, the Planning Analytics database will read only the populated cells in security cubes. In the case of a sparsely populated security cube, this will dramatically shorten the load time of the Planning Analytics database.

Note: If you populate the security settings via rules and want to use this parameter, you must write feeders for the rules that populate your security cubes. Because security settings are stored as strings, the rules that populate your security cubes must include the FeedStrings function.