Cannot export reports over a few hundred rows

**mipapage** · 2008-03-31, 09:36 PM

We have an issue where we cannot export more than a few hundred rows in the reports module.

It's more or less a resource error, that is, either not enough memory (I've tried up to 768M for PHP) or not enough execution time (I'm at 60 seconds right now).

The latest error is:
Fatal error: Maximum execution time of 60 seconds exceeded in /path/to/sugar/include/utils/array_utils.php on line 48

This error spat out a huge array to the screen.

We could push on adding memory and time, but why on earth does the report work to html but not to CSV?

Is there anything we can do to improve this? Is there a 3rd party reporting extension that we can use if this is unfixable?

**BrianSteffens** · 2008-03-31, 10:15 PM

You could increase your php timeout, but it will still perform slowly, it would just -eventually- finish. Have you tried exporting different kinds of data with different fields and different filters?

There are external programs that do things like that, provided your administrators don't mind you connecting directly to the live database (scary scary). I'd prefer not to recommend one because I don't have enough experience with any of them to stand by the fact that it works and doesn't mess anything up.

**mipapage** · 2008-04-01, 08:18 AM

Hey BrianSteffens,

Thanks for the reply. We have increased our PHP timeout to one minute from 30 seconds, which should be more then enough for a paltry 2000 row csv export. The report itself runs, its the export that dies. This is what I don't get; it can obviously fetch the rows and format them to HTML, why not to csv? There has to be a bug in there somewhere but I have no idea where and would love to hear from others on this.

At the moment we are simply showing the query and then running that in Navicat where we can export straight to Excel.

**BrianSteffens** · 2008-04-01, 04:15 PM

I think the CSV handling code in Sugar is very poorly optimized, for import as well. We were having timeouts at 5 minutes importing 4000 contacts at a time on a nice machine. I eventually wrote a script to read the files and do the insert statements manually, which worked fine.

**mipapage** · 2008-04-01, 08:46 PM

Originally Posted by BrianSteffens

I think the CSV handling code in Sugar is very poorly optimized, for import as well. We were having timeouts at 5 minutes importing 4000 contacts at a time on a nice machine. I eventually wrote a script to read the files and do the insert statements manually, which worked fine.

Yeah, that's the trouble. We can do the navicat thing, but then management comes up with "The old CRM could DO this, why is this feature here but it doesn't work? What else doesn't work?" which is never fun.

Anyways, I'm pretty sure I filed a ticket for this a few days ago, hopefully it gets responded to shortly...