# ODBC connector, multiple msg(SQL) from For cycle

**URL:** <https://discourse.nodered.org/t/odbc-connector-multiple-msg-sql-from-for-cycle/82080>\
**Category:** Jobs\
**Tags:** database\
**Created:** [16 October 2023 11:06 UTC](https://discourse.nodered.org/t/odbc-connector-multiple-msg-sql-from-for-cycle/82080 "2023-10-16T11:06:23Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [16 October 2023 13:41 UTC](https://discourse.nodered.org/t/odbc-connector-multiple-msg-sql-from-for-cycle/82080/13 "2023-10-16T13:41:32Z")

</div>

knowing nothing about the node forward makes it hard to help further.

You can use rate limit as a queue. To make it more efficient once your sql node responds you can feed msg.flush set to 1 back to the delay node to release next. Read help text for delay node, both Colin and me have posted example flows for this in the past.  
here is one

> [@Problem with TCP requests](https://discourse.nodered.org/t/problem-with-tcp-requests/81538/9):
>
> Will queuing the inputs and only allowing new input once tcp responds work [{"id":"7f219818a234a3c6","type":"inject","z":"d1395164b4eec73e","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"eeeeee","payloadType":"str","x":510,"y":520,"wires":[["3b447fd41df4372d"]]},{"id":"3b447fd41df4372d","type":"function","z":"d1395164b4eec73e","name":"add \"\\r\\n\"","func":"msg.payload = msg.payload + '\\r\\n';\nreturn ms…

> [@How to process any messaging queues synchronously in node-red](https://discourse.nodered.org/t/how-to-process-any-messaging-queues-synchronously-in-node-red/71805/7):
>
> If you mean that you have a section of flow and you want to wait till one message has completely passed through that section before the next one is allowed through then have a look at this example of how to do it. Set the time in the Queue node to a greater time than your flow should ever take to run through. If something locks up then it will release the next message after that time in order to let things keep going. [{"id":"b6630ded2db7d680","type":"inject","z":"bdd7be38.d3b55","n…

---

_[View the full topic](https://discourse.nodered.org/t/odbc-connector-multiple-msg-sql-from-for-cycle/82080)._