Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Timeout expired in reporting services log Expand / Collapse
Author
Message
Posted Sunday, January 6, 2013 10:58 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 10:49 PM
Points: 90, Visits: 388
We are getting the Time out expired error message in reporting service log file while executing the one report which has huge data.Help me to resolve the issue.

Regards,
Ram
Post #1403341
Posted Sunday, January 6, 2013 11:21 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 7:35 AM
Points: 471, Visits: 874
Firstly, can you provide more information?
E.g. How long is the timeout, what is the query (provide SQL), how many rows, an example of the data and the purpose of the report - why is the data so huge?

Does your report really require huge data?

I have had situations where detailed reports are required for legally defensible reasons, but that is extremely rare. If you must have a lot of data on the report, you will have to break the report up into chapters and run them separately. You will find that this is not a reporting services issue per se, for example you will run into similar limitations with crystal reports.

One common issue that people have with reporting services is that they try to bring a huge dataset into the report and then use filters within the report. That is the wrong way to do it, you are better to filter the data in the SQL. Let the SQL engine do the work to optimise and minimise the required dataset.
Post #1403417
Posted Monday, January 7, 2013 3:25 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 10:49 PM
Points: 90, Visits: 388
Thanks for your reply. We have table that has 31 million records. Report service will commnunicate with database table and has to display the data.

We have storeprocedure to filter the data on datewise with timestamp . Some records has null timestamp and report is taking more thane 30 minutes to pull out the records for 1 day.

Regards,
Ram
Post #1403514
Posted Monday, January 7, 2013 3:11 PM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 7:35 AM
Points: 471, Visits: 874
31 million rows is large but not huge.

If the stored proc is taking 30 minutes to filter on the date then it sounds like you need to add an index to that table.
Post #1403889
Posted Wednesday, January 9, 2013 5:10 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 10:49 PM
Points: 90, Visits: 388
Thanks for your response. After creating the Indexes on column level now report generates with in 2 minutes.

Regards,
Ram
Post #1404700
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse