So, let's just say we have a pivot table chart setup.. the data structure is, oh around 2,000,000 rows with approximately 20 fields for each.
Immediately you know this is a large pivot table, and the data loads properly and without any issues - however there's an enormous delay and wait time.
Is there nothing (variable.. setting) that allows for a more dynamic load approach?
Were I able to post this in the Server forums too I would, as we are also running QlikView Server - so if there's a more appropriate response in that line, please reclass as you see fit.
I too had a similar situation where one Tab had a Pivot which loads about 1 million rows of calculated dimensions data..I looked for a solution for this problem , but the only solution i could come up was to separate this sheet object from this QVW, place it in another QVW and just a Button to click on the first QVW which takes to the second QVW. This way both the applications now run really faster and the end users would not know that they are opening the different QVW manually everytime...I dont know if you can really do this in your current project, but I dont think there is any other option. Also you may try pumping up the memory on the server as it would always help..
I too had a similar situation where one Tab had a Pivot which loads about 1 million rows of calculated dimensions data..I looked for a solution for this problem , but the only solution i could come up was to separate this sheet object from this QVW, place it in another QVW and just a Button to click on the first QVW which takes to the second QVW. This way both the applications now run really faster and the end users would not know that they are opening the different QVW manually everytime...I dont know if you can really do this in your current project, but I dont think there is any other option. Also you may try pumping up the memory on the server as it would always help..
Do you have to wait for a very long time to open the file on server or to get the results after a selection?
For the first problem, you could set the pre-load option on the server (document section), so it would be already on the memory even for the first user that tries to open it
For the second problem, I would go to Andy's approach.
Maybe you could also segment the pivot creating a document with less fields (and maybe rows) if it fits the users needs. Data reduction (on section access) could also improve the performance for some users.
