paul.knibbs (8/24/2016)
Got the wrong answer, but that's because I pretty much clicked at random...I wanted to know the actual answer and my Google-fu failed me in finding it. Odd that functionality like this is only just being introduced in SQL 2016, though, I imagine it would have been useful a long time ago!
Maybe is a little bit confusing that in the MSDN documentation
for sys.time_zone_info (Transact-SQL) is incorrectly specified:
"Applies To: "SQL Server (starting with 2008)".
Nice one, thanks Steve.