cascading parameter issue

  • Hi,

    I'm using SSRS 2008 R2 and I have one report having cascading parameter "Customer" which is very slows on browser but the query that generates the cascading parameter is very fast on SSMS and BIDS but once deploy on server then browser stop responding.

    Can you please help me on this?

    Regards,

    Amit J

  • How many customers are being returned?

    Are you connecting to the same SQL Server from BIDS and the Report Server?

    Are you connecting as the same user or with the same permissions from BIDS and from the Report Server?

    Have you looked at dbo.ExecutionLog in the ReportServer database to see how long the report is taking for retrieval, processing, and rendering to see where the bottleneck is?

  • H Jack,

    Thank you so much for your response, here are answers on your questions might be it would help:

    1) Number of customer getting from query= 84610

    2) Yes we are connected with same server

    3) Yes same users is trying to run the report from BIDS and server (IBIDS runs fast Server not respond)

    4) It does not add rows to log table until it report executes... here we get problem in loading Customer parameter depends on "Business Relationship" parameter.

    One important point is it does not load Customer parameter in IE but in Chrome it loads the parameter but does not respond when clicks on "View Report"

    Regards,

    Amit J

  • amit_pjoshi 52509 (6/16/2015)


    H Jack,

    Thank you so much for your response, here are answers on your questions might be it would help:

    1) Number of customer getting from query= 84610

    2) Yes we are connected with same server

    3) Yes same users is trying to run the report from BIDS and server (IBIDS runs fast Server not respond)

    4) It does not add rows to log table until it report executes... here we get problem in loading Customer parameter depends on "Business Relationship" parameter.

    One important point is it does not load Customer parameter in IE but in Chrome it loads the parameter but does not respond when clicks on "View Report"

    Regards,

    Amit J

    Are the 84610 customer rows before or after applying the business relationship filter to the query?

    Are you applying the filter to the query or to the data set AFTER retrieving all 84610 rows?

    Ideally you should reduce the rows returned for the parameter for at least 2 reasons:

    1. To improve performance. Loading 80K+ rows into a dropdown is goign to be slow no matter what technology you are using.

    2. To improve usability. How can a user find the customer or customers they need scanning through 80K+ rows?

    I'd suggest adding another parameter that the customer parameter depends on that is a partial of the customer name.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply