on 04-10-2015 11:03 AM
hello
I do not understand the generation of the P-index on the E fact table after compression of an inventory cube, my basic purpose of compression is to save storage space but the P-index is very large and it has doubled the storage space, can someone tell me how to resolve this issue? The impact when dropping this index?
thanks
Hi Akrem,
unfortunately compression retains the aggregated format of the data. I would recommend following the note below to reduce the number of requests stored in your admin tables...
Running RSSM_REDUCE_REQUESTLIST...
1431315 - P24: Reduction of very large request lists in cubes and DSOs
Thanks,
Colm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.