Change Detection with standard trace columns and UTC/local time mismatch

Hi everyone,

We are using Auto Refresh with Change Detection on a view in our Thinkwise application.

Our Change Detection query is based on the standard trace columns, for example:

where update_date_time > @last_refresh_utc

During testing we noticed that the view was refreshing every refresh interval, even when there were no actual changes.

After some investigation we found the following:

• @last_refresh_utc is supplied in UTC by the GUI/Application Tier.

• Our insert_date_time and update_date_time trace columns contain local SQL Server time.

• On our environment the difference is currently +2 hours (CEST).

For example:

select
    sysutcdatetime() as utc_time,
    getdate() as local_time,
    max(update_date_time) as latest_update
from stage_sales_order;

Result:

utc_time      = 2026-06-03 13:41
local_time    = 2026-06-03 15:43
latest_update = 2026-06-03 15:43

Because of this, Change Detection keeps finding records where:

update_date_time > @last_refresh_utc

even though no new changes have occurred.

As a test, we modified the Change Detection query to compensate for the timezone difference:

dateadd(hour, -2, update_date_time) > @last_refresh_utc

After doing so, the continuous refreshing stopped and Change Detection behaved as expected.

My question is:

What is the recommended Thinkwise approach in this situation?

• Is there a built-in way to compare local database timestamps with @last_refresh_utc?

• Are there best practices for using Change Detection together with the standard trace columns?

Thanks in advance.