# What SQL permissions and/or tables are required to use Tag Historian?

**URL:** <https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233>\
**Category:** Ignition\
**Tags:** ignition81, scripting, database\
**Created:** [August 1, 2023, 3:52pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233 "2023-08-01T15:52:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [August 1, 2023, 3:52pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233/1 "2023-08-01T15:52:09Z")

</div>

I am working on a locked down system that doesn't allow users to CREATE tables in Microsoft SQL database. Is there documentation that details what SQL tables are required to run Tag Historian? A cursory glance at the manual didn't show anything relevant.

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [August 1, 2023, 3:59pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233/2 "2023-08-01T15:59:33Z")

</div>

I think one problem you'll face if you don't allow the Ignition user to CREATE is what happens when a new table is required? Like my history tables look like  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/b/9bd5bc1c29ed6b0a20e8fc5ff2cce26b1e426970.png)

Unless someone manually wants to create it each time, I would really recommend they figure out a way to let Ignition user create tables. Maybe they'll want to create a fresh DB silo'd off from other important data and then feel comfortable granting CREATE privilege's, but I do think the easiest thing is to let Ignition manage this.

---

<div class="post-metadata">

**Author:** ![bmeyers](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmeyers/32/37453_2.png) [@bmeyers](https://forum.inductiveautomation.com/u/bmeyers)\
**Post date:** [August 1, 2023, 4:04pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233/3 "2023-08-01T16:04:03Z")

</div>

You bring up a good point I didn't think about. I will see if I can convince the team here to make a user with more privileges.

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [August 1, 2023, 4:08pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233/4 "2023-08-01T16:08:07Z")

</div>

I hope Ignition isn't using root haha.

---

<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 1, 2023, 4:14pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233/5 "2023-08-01T16:14:01Z")

</div>

If you turn off partitioning, then you wouldn't need a new partition table created periodically. You will then have the _other_ problem of an endlessly growing table to deal with, but 🤷‍♂️

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [August 1, 2023, 5:40pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233/6 "2023-08-01T17:40:07Z")

</div>

> [@paul-griffith](#):
>
> You will then have the _other_ problem of an endlessly growing table to deal with, but 🤷‍♂️

You evil, evil man... 😛  
From experience of starting with a monthly partition at sites, to a weekly partition, now down to 3 day partitions at some sites. I cannot even fathom not having the tables partitioned on the standard historian database buildout.

---

<div class="post-metadata">

**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:** [August 1, 2023, 5:48pm UTC](https://forum.inductiveautomation.com/t/what-sql-permissions-and-or-tables-are-required-to-use-tag-historian/77233/7 "2023-08-01T17:48:18Z")

</div>

> [@MMaynard](#):
>
> I cannot even fathom not having the tables partitioned

Common practice when the DB involved has decent native partitioning support.
