![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all, Any ideas of how to implement a scalable Paging soluion using MDX (subset is not an option since it first retrieves all data). |
#3
| |||
| |||
|
|
-----Original Message----- "yanec" <yaniv.inbar (AT) retalix (DOT) com> wrote in message news:123001c39191$4c200c40$a301280a (AT) phx (DOT) gbl... Hi all, Any ideas of how to implement a scalable Paging soluion using MDX (subset is not an option since it first retrieves all data). Can you please elaborate more on the problem that you are trying to solve. Usually, PTS will do intelligent paging automatically, and its behaviour can be tuned by using Cache Policy, Cache Ratio etc connection string properties. -- ================================================== Mosha Pasumansky - www.mosha.com/msolap Development Lead in the Analysis Server team All you need is love (John Lennon) Disclaimer : This posting is provided "AS IS" with no warranties, and confers no rights. ================================================== . |
#4
| |||
| |||
|
|
So we played with SubSet but then we realized that subset is not a scalable solution becouse it seems that first the olap prepares the entire mdx query data and only then apply's the subset |
![]() |
| Thread Tools | |
| Display Modes | |
| |