Timeline for answer to How to handle TimeZone properly in SQL Server? by 20c
Current License: CC BY-SA 3.0
Post Revisions
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2020 at 9:24 | comment | added | Arwin | For most cases this is correct, but consider daylight saving time. If you record a time in the summer, in the winter it will be shown as a different time. This is a bug that was in Exchange/Outlook for many years frustrating customers for whom the exact time could mean winning or losing a patent. So if that's not what you want, you will need to know what the timezone was at the time this time was recorded. Ideally, you will even know this information for the time at which the time was recorded, as you may need historical information on timezones, which sometimes change. | |
| Aug 17, 2016 at 9:57 | review | Late answers | |||
| Aug 17, 2016 at 10:15 | |||||
| Aug 17, 2016 at 9:40 | history | answered | 20c | CC BY-SA 3.0 |