locked
Using Synchronization Services for ADO.Net version 2 with different time zones RRS feed

  • Question

  • Hi Liam,

     

    Now that the SQL Server 2008 and the Synchronization Services for ADO.Net version 2 are out, I am wondering how I will implement the synchronization I need between SQL 2008 Servers running in different time zones.

     

    I suppose this would involve the use of the new SQL 2008 data type 'datetimeoffset', which defines a date that is combined with a time of a day that has time zone awareness and is based on a 24-hour clock.

     

    Does the Synchronization Services for ADO.Net version 2 automatically uses datetimeoffset data type when using SQL 2008 on both ends when the participating tables on both ends have the 'Change Tracking' feature turned on? Also, is it aware of  the 'Track Columns Update' SQL 2008 table feature and uses it to more granularly track the changes?

     

    If this is not the case, what is required to keep SQL 2008 databases synchronized across different time zones?

     

    Thanks in advance,

     

    Eduardo Quintana

     

    Wednesday, August 13, 2008 2:38 PM

Answers

All replies