Need the ability to set a time zone per Azure sql database
We need to be able to set the timezone for an Azure sql or DW database. This should be a database option.
Now we are faced with changing all of our code which references getdate() and similar date functions.
We shouldn't have this extra difficulty in moving to a cloud database.
Planned for SQL DB- no time frame to share yet. Available in SQL Managed Instance
Stop creating infinite loops in flow.
Sharepoint Designer excludes the triggered workflow when determining whether an item has been updated, ensuring the workflow won't recursively trigger itself in an infinite loop. In Flow there is no such consideration. So when I create a flow to fire every time a list item is changed, and the action is to update something in that list, the action of the flow triggers the flow again. Ergo, infinite loop.
And stop telling the dev community how to work around it. We know how to work around it and create secondary columns that get flagged. The point is we should not have to come up with a workaround for such a stupid, unnecessary problem.
Yes,we are waiting for the change that the user can set the time zone of DW and DB..
Atsushi Kodama commented
I think SQLDB and SQLDW are same, but I'd like to ask that is this also planned for Azure SQL Data Warehouse?
Deepesh Gosavi commented
Temporary solution was shared by team, need to have permanent solution for SQL database. In such case Financial organisation will take back foot. Microsoft should rectify this issue and enable configuration of Time zone as per Country.
Wiwit Khristianto commented
Please priority this mods, as it is a fundamental configuration. i can not believe that it was missed in the design stage of azure hyperscale.
Thank you much appreciated.
We absolutely need do be able to use the getdate() function as it was working in an on premise environment... Our sotware has hundreds of modules. It is unthinkable of having to change all getdate() calls for a call to a udf to mimic the old getdate(). Can someone from Microsoft tell us if this will be done in the single database instances same as it has been fixed in the Managed instances?
Hi - is this also planned for Azure SQL or just SQL Managed Instance on Azure? thanks.
Do we have any update on Time Zone setting for MI?
George Camp commented
Please provide the ability to configure time at the database level for Platform as a service customers.
WE have just gone live with our application and this unseen "feature" of ONLY UTC time is killing us!
This is marked as started in Managed Instance Feedback
Hitesh Patel commented
Do we have any update on Time Zone setting for Managed Instance?
Marc L. Allen commented
Any update on this? I've gotten all excited about SQL MI, carefully combed through the limitations (didn't see any timezone issue), sold my company, created a test host, started testing, and BOOM!
Please, please, don't make me build up a SQL clustered set.
Any plans to include this function for SQL Logical Server and Pools?
Hi, I won't be original, but... Any updates on ETA yet?
Bill Hodder commented
Any update on this? GA for SQL MI is only a few weeks away....
Tomasz K commented
Managed instances in preview (as per https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-transact-sql-information ) " GETDATE() and other built-in date/time functions always returns time in UTC time zone. See GETDATE". This will be available in GA?
Yomi Bazuaye commented
Glad to hear that this feature has been added to the backlog. In my opinion this feature should have been available out of the box.
At this point in time (Late Aug 2018) can anyone from the SQL engineering team give an ETA for the availability of this feature?
Danny Lankar commented
I have now come across this issue and YES We NEED to be able to set a timezone per azure sql database.
Joe Rather commented
I agree with Mark. We need this in PaaS as well as IaaS.