# Using Stored Procedure in Ignition Report

**URL:** <https://forum.inductiveautomation.com/t/using-stored-procedure-in-ignition-report/63084>\
**Category:** Ignition\
**Created:** [August 17, 2022, 12:59am UTC](https://forum.inductiveautomation.com/t/using-stored-procedure-in-ignition-report/63084 "2022-08-17T00:59:09Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 17, 2022, 3:02pm UTC](https://forum.inductiveautomation.com/t/using-stored-procedure-in-ignition-report/63084/3 "2022-08-17T15:02:47Z")

</div>

> [@eden](#):
>
> I’ve also noticed that the stored procedure runs fast in SQL Server Management Studio (SSMS) is is slow to load in the report. Has anyone encountered this?

> [@Slow Query in Ignition](https://forum.inductiveautomation.com/t/slow-query-in-ignition/55908/3):
>
> Found it - try SET ARITHABORT ON before executing the query:

---

_[View the full topic](https://forum.inductiveautomation.com/t/using-stored-procedure-in-ignition-report/63084)._