Here is a strange one. I have a service that is invoked by a jdbc update notification. When invoked it inserts a row in a table. One of the fields inserted is a timestamp obtained from IS via the built-in function getCurrentDateString (with template yyyy-MM-dd HH:mm:ss.SSS).

So far so good. However, in one of my test the timestamp that was stored in the table was approximately one hour ahead of the actual time (actual time= 11:15 AM, stored time=12:18 AM). All other tests show the correct time. I cannot reproduce the problem but my data base contains hard evidence that this truly happened.

Obviously, something funny is going on when and IS date string is converted to a SQL Server datetime field.

Oh, now I get it. SQL Server counts time as 12:00 AM, 1:00 AM, … 11:00 AM, 12:00 PM. I thought midnight was 00:00.