# Stored Procedure call overhead-way to batch? **URL:** \ **Category:** Ignition\ **Created:** [September 30, 2024, 8:12pm UTC](https://forum.inductiveautomation.com/t/stored-procedure-call-overhead-way-to-batch/96630 "2024-09-30T20:12:38Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 30, 2024, 9:19pm UTC](https://forum.inductiveautomation.com/t/stored-procedure-call-overhead-way-to-batch/96630/3 "2024-09-30T21:19:32Z")
Consider nesting that stored procedure inside a new stored procedure that accepts array parameters. It would call the original SP for each, and assemble the result from each into a row of a response dataset. One call to process many operations. You'll need a competent database (with UNNEST or equivalent support): > [@Taking a Dataset and Inserting it to a SQL temp table](https://forum.inductiveautomation.com/t/taking-a-dataset-and-inserting-it-to-a-sql-temp-table/83852/4): > > If you were using a competent database (the following is PostgreSQL), you can pass java arrays as arguments, and unnest() them in a FROM clause. For an example, I created a table in my psql forum playground called phrases, to be used in a join. When queried by itself, you get this dataset: "#NAMES" "prefix","suffix" "#TYPES" "str","I" "#ROWS","4" "Hello","1" "Good Bye","2" "Welcome to","3" "Whoa!","4" To go with that, in a custom property named lookups, I created the following unbound datase… --- _[View the full topic](https://forum.inductiveautomation.com/t/stored-procedure-call-overhead-way-to-batch/96630)._