<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: What timezone is the “timestamp” value on a table's history? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/what-timezone-is-the-timestamp-value-on-a-table-s-history/m-p/162808#M55086</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/210475"&gt;@yit337&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;TIMESTAMP values are internally normalized and persisted in UTC, but they are displayed using the &lt;STRONG&gt;current session’s local timezone&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Therefore, it is not based on the timezone of the person who originally performed the write. It depends on the timezone configured for the SQL or Spark session that reads the history.&lt;/P&gt;&lt;P&gt;The Databricks SQL system default is UTC, so it will normally display as UTC unless the session or SQL warehouse timezone has been changed.&lt;/P&gt;&lt;P&gt;You can verify the active timezone with:&lt;/P&gt;&lt;PRE&gt;SELECT current_timezone();&lt;/PRE&gt;&lt;P&gt;And force consistent UTC output with:&lt;/P&gt;&lt;PRE&gt;SET TIME ZONE 'UTC';
DESCRIBE HISTORY catalog.schema.table_name;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jul 2026 13:39:48 GMT</pubDate>
    <dc:creator>szymon_dybczak</dc:creator>
    <dc:date>2026-07-13T13:39:48Z</dc:date>
    <item>
      <title>What timezone is the “timestamp” value on a table's history?</title>
      <link>https://community.databricks.com/t5/data-engineering/what-timezone-is-the-timestamp-value-on-a-table-s-history/m-p/162803#M55085</link>
      <description>&lt;P&gt;Is it UTC, or the local zone of whoever accesses it?&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2026 13:13:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/what-timezone-is-the-timestamp-value-on-a-table-s-history/m-p/162803#M55085</guid>
      <dc:creator>yit337</dc:creator>
      <dc:date>2026-07-13T13:13:15Z</dc:date>
    </item>
    <item>
      <title>Re: What timezone is the “timestamp” value on a table's history?</title>
      <link>https://community.databricks.com/t5/data-engineering/what-timezone-is-the-timestamp-value-on-a-table-s-history/m-p/162808#M55086</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/210475"&gt;@yit337&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;TIMESTAMP values are internally normalized and persisted in UTC, but they are displayed using the &lt;STRONG&gt;current session’s local timezone&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;Therefore, it is not based on the timezone of the person who originally performed the write. It depends on the timezone configured for the SQL or Spark session that reads the history.&lt;/P&gt;&lt;P&gt;The Databricks SQL system default is UTC, so it will normally display as UTC unless the session or SQL warehouse timezone has been changed.&lt;/P&gt;&lt;P&gt;You can verify the active timezone with:&lt;/P&gt;&lt;PRE&gt;SELECT current_timezone();&lt;/PRE&gt;&lt;P&gt;And force consistent UTC output with:&lt;/P&gt;&lt;PRE&gt;SET TIME ZONE 'UTC';
DESCRIBE HISTORY catalog.schema.table_name;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2026 13:39:48 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/what-timezone-is-the-timestamp-value-on-a-table-s-history/m-p/162808#M55086</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2026-07-13T13:39:48Z</dc:date>
    </item>
  </channel>
</rss>

