# Stored Procedure Question **URL:** \ **Category:** General Discussion\ **Tags:** ignition81, perspective\ **Created:** [April 2, 2024, 3:28pm UTC](https://forum.inductiveautomation.com/t/stored-procedure-question/88237 "2024-04-02T15:28:47Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\ **Post date:** [April 2, 2024, 5:03pm UTC](https://forum.inductiveautomation.com/t/stored-procedure-question/88237/5 "2024-04-02T17:03:47Z")
OK, so I found what I think is the issue... You need to add your DB's version of `SET NOCOUNT ON` (that's SQL Server syntax) in your procedure because if you don't , you'll return two datasets - the number of rows affected and then the data you're expecting. I found that [here](https://forum.inductiveautomation.com/t/sql-query-tag-issue/10345/3) and remembered that I myself have done this before... --- _[View the full topic](https://forum.inductiveautomation.com/t/stored-procedure-question/88237)._