I just encountered a strange thing - this is the scenario:
NAV 3.70.B on SQL Server 2000, Windows Server 2003, Client and Server on the same machine
A certain process - a stored procedure from a non-NAV db - writes records into a NAV table. When doing this, the field “Inserted Date/Time” (type datetime) is filled; the sp uses the getdate() function for this. Now it comes: if the system time is e.g. 17:00, getdate() retreives 17:00 and inserts this into the NAV table. But when looking at the record in NAV (via Table Run, Form or C/AL Code) the time is 19:00 - plus 2 hours!!! When querying the record via SQL Query Analyzer, the time is still 17:00 (which is correct). (The date is allways OK)
When NAV is processing the record, the field “Processed Date/Time” is filled, using the CURRENTDATETIME function. E.g. at system time 18:00 NAV inserts 18:00, but when querying this via QA the time is 16:00 - minus 2 hours!
So there is allways an offset of two hours between physical storage and display in NAV. To me this looks like a TimeZone problem: In the current case it’s Copenhagen, GMT+1 (DLST), but as mentioned: Client and SQL Server are running on the same machine, thus using the same TimeZone etc…
What is going on there? What do I have to check/configure/change? Please enlighten me!