June 24, 2010 at 2:55 am
I have an end user who runs a stock report. The report returns 10000 lines. When he atempts to export to excel his machine hangs (not responding) then eventually crashes. His PC is a fairly decent spec.
I have tested on my 64 bit machine (8GB RAM). I initially get the not responding but after 3 minutes the excel file renders OK.
I do not want to purchase new hardware if it will not resolve the issue.
What is happening under the covers when export to excel is selected? Is ther anything I can do on the server running reporting services?
Thanks,
Phil.
-------------------------------------------------------------------------------------
A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge."
Two hydrogen atoms walk into a bar. One says, 'I think I've lost an electron.' The other says 'Are you sure?' The first says, 'Yes, I'm positive... '
Tommy Cooper
June 24, 2010 at 6:58 am
Phil, I have a couple of thoughts on this. The first one is, does your user actually need to see all 10k lines, or does he then aggregate it further? Can you do the aggregations for him in the report to make the rendering process less intensive for his machine?
Secondly, that's a lot of data, so it may be that it's just taking much longer to transfer and render the data to his machine as opposed to yours. IT could be a network thing, perhaps your machine is on the same network segment as your server and his is not, perhaps the same switch as the server or even his might be plugged into an old 10/100 switch and yours is in a gigabit port. Remember the more hops (through switches/routers etc) a data packet takes the more latency you get. When you are transferring that much data the network, the network architecture really comes into play.
Third, how close to real time does he need the report? Can you setup a subscription that generates it on a schedule and either email's it to him (if the file is small enough) or drops it on a network drive? That way the server does the work and not his desktop. I can't imagine he'd need all 10,000 rows and then it not take so much time to evaluate those rows that the data would be old by the time he gets it if he's looking to use this for real time trading. Perhaps a more refined report with additional parameters to cut down the size of the data is in order?
Here's a link to rendering reports as excel spreadsheets from SSRS. It may provide some additional thoughts/information. http://msdn.microsoft.com/en-us/library/ms159836.aspx
-Luke.
June 24, 2010 at 8:54 am
Hi Luke, some good points. I think scheduling is the best option. His machine hangs off a 8 port GB switch (shared) that patches into a single floor port that patches into a GB switch in the comms room.
Thanks,
Phil.
-------------------------------------------------------------------------------------
A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge."
Two hydrogen atoms walk into a bar. One says, 'I think I've lost an electron.' The other says 'Are you sure?' The first says, 'Yes, I'm positive... '
Tommy Cooper
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply