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.
One of the most wanted Azure SQL Database Managed Instance features is now available!
Check the announcement with link to the docs:
Thanks for valuebale information
<a href="https://polyapk.com/clash-of-magic-apk-2020-download-latest-hack-mod-apk/">clash of magic</a>
<a href="https://polyapk.com/doodle-army-2-mini-militia-mod-apk-5-0-2-unlimited-ammo-and-nitro/">mili militia 2 apk mod</a>
Talha BAR commented
I know about one, the one name Azure SQL database Manager
Thanks for sharing this information. I really like your post very much. You have really shared an informative and interesting post with people https://www.tellthebell.today/
yes and i think on of the most popular is azure SQL 1 gb rfs. great!!
Thanks for sharing this useful info..
Can I know if you are planning to do this in the Single database instances too?
I don't understand how SQL Azure has Getdate() and Getutcdate() that return the same results... why have 2 functions that do the same thing? It's non-sense to me and it is affecting our software for which we are promoting to install it on SQL Azure (single database)...
I need to know How to proceed... Stay with Azure, change all the calls in our software or find another solution?
When can we expect this feature go live after preview.?
Sorry but I'm going to say it... this really needs to be on the cheaper offerings too
Phil Marshall commented
Fabulous to see this progressed! Thanks for listening to customer feedback! :-)
For those looking for the documentation, I found this page:
The key messages that I got out of this is:
* As of today (11-Apr-2019) it is in Preview.
* Managed Instance is the only deployment option of Azure SQL Database that supports time zone setting.
* A time zone of managed instance can be set during instance creation only.
Hi - is this fix also available for Azure SQL or just the Managed Instance ? thanks.
Sorry, I am new to these boards...where do I go to see the documentation on the feature how to do this now that is is available?
Parimala Ramdas commented
What date is the approximate release of this in gov cloud? Thanks
Parimala Ramdas commented
Is this going to be rolled out in Azure gov cloud as well?
Craig Gall commented
He there. Are we still looking at April for Preview on this.
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.