# oracle connector with db looping

**URL:** <https://forum.knime.com/t/oracle-connector-with-db-looping/77227>\
**Category:** KNIME Analytics Platform\
**Tags:** database, big-data\
**Created:** [February 13, 2024, 8:19pm UTC](https://forum.knime.com/t/oracle-connector-with-db-looping/77227 "2024-02-13T20:19:35Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ipazin](https://forum-cdn.knime.com/user_avatar/forum.knime.com/ipazin/32/806_2.png) [@ipazin](https://forum.knime.com/u/ipazin)\
**Post date:** [February 14, 2024, 7:45am UTC](https://forum.knime.com/t/oracle-connector-with-db-looping/77227/2 "2024-02-14T07:45:10Z")

</div>

Hello @likhangy,

according to this topic this is expected to be slow in certain cases:

> [@DB Looping Node](https://forum.knime.com/t/db-looping-node/46525):
>
> I have just tried using the new DB Looping Node. I am finding that it suffers the same limitations as legacy approaches; namely that it cannot accept a large list for the IN statement. Therefore a loop of several (or many times) over the database is still necessary, which is of course very slow. Am I missing something? Can a large list be used and loop over the database only once?

You can always read data into KNIME (460k is rather small table) and then use Reference Row Filter node to filter it. Should be much faster.

Br,  
Ivan

---

_[View the full topic](https://forum.knime.com/t/oracle-connector-with-db-looping/77227)._