# DB Reader (legacy) limitations **URL:** \ **Category:** KNIME Extensions\ **Tags:** big-data-extension, big-data\ **Created:** [October 27, 2021, 6:06am UTC](https://forum.knime.com/t/db-reader-legacy-limitations/36974 "2021-10-27T06:06:43Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [October 27, 2021, 6:38am UTC](https://forum.knime.com/t/db-reader-legacy-limitations/36974/3 "2021-10-27T06:38:22Z")
@Alkaline as a workaround you could load the data in chunks of you have some sort of rowid. Maybe not the most elegant way. > [@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… > **[Export huge MS sql table to csv without fetching all records together –...](https://hub.knime.com/mlauber71/spaces/Public/forum/kn_example_huge_db_to_csv/m_001_write_csv_41~eeeQpO-YFJ5EPfco/current-state)** > > 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 th… --- _[View the full topic](https://forum.knime.com/t/db-reader-legacy-limitations/36974)._