Public Preview: Time zone choice for Azure SQL Database Managed Instance
Posted on Wednesday, April 10, 2019
While using Coordinated Universal Time (UTC) is a recommended practice for data tier solutions in the cloud, Azure SQL Database Managed Instance now offers a choice to configure the time zone to meet the needs of the existing applications.
If your application stores date and time, invokes date and time functions, or schedules SQL Agent jobs with an implicit requirement for a specific time zone, you can now migrate to managed instance without any application changes.
A list of supported time zones is regularly updated with the new time zone definitions and changes to the existing ones.
The time zone of managed instance can be configured during the instance creation and cannot be modified once the instance has been created.
For more details, see Time Zone in Azure SQL Database Managed Instance.
See related feedback from Azure customers
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.Mohamed Sharaf