# Data exchange via local SQL DB table

**URL:** <https://forum.inductiveautomation.com/t/data-exchange-via-local-sql-db-table/35621>\
**Category:** Ignition\
**Created:** [June 13, 2020, 6:32am UTC](https://forum.inductiveautomation.com/t/data-exchange-via-local-sql-db-table/35621 "2020-06-13T06:32:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [June 14, 2020, 10:18pm UTC](https://forum.inductiveautomation.com/t/data-exchange-via-local-sql-db-table/35621/4 "2020-06-14T22:18:53Z")

</div>

Normally, I'd say the buffer cache should be sufficient for this operation. However, you'll need to balance SQL Server memory requirements to Ignition's.

> [@System Slowing down over a period](http://forum.inductiveautomation.com/t/system-slowing-down-over-a-period/35238/4):
>
> +1 on what Phil said. The database should be on a separate host. In the meantime, check the memory allocation to SQL server. and set it to something reasonable. By default, it will use all the memory it can. This article can give some handy calculations.

---

_[View the full topic](https://forum.inductiveautomation.com/t/data-exchange-via-local-sql-db-table/35621)._