Sorry, I did not understand. Can you elobarate more. I already have cross joins in my dataset.

Hello Guys, I have an attribute with 85,611 rows and I wanted this to be a parameter. I declared the parameter as multivalue parameter without cascading but it is affecting the performance so how can I solve this problem. Please help me out from this problem. I was stuck up here trying to solve this. For your information this is from SSAS cube. I apprecite your time. Thanks and Regards Tarak I'd think you should use JOINs instead of params.If you think my suggestion is useful, please rate it as helpful. If it has helped you to resolve the problem, please Mark it as Answer. Sevengiants.com

creating a parameter with 86k possible values, doesnt sound a very good idea by just reading it. :) If you are creating your report with a report model, I am sure you can use the those vaules in a table format and do necessary operations as requested.If you think my suggestion is useful, please rate it as helpful. If it has helped you to resolve the problem, please Mark it as Answer. Sevengiants.com

Hello Guys, I have an attribute with 85,611 rows and I wanted this to be a parameter. I declared the parameter as multivalue parameter without cascading but it is affecting the performance so how can I solve this problem. Please help me out from this problem. I was stuck up here trying to solve this. For your information this is from SSAS cube. I apprecite your time. Thanks and Regards Tarak

As I understood, users don't like multi selection for parameters which contain large dataset. I used this parameter as search parameter instead of multi selection. This solves my problem. In my query, I used Contains function in MDX and Like function in SQL. I showed to end users as demo and they liked it.