# Timestamps in Tag Historian vs Transaction Groups working differently in reports

**URL:** <https://forum.inductiveautomation.com/t/timestamps-in-tag-historian-vs-transaction-groups-working-differently-in-reports/69422>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 3, 2023, 5:57pm UTC](https://forum.inductiveautomation.com/t/timestamps-in-tag-historian-vs-transaction-groups-working-differently-in-reports/69422 "2023-02-03T17:57:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![CBandurski](https://avatars.discourse-cdn.com/v4/letter/c/898d66/32.png) [@CBandurski](https://forum.inductiveautomation.com/u/CBandurski)\
**Post date:** [February 3, 2023, 5:57pm UTC](https://forum.inductiveautomation.com/t/timestamps-in-tag-historian-vs-transaction-groups-working-differently-in-reports/69422/1 "2023-02-03T17:57:27Z")

</div>

I've successfully created reports using a Tag Historian Query. I'm now trying to create a report using an SQL query. The problem I'm running into is that the t\_stamp column is an integer in historical tables, but text in transaction group tables. The former is able to be formatted as a date in the reporting module while the latter just displays the unix time as a string. Now, I can format the date as desired in my SQL query, but I'd really like to make that adjustment at the cell level in the report. I've tried casting t\_stamp to a double but no dice. I'm guessing the Tag Historian Query data source in reports is doing something in the background to convert the column to a date.

Am I missing something obvious here?

---

<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 3, 2023, 9:45pm UTC](https://forum.inductiveautomation.com/t/timestamps-in-tag-historian-vs-transaction-groups-working-differently-in-reports/69422/2 "2023-02-03T21:45:15Z")

</div>

The historian's `t_stamp` column is milliseconds UTC. Most databases have conversion functions. (There's too much variability in branded databases' support for precision timestamps that handle timezoned data correctly. Looking at you, Microsoft.)