# SQL historian best practice - cost threshold for parallelism

**URL:** <https://forum.inductiveautomation.com/t/sql-historian-best-practice-cost-threshold-for-parallelism/108451>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [July 14, 2025, 10:28pm UTC](https://forum.inductiveautomation.com/t/sql-historian-best-practice-cost-threshold-for-parallelism/108451 "2025-07-14T22:28:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![SWoollett](https://avatars.discourse-cdn.com/v4/letter/s/a9a28c/32.png) [@SWoollett](https://forum.inductiveautomation.com/u/SWoollett)\
**Post date:** [July 14, 2025, 10:28pm UTC](https://forum.inductiveautomation.com/t/sql-historian-best-practice-cost-threshold-for-parallelism/108451/1 "2025-07-14T22:28:52Z")

</div>

Are there any recommendations on what to set the cost threshold for parallelism to on MSSQL server when using it as a historian for Ignition?

Most reading I've done recommends increasing it to improve performance. So I'm curious what have people found to be a suitable cost threshold for Ignition historians?

Cheers