Skip to main content

We have discovered that our IFSCloud database server is currently running 1 hour behind the local time, resulting in a 1-hour time difference between the server and the local time.

I would like to know if adjusting the server time while the environment is up and running could cause any issues. Has anyone encountered this situation before? If so, what precautions should we take when correcting the server time to avoid any potential impact on the system or database performance?

Any insights or best practices would be greatly appreciated!

Hi @maheshmuz,

Changing the database server time while it's running can lead to significant issues, including inconsistent timestamps in data records, disruption of transaction logs, and problems with time-sensitive jobs like backups or scheduled queries. It can affect data consistency, especially in distributed systems, where time synchronization is crucial, potentially leading to replication conflicts. Time-based triggers, constraints, or caches may behave unpredictably, and logs could become difficult to interpret due to mismatched timestamps. These disruptions can also affect backup operations and audit trails, so it's important to plan carefully, pause critical processes, and synchronize distributed systems before making time changes.


Reply