1

I Have a web site, which is on server1. It uses web service, which is on server2. Web service uses database, which is on server3.

Server1 server2 and server3 has different timezone, so when I get datatable via web service, Datetime type column has different time value.

For example,

if in database I have a record (date type) '2010-03-24-12:00:00', on web site I get '2010-03-24-13:00:00'

I tried to change column's "DateTimeMode" but problem was not solved.

madth3
  • 7,275
  • 12
  • 50
  • 74
Vano Maisuradze
  • 5,829
  • 6
  • 45
  • 73
  • 1
    Are you sure the values aren't already stored wrong now? Because the DateTimeMode did it for us – flq Mar 23 '11 at 21:55

3 Answers3

3

As a rule of thumb, I have always stored datetime values in my databases as UTC and left it up to the client to adjust accordingly to its associated timezone. .NET 3.5 makes this timezone adjustment very easy.

Ben.Vineyard
  • 1,149
  • 8
  • 14
2

There is a problem with serialising a DateTime and WCF.

The best solution is to always store the DateTime as UTC in the database. Then when reading the DateTime from SQL always use DateTime.Specify to specify a DateTimeKind.Utc.

Richard Schneider
  • 34,944
  • 9
  • 57
  • 73
1

Using Universal time or GMT should cure that problem.

gt124
  • 1,238
  • 13
  • 23