[CLOSED] Excel corrupted when ROWLIMIT IS SET TO 1000000
I had 30lakh records and trying to split 10lakh records into each sheet. I tried splitting the records using ROWLIMIT=1000000, It was generating a corrupted excel.This message has been edited. Last edited by: FP Mod Chuck,
December 19, 2019, 07:42 AM
MartinY
Excel still has its limits Not because you are splitting the result in 3 tabs of 1M records each that Excel will accept that.
The first question that I would ask myself is : why producing a report that contains 3M records ? For me it makes no sense
Maybe you are not using the proper approach
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
December 19, 2019, 08:24 AM
venkatesh emandi
It is a business requirements, And the data is for one year.
December 19, 2019, 09:06 AM
MartinY
quote:
Originally posted by venkatesh emandi: It is a business requirements, And the data is for one year.
You must get more information (or provide us with more info) regarding the goal behind this :
- What is the purpose of having one year of detailed data where over 3M rows are extracted and included in an Excel file ? - What they want to do with that ? - Can you provide something different then their requirement to better answer their needs ?
Nobody can work with that number of data as a BI POV. This looks more like a data dump and sure that Excel is probably not the good platform to dump in. It also looks like we are missing a lot of information...
Please update your signature to let us know which WF version you are working with. That may help us helping you in future.
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
December 19, 2019, 02:46 PM
BabakNYC
I've never attempted to do this, so I can't tell if it should or shouldn't work but like MartinY says, you've probably hit a limitation.
Test 1: Dump this data into a CSV and see if Excel can open that CSV file. That'll give you an idea if in fact Excel is choking on the size of your output.
Test 2: Try running the request on the reporting server (with ON TABLE HOLD FORMAT XLSX) to see if it still corrupts the excel file. That eliminates the WebFOCUS client and any client memory limitations as a potential issue.
Ultimately, if your requirements aren't flexible, the only thing left is to open a case with IB tech support to get their official response. But I'm pretty sure tech support will ask you to try these two tests so you may want to have this information before you call them as they help narrow down where the issue is.