Support regional settings to fix GetDate() function
GetDate still on UTC all the time. For the promised value of MI to be the destination for lift&shift without code changes, this breaks it. Now developers have to review their code and update it for MI and if decided to move the database to their IaaS environment, they have to change it back again.
Thank you for your feedback. We are currently working on supporting non-UTC time zone in Azure SQL Managed Instance.
We are also interested in your feedback on use cases for changing time zone setting on the existing instances, aside from the trivial case of correcting time zone chosen by mistake.
It's almost there, it will enter public preview during April and GA should follow very soon after that.
May i know aprroximate release of non-UTC time zone?
Marc L. Allen commented
Is there any place to get an update on when this might be completed? I have a managed instance, and I'm OK with just changing the timezone. I'm not worried about fixing anything due to the UTC timezone.
Bill Hodder commented
Well if you guarantee to add the feature to change the time zone, then we could move to it immediately, as GMT and UTC match for the next few months... so isn’t a problem right now, but will become a major problem for us when DST kicks back in...
Andrew Toi commented
yes, that would be helpful for our existing deployed instances.