August 27, 2008 at 7:50 am
I have some Excel VBA code which calls a stored procedure, gets back about 90,000 rows, then renders each row over two sheets in Excel.
This takes approximately one minute and is used a lot by my clients.
We are moving to Reporting Services (it's excellent). BUT, when I call the same stored procedure and Export to Excel it takes 10 or 15 minutes.
Is there a way to improve this please? Even if it means writing my own code and not using the default behaviour (basically, I'm desperate).
Thanks for any help,
Tom.
August 27, 2008 at 9:06 am
Are rendering the report on the web (intranet) first or going directly to excel?
How much formatting are you doing in the report?
I'm going to guess, not knowing the internals of how RS renders to Excel, that you aren't going to be able to do a whole lot to fix the performance. You have the request going to the Report Server on IIS, then hitting the RS web service and rendering across all those connections while Excel is directly hitting the DB. So you have added layers. I'd start by making sure the report itself is as vanilla as possible, and if that makes a big impact, even have separate reports, one to render to the web and one to render directly to Excel.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply