June 11, 2013 at 12:15 pm
I have a report that ran fine prior to upgrade to sql 2008 R2 SP1.
It has 3 parameters.
1. to select people,
2. to select date.
3. is default(run date)
when we run this report for one person, it works fine. But when we run it for "all" people, it times out.
it basically runs a stored procedure in the back, xxx ,' all', 'date', Default
If I run the stored proc, it takes 47 seconds to get all results.
So something changed in the R2/SP1 that messed this up.
We have no answers .....
Can anybody help?
Warmest Regards
Paresh Motiwala
Boston
Paresh Motiwala Manager of Data Team, Big Data Enthusiast, ex DBA
June 11, 2013 at 1:33 pm
Paresh Motiwala (6/11/2013)
I have a report that ran fine prior to upgrade to sql 2008 R2 SP1.It has 3 parameters.
1. to select people,
2. to select date.
3. is default(run date)
when we run this report for one person, it works fine. But when we run it for "all" people, it times out.
it basically runs a stored procedure in the back, xxx ,' all', 'date', Default
If I run the stored proc, it takes 47 seconds to get all results.
So something changed in the R2/SP1 that messed this up.
We have no answers .....
Can anybody help?
Warmest Regards
Paresh Motiwala
Boston
There is pretty much nothing anybody can do to help based on the lack of any details. It seems you have some sort of performance issue with your query. Please see this article on how to post performance problems.
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
June 11, 2013 at 1:51 pm
Hi Sean
Thanks for your response.
But the query runs fine in 47 seconds.
It just doesn't run in SSRS or Report Builder.
It used to work before.
So if you can help, please let me know what info are you looking for?
Paresh Motiwala Manager of Data Team, Big Data Enthusiast, ex DBA
June 11, 2013 at 2:02 pm
Paresh Motiwala (6/11/2013)
Hi SeanThanks for your response.
But the query runs fine in 47 seconds.
It just doesn't run in SSRS or Report Builder.
It used to work before.
So if you can help, please let me know what info are you looking for?
Unless your tables are really large (millions and millions of rows) I would say that 47 seconds is not running "fine". 🙂
Not to sound snippy but just saying that a query used to work but doesn't know does not provide information. That is like taking your car to the shop and telling them the car used to run but now it doesn't, what could be wrong.
As outlined in the article I suggested, let's start with the execution plan. The actual plan, not the estimated one.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
June 13, 2013 at 7:08 am
Hi Sean
So let's say you are the mechanic.
What questions would you want me to answer.
For the user 47 seconds is ok. so even if the page returns the results in 2 minutes, I and the users don't care.
It is indeed an extremely complex query, that returns 240 rows.
There is nothing on CPU, memory consumption is low.
It is just the time it takes to render.
and then after a while it returns with the time out errors.
couple of years ago, we had a similar issue with some reports when we switched to SQL 2008R2 and then to SQL 2012.
a report that normally ran for 5 seconds took 155 seconds.
Microsoft worked on it for 3 months. Came back with the solution, rewrite all our 2500 reports.
It is only later they understood that in these versions the report rendering doesn't happen at the SQL Server level but at the client's browser level.
So we installed a Google Chrome Browser, the report came back in 55 seconds.(as against 5). Still the users were not happy.
Microsoft refunded all our consulting hours/fees.
Paresh Motiwala Manager of Data Team, Big Data Enthusiast, ex DBA
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply