# Writing large csv files + memory issues

**URL:** <https://forum.knime.com/t/writing-large-csv-files-memory-issues/15060>\
**Category:** KNIME Analytics Platform\
**Created:** [May 3, 2019, 8:47am UTC](https://forum.knime.com/t/writing-large-csv-files-memory-issues/15060 "2019-05-03T08:47:07Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![mlauber71](https://forum-cdn.knime.com/user_avatar/forum.knime.com/mlauber71/32/73590_2.png) [@mlauber71](https://forum.knime.com/u/mlauber71)\
**Post date:** [May 10, 2019, 9:17am UTC](https://forum.knime.com/t/writing-large-csv-files-memory-issues/15060/6 "2019-05-10T09:17:44Z")

</div>

Could you try and write the data to CSV in loops? Only so much at a time and then append it to an existing CSV file. We had a similar discussion recently:

> [@Export huge MS sql table to csv without fetching all records together](https://forum.knime.com/t/export-huge-ms-sql-table-to-csv-without-fetching-all-records-together/15105/2):
>
> have you thought about doing it in chunks? And then appending the result to a CSV file. The example attached uses ROWIDs from SQLite. You could see if you either have a ROWIDs present or you could create one yourself. You can choose the size of the chunk/batch yourself (I use integers you might have to see if with very large numbers you might need big integers or something. Even a workaround with using strings might be possible). Only other idea would be to write a CSV file directly on a Big Da…

---

_[View the full topic](https://forum.knime.com/t/writing-large-csv-files-memory-issues/15060)._
