In the Physical Table properties dialog, in the General tab, make one of the

Managing Performance Tuning and Query Caching 7-19 The probing query is logged when the log level is equal or greater than 2. The status of the subsystem, such as if the subsystem is enabled and events such as start and shutdown events, are also written to the server log. Be aware of the following cache purge issues: ■ The size of multidimensional cache entries can grow very large. Therefore, a limit on the size of each member set has been established in the MDX_MEMBER_CACHE section of the NQSConfig.INI file. ■ The format of persisted cache might not be consistent after an upgrade. Therefore, you should purge all cache before a software upgrade. ■ The cache is populated the first time that the query runs. You should arrange to populate the cache during off-peak hours, to minimize performance impact. The following purge procedures are specific to SAPBW data sources: ■ SAPurgeALLMCNCache. Purges all SAPBW cache entries. The following shows the syntax of this procedure: SAPurgeALLIMCNCache ■ SAPurgeMCNCacheByCube. Purges all cache entries that are associated with the specified physical cube. The database name and cube name are the external names of the repository objects. The following shows the syntax of this procedure: SAPurgeMCNCacheByCube DBName, CubeName Table 7–2 describes the messages that are returned. Only users with administrative privileges can run ODBC purge procedures. Caution: With each increased logging level, performance is impacted. Use caution when increasing the log level for users. Note: In the Administration Tool, you can purge cache for an individual cube table by right-clicking the cube table, and then selecting Purge Member Cache. This must be performed in online mode by a user with administrator privileges. Table 7–2 SAP Purge Cache Return Codes and Messages Return Code Return Message 1 SAPurgeALLMCNCache returns successfully. 1 SAPurgeMCNCacheByCube returns successfully. 59116 The database specified does not exist. Note: If the database and physical cube are both wrong, then this result code is returned. 85025 The physical cube specified does not exist.