We have some spreadsheets that are about 18 MB in size that are being converted to csv. One sheet that is 52 columns, 61,407 rows just took 54 minutes to export to a pipe-delimited file.
Any configuration tips as I can't believe this is normal? Maybe network settings somehow? It is writing to a UNC folder set up in a job variable in case that info helps.
Is anyone else experiencing long convert times as well? Did you come up with an alternative?
Thank you

Can you compare with saving it locally?

---

Version 8.2.4 by the way.
I copied the spreadsheet to C:\temp on the VisualCron server, edited the task's folder to be C:\temp. The filename is not a regex and it took 53 minutes.

Note: when I open the sheet manually using Excel 2010, a security warning appears stating data connections have been disabled. If I click the button to "enable content" I get a dialog asking me if I want to make this a trusted document. The files still export though eventually, and if I manually edit one down to 60 rows it converts in a flash.

Thanks for your quick attention by the way!
Gary

53 minutes for about 60000 rows today 😞

FYI - As an experiment, tested using a get cell task followed by a write file task on a 60442 row spreadsheet: 57 minutes. :-(
I set up a job in our trial version of AutoMate to do the same thing for grins and it took 18 minutes for the same file. AutoMate seemed to open an instance of Excel as a temp or working copy of the spreadsheet was opened in the folder while it ran.

Right, we are not dependnt on Excel. We probably do more checks and have more features which comes at the cost of speed.

---