Lowell (5/9/2014)
i'm thinking you might be able to do this in SQL, can't you?what am i overlooking here?
Hey there. I am 99.9% positive that the issue is TIMEZONEOFFSET in SQL Server is not DST aware, hence making historical conversions suspect. That might need to be re-verified as it has been a year or two since I looked into this in detail, but I was wondering the same thing and seem to recall this being the blocker.
Take care,
Solomon...
EDIT:
Actually, yes, that is the issue. TIMEZONEOFFSET requires an actual offset, not a TimeZoneID that would point to info that includes the offset, DST info, etc.
SQL# — https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
Sql Quantum Lift — https://SqlQuantumLift.com/ ( company )
Sql Quantum Leap — https://SqlQuantumLeap.com/ ( blog )
Info sites — Collations • Module Signing • SQLCLR