![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Hi Tony, Look if the query creates a lot of subquery's (you can check that in the query log, sample interval 1) to get your results set. If yes you can try ;cache policy = 7; connection string. Prior to SP3, when the client formed a request to the server, the slice portion of that request could contain at most one member for each dimension. As a result, when the query requested members scattered at multiple levels of a dimension, there was a high likelihood that Sonar would generate many requests to satisfy the query. With OR query functionality enabled, the slice can contain an array of members for each dimension. This can significantly reduce the number of requests sent by the client for a given query. This only works for MOLAP. HTH, Bas "This posting is provided "AS IS" with no warranties, and confers no rights." |
![]() |
| Thread Tools | |
| Display Modes | |
| |