locked
Weird Issue RRS feed

  • Question

  • I have a report which works fine when I run it on the SSRS server, but it takes a lot of time on client's machine. I don't know if it's slow on all client's machines. The report takes several seconds to only show the parameters page and then I have to enter parameters and it takes several seconds to react to those parameters. It takes 2 seconds for the data set to return results when the query is executed in SSMS. Any thoughts? Thanks in advance.
    Friday, February 11, 2011 4:54 PM

Answers

  • Hi,

     

    Base on your description, this issue could be caused by dataset or network. To rule out dataset problem, you can create a same report which has no dataset for parameters default and available values (you can copy and modify the report), and then you and your clients can try to access this report. If this issue persists in the new report, it means that the problem is that report or network. Otherwise, please drop the datasets one by one to find out which one needs more time than others to execute.

     

    To rule out network problem, you can create a blank report (but the best with a few parameters), and then you and your clients try to access this report. If this issue persists in the blank report, it means that the issue is a network problem. Please check your network, or contact the user who has this issue to check his/her network.

     

    If there is anything unclear, please feel free to ask.

     

    Thanks

    Albert Ye

    • Marked as answer by Tony Chain Monday, February 21, 2011 2:19 AM
    Wednesday, February 16, 2011 10:52 AM

All replies

  • Looks like a network problem between the client machine and the server... are the machines in the same geographical location?  
    Cheers,
    Jason
    P.S. : Please click the 'Mark as Answer' button if a post solves your problem! :)

    Some Random Thoughts

    Friday, February 11, 2011 5:27 PM
  • Yes they are. I heard from another user who said it's working fine on his machine. Not sure how much it is on his work station.
    Friday, February 11, 2011 7:13 PM
  • Any other thoughts?
    Friday, February 11, 2011 9:10 PM
  • Hi,

    Do your parameters have default values, which aren't retrieved from a dataset, but specified using VB.net?


    Remember to mark as an answer if this post has helped you.
    Friday, February 11, 2011 9:49 PM
  • No, all the parameters are using data sets..
    Saturday, February 12, 2011 12:33 AM
  • Hi,

     

    Base on your description, this issue could be caused by dataset or network. To rule out dataset problem, you can create a same report which has no dataset for parameters default and available values (you can copy and modify the report), and then you and your clients can try to access this report. If this issue persists in the new report, it means that the problem is that report or network. Otherwise, please drop the datasets one by one to find out which one needs more time than others to execute.

     

    To rule out network problem, you can create a blank report (but the best with a few parameters), and then you and your clients try to access this report. If this issue persists in the blank report, it means that the issue is a network problem. Please check your network, or contact the user who has this issue to check his/her network.

     

    If there is anything unclear, please feel free to ask.

     

    Thanks

    Albert Ye

    • Marked as answer by Tony Chain Monday, February 21, 2011 2:19 AM
    Wednesday, February 16, 2011 10:52 AM