# Microsoft SQL Server DATETIMEOFFSET

**URL:** <https://forum.inductiveautomation.com/t/microsoft-sql-server-datetimeoffset/29761>\
**Category:** Ignition\
**Created:** [November 7, 2019, 5:50pm UTC](https://forum.inductiveautomation.com/t/microsoft-sql-server-datetimeoffset/29761 "2019-11-07T17:50:11Z")\
**Posts on this page:** 1\
**Showing post:** 27

<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:** [February 13, 2024, 8:06pm UTC](https://forum.inductiveautomation.com/t/microsoft-sql-server-datetimeoffset/29761/27 "2024-02-13T20:06:41Z")

</div>

> [@Zach\_Larson](#):
>
> correct way is changing Ignitions translators datatype Datetime to a Datetime2.

That is a convenience that causes Ignition's table-creation helpers to use those column types. The critical change is to the table--change the column type.

Yes, it can be a big deal for a system in production. It is best to get the column types correct up front. (For a corporation that has facilities spanning multiple time zones, the plain MS SQL Server `datetime` column type is a terrible design choice. Your client's DB admins should be chastized.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/microsoft-sql-server-datetimeoffset/29761)._