Hi,

I'm currently working on synchronizing two databases on the same SQL Server 2005 instance.
One database publishes and distributes an article.
The other database is the subscriber.

One table contains a datetime column. Once records in this tables are synchronized on the subscriber, there is an offset of 1 hour.

e.g.: on the publisher the datetime is 2008-12-19 00:00:00.000
whereas on the subscriber the value is 2008-12-18 23:00:00.000

I have been searching the internet for similar posts. There are a number, but no answer yet that helps me out.

Thank you in advance!

Regards Roeland Verbeek

Does the system time on both the publisher and subscriber look same or different?

__________________
- Vijay G

What about replication and UTC time?

I'm a bit reluctant to admit that the problem wasn't on the SQL side.

Our customers are running their business on Navision (Microsoft Dynamics Nav). Navision uses SQL server as database.

It appears that if you enter a date time in Navision, everything looks OK. Running a query within Navision shows the correct date time.

However, the record stored in SQL Server it self already shows a one hour shift. And this record is replicated.

To be short: SQL works okay, but Navision uses some kind of time zone setting to store the actual data.

Thanks for your time!