You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per recommendation, we have created the data pump daemon user with a GMT timezone. However, The date-time timezone in MSSQL tables is GMT and our service now is local time zone 'Asia/Singapore'.
We would like to standardize on local timezone, is it possible for data pump to copy the date time data in local timezone from SN than in GMT?
Looking at documentation of timezone in datapump, there does not seem to be an option like
set time_zone = 'US/Eastern'; in MSSQL.
Please advise
The text was updated successfully, but these errors were encountered:
Just to clarify, ServiceNow always stores date/time values in GMT, regardless of the configured system time zone. The REST API always returns date/time values in GMT. It sounds like you are requesting that SNDML use the database local timezone (instead of GMT) when writing date/time values to the database.
I did a bit of investigation. GMT is currently hard-coded. You will see it if you look at the file main/java/sndml/datamart/DatabaseStatement.java line 32. It should be possible to make the code more flexible by switching to a soft-coded time zone that could be changed via a property in the connection profile.
Unfortunately, I am not currently able to test this change. I will need to spin up an MSSQL database. I will put this on the list of enhancements for the next release.
As per recommendation, we have created the data pump daemon user with a GMT timezone. However, The date-time timezone in MSSQL tables is GMT and our service now is local time zone 'Asia/Singapore'.
We would like to standardize on local timezone, is it possible for data pump to copy the date time data in local timezone from SN than in GMT?
Looking at documentation of timezone in datapump, there does not seem to be an option like
set time_zone = 'US/Eastern'; in MSSQL.
Please advise
The text was updated successfully, but these errors were encountered: