August 19, 2008 at 1:12 am
Hello gyus!
is there some way to export the output of report to excel 2007?
i am using reporting services in SQL Server 2008
Thanks in advance!
August 19, 2008 at 8:32 am
I'm using SQL2005 with Excel 2007 and the standard export feature to Excel works perfectly, can't imagine SQL2008 would have any problem there. What problems do you have?
Nigel West
UK
August 19, 2008 at 9:59 pm
Well, i have used both Sql Server 2005 and 2008 and by default, they export to excel 2003. If report has data more than 65535 rows, it gives error and doesnt export successfully.
August 21, 2008 at 9:11 am
You can work around the limitation in Excel 2003 by breaking up the report into multiple tabs. On the table properties, go to the Groups tab and add a new group.
In the Group on area enter: =Int((RowNumber(Nothing)-1)/60000)
and check the Page Break at End box.
You'll get one tab for each 60,000 rows. If you want to change the number of rows per tab, just change the number in the divisor.
Mike Hayes
August 21, 2008 at 10:45 pm
woww!
great!
that's a good and easy to implement work around!
September 2, 2008 at 7:12 pm
What is the standard export feature to Excel? 🙁
September 3, 2008 at 1:13 am
hey what do you mean by standard export feature. its normal export format when excel export is excel 2003!!!
what else do you want to know???
November 28, 2008 at 3:32 am
Mike Hayes (8/21/2008)
You can work around the limitation in Excel 2003 by breaking up the report into multiple tabs. On the table properties, go to the Groups tab and add a new group.In the Group on area enter: =Int((RowNumber(Nothing)-1)/60000)
and check the Page Break at End box.
You'll get one tab for each 60,000 rows. If you want to change the number of rows per tab, just change the number in the divisor.
Mike Hayes
I changed my report as how do you said but it's not working on export to excel! How I can see whether the report is breaking and the break parts are exporting to excel?
November 28, 2008 at 6:33 am
When you say it's not working, what's not working? It doesn't work at all? Do you get an error? What?
Mike Hayes
November 28, 2008 at 7:12 am
Exception of type System.OutOfMemoryException was thrown.
Version Information: Microsoft .NET Framework Version:1.1.4322.2407; ASP.NET Version:1.1.4322.2407
November 28, 2008 at 7:51 am
How it is the report splitted? Where it shows the tabs? The report is exported to excel already splitted? or how....?
December 1, 2008 at 9:07 am
It sounds like the Excel export is using all of the available memory. This would be happening on the server side. How many rows are you attempting to export? What kind of data? How much data per row? If you're trying to export 1/2 million rows of large textual data to Excel or if there's lots of formatting, then I could see you getting something like this. I don't have a good solution for you. Sorry.
Mike Hayes
December 2, 2008 at 1:05 am
ok, thanks! I have a lot of memory on RS server. The report throws only 80,000 rows. So, it shouldn't be a problem with your solution. But, it didn't work! Anyway, I ran the stored procedure of the report on database server level.
December 3, 2008 at 6:49 am
That's an error indicating the server did not have enough memory to render the report to Excel and not an issue with the version. I've seen this quite a bit on large reports and Excel is the worst when it comes to rendering. The issue has been resolved in SQL Server 2008 but in the meantime, you may want to try a CSV download and then import that into Excel.
December 3, 2008 at 6:59 am
I just expected that it should be built a new rendering engine for Excel 2007, maybe in RS 2005. This isn't a solution to tell to a bussiness-like people to export the report as CSV file and from there to Excel. Those people like the problem to be easiest and simplest.
Viewing 15 posts - 1 through 15 (of 28 total)
You must be logged in to reply to this topic. Login to reply