Riyaz wrote:Hi There
We have a problem in Azure SQL db where the database assumes a different timezone than whats set on the azure sql server. Please let me know how to solve this as we are getting some time travel issues within Jiwa.
Why is it a problem?
Azure SQL is always UTC as far as I was aware, and that cannot be changed, and you shouldn't need to, or care about it.
When you create a document (say a PO) in Jiwa the date/time used for the document date is that of the Windows environment running the application - so in your Azure VM you should have set the region and timezone to suit your needs. The Azure SQL Server stores what dates it's been given, except for LastSavedDateTime which is the SQL Server date and is used for concurrency control.
If you're doing something that relies on our LastSavedDateTime fields to be the same timezone as your application, then you need to adjust your comparisons to convert the UTC time to local time.
I can only guess really what your best course of action is because you never said what the problem is.