SQL Server 2016的“在时区”功能无法按预期工作

Question

I'm using SQL Server 2016 at Amazon AWS. My emails are being sent with incorrect times when sent from my pupper at Amazon. When I try to recreate this bug locally the times are correct. Here is an example of how I use at time zone .

getDate() at time zone 'utc' at time zone u.timezone

where u.timezone is the user's timezone and u refers to an aliased table users .

The times being outputted are at UTC time, so I see 7:36pm instead of 2:36pm (they are formatted with MomentJS)

I don't really know where to start with this one, sorry guys and gals.

UPDATE

My server is sending the correct time (with the correct timezone offset) to the email factory. When the server creates the emails, times are formatted using MomentJS. The barebones moment() function will take a time with a timezone offset (-5:00) and adjust it to the local machine's local time. Local time on my machine is EST, but in Amazon (where the email is being created) is not. Thus I must use moment.parseZone() .

From the MomentJS docs :

If your date format has a fixed timezone offset, use moment.parseZone:
moment.parseZone("2013-01-01T00:00:00-13:00");
This results in a date with a fixed offset:
"2013-01-01T00:00:00-13:00"

Since I can't see this change until it is pushed onto our dev environment, I won't be able to know if this fixed it, but I think this was the problem.

Answer 1

My server was sending the correct time (with the correct timezone offset) to the email factory. When the server created the emails, times were formatted using MomentJS.

The barebones moment() function takes a time with a timezone offset (-5:00) and adjusts it to the local machine's local time.

Local time on my machine is EST, but in Amazon (where the email is being created) is not. Thus I must use moment.parseZone() .

Changing to moment.parseZone() fixed this issue. Problem solved.