# MSSQLSERVER is taking up too much memory

**URL:** <https://forum.inductiveautomation.com/t/mssqlserver-is-taking-up-too-much-memory/91787>\
**Category:** Ignition\
**Created:** [June 12, 2024, 10:52pm UTC](https://forum.inductiveautomation.com/t/mssqlserver-is-taking-up-too-much-memory/91787 "2024-06-12T22:52:57Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [June 13, 2024, 5:13pm UTC](https://forum.inductiveautomation.com/t/mssqlserver-is-taking-up-too-much-memory/91787/8 "2024-06-13T17:13:42Z")

</div>

> [@Tien-Phuc\_Huynh](#):
>
> s taking separate data line for each tag instead of 1 set of data per the time specified?

Yes, that's how the historian works. If you want to record unconditionally a bunch of tags, the SQL Bridge's wide tables are more space-efficient, and keep the samples together in database rows.

Some related reading:

> [@Which approach to follow - Tag Historian /Transaction Groups/Tag Event Script and Query Tag/Named Query](https://forum.inductiveautomation.com/t/which-approach-to-follow-tag-historian-transaction-groups-tag-event-script-and-query-tag-named-query/54535):
>
> Can someone provide guidelines to decide which approach to follow in which case?

(Follow the nested links.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/mssqlserver-is-taking-up-too-much-memory/91787)._