Hello!
I have a branch versioned database that is showing a timestamp that is 5 hours behind. The machine where the data resides is showing the correct time.
Is there a setting somewhere in the enterprise deployment that I may have missed? Any insight is appreciated!
*Updated to add these are local on-prem servers/db.*
Thank you!
Sara
I did more troubleshooting on time zones and put in a change request with our db team to review.
It depends on situational requirements, but best practice is to keep the database server and all timestamp values set to UTC (aka Greenwich Mean Time). Web clients are exceptionally persistent in converting date/time values to localtime, even when they're already sharing a timezone.
- V