Example: CURRENT_TIMESTAMP and the TimeDateWZControl Flag - Analytics Database - Teradata Vantage

SQL Functions, Expressions, and Predicates

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2024-01-12
dita:mapPath
obm1628111499646.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
kby1472250656485
lifecycle
latest
Product Category
Teradata Vantage™

This example shows the effect of the DBS Control flag TimeDateWZControl on the results returned by CURRENT_TIMESTAMP when the function is specified without an AT clause or with an AT LOCAL clause.

Assume the following:
  • The time local to Vantage is 11:59:00 Coordinated Universal Time (UTC), January 31, 2010.
  • User TK lives in Tokyo, and has a time zone defined as +9 hours offset from UTC.
  • User LA lives in Los Angeles, and has a time zone defined as -8 hours offset from UTC.
  • User TK and User LA run the CURRENT_TIMESTAMP function at exactly the same time.

If the TimeDateWZControl flag is enabled:

For User TK, the CURRENT_TIMESTAMP function returns:

2010-01-31 20:59:00.000000+09:00

For User LA, the CURRENT_TIMESTAMP function returns:

2010-01-31 03:59:00.000000-08:00


If the TimeDateWZControl flag is disabled:

For User TK, the CURRENT_TIMESTAMP function returns:

2010-01-31 11:59:00.000000+09:00

For User LA, the CURRENT_TIMESTAMP function returns:

2010-01-31 11:59:00.000000-08:00