- Newest
- Most votes
- Most comments
Hi,
According to https://repost.aws/knowledge-center/rds-change-time-zone
It’s a best practice to use the UTC time zone at the database layer. Because UTC doesn't observe daylight savings (DST), you don’t have to adjust the time later when it shifts.
Hope it helps and if it does I would appreciate the answer to be accepted so that community can benefit for clarity, thanks ;)
Hi all,
We've moved our on-premise application to AWS and all default date time stamps for table columns and stored procedures are based on GETDATE() we NEED the DB instance to observe daylight savings as it is now causing us a massive headache.
All our clients are UK based, it is completely impractical and nigh-on impossible for us to modify our entire db or client codebase to handle DST in-code especially as it was previously just handled by the underlying OS that we installed the MSSQL instance to when our solution was deployed on-premise.
Is there a workaround to make the RDS instance observe DST? It doesn't look like it according to the timezone settings documentaion, non of the "local" timezones observe DST, which kind of negates the point of having local timezones IMHO....
Many thanks, Dean
Relevant content
- asked 16 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago