Export (0) Print
Expand All

Maintaining Monitoring Server databases

PerformancePoint Server 2007

Updated: 2009-04-23

In this article:

The requirements for maintenance of the Monitoring Server database are minimal. The most important task is to routinely back up the data, so that in the event of data corruption or data loss, the system can be restored. It is also important to ensure that the size of the database does not exceed the maximum disk space, and that the available disk space is sufficient for your needs. If the database does become corrupted despite these basic maintenance requirements, restoring from a previous backup is recommended because the process of fixing the structure of the data can be extremely difficult.

Session objects

The Microsoft Office PerformancePoint Server 2007 repository is a potential bottleneck for Web server scaling, because temporary objects are stored in the repository and require a periodic automatic cleanup. The size of the temporary object table can be quite large for high bandwidth farms with OLAP views. This can be mitigated by lowering the default age of the temporary objects from 10 hours to 2 hours. This can be changed in the settings table of the monitoring database. Change the value MaxHoursOfSessionObjects from 10 to 2.

There are two other items to consider when configuring the clearing of temporary objects. The first is the HoursToCleanSessionObjects row. This sets the number of hours between temporary object removals. This setting can be changed from 2 to 1 to perform the cleanup more often. The second item is the tempFCOClean stored procedure. This procedure is executed when cleaning up the temporary objects.

The temporary object cleanup can be disabled to allow more flexible scheduling of the stored procedure (TempFCOClean) within Microsoft SQL Server 2005. Setting HoursToCleanSessionObjects and MaxHoursOfSessionObjects to “0” will disable the cleanup.

Parameter objects

When parameters are used in a dashboard, parameter values that were selected are cached in the parametersvalue table. This table can grow to impact performance but this is not very likely. This clearing of the table has settings stored in the setting table of the Monitoring Server database. The MaxHoursOfParameterValues contains the age (2,160 hours) of the parameters that will be deleted when the parameter values are cleaned. The HoursToCleanParameterValues contains the time between parameter value cleanups.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for PerformancePoint Monitoring Server.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft