# Sqlt\_data\_x\_x\_x Table Keep Changing of Name Making Sql Querry Invalid

**URL:** <https://forum.inductiveautomation.com/t/sqlt-data-x-x-x-table-keep-changing-of-name-making-sql-querry-invalid/72975>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [April 27, 2023, 3:48pm UTC](https://forum.inductiveautomation.com/t/sqlt-data-x-x-x-table-keep-changing-of-name-making-sql-querry-invalid/72975 "2023-04-27T15:48:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Emile\_Laplante](https://avatars.discourse-cdn.com/v4/letter/e/c57346/32.png) [@Emile\_Laplante](https://forum.inductiveautomation.com/u/Emile_Laplante)\
**Post date:** [April 27, 2023, 3:48pm UTC](https://forum.inductiveautomation.com/t/sqlt-data-x-x-x-table-keep-changing-of-name-making-sql-querry-invalid/72975/1 "2023-04-27T15:48:55Z")

</div>

Hi,

I plot tag history on charts in vision. I use a sql querry to check if there is data in the data base to show or not the graph. There is the sql querry :

> SELECT COUNT(\*) as test  
> FROM sqlt\_data\_1\_2023\_04

But it seems that a new table is created with a new name at each month (sqlt\_data\_x\_x\_x), so the querry become invalid at every month.

So, is it possible to store the tag data always in the same table?

Thank you!

---

<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:** [April 27, 2023, 3:52pm UTC](https://forum.inductiveautomation.com/t/sqlt-data-x-x-x-table-keep-changing-of-name-making-sql-querry-invalid/72975/2 "2023-04-27T15:52:10Z")

</div>

Sure, disable partitioning on the DB history provider:  
[https://docs.inductiveautomation.com/display/DOC81/Tag+History+Providers#TagHistoryProviders-DatasourceHistoryProviders](https://docs.inductiveautomation.com/display/DOC81/Tag+History+Providers#TagHistoryProviders-DatasourceHistoryProviders)

This is likely to have adverse effects on your DB performance over time, as the table row count grows, unless you have a "smarter" DB that does transparent partitioning. Consider yourself warned.