locked
Handling Synchronization with Different Timezones RRS feed

  • Question

  • I am synchronizing data between the client SSCE 3.5 (desktop application) and a central SQL Server 2005.  Since the SSCE T-SQL does not have the GETUTCDATE() function then how should one handle synchronizing data between different timezones?

     

    For example, the T-SQL code for an insert on my SSCE database (the client) may look like this:

     

    INSERT INTO Customer (CustomerID, FirstName, Phone, CreationDate, LastEditDate)

    VALUES (1, 'John', '800-555-5555', GETDATE(), GETDATE())

     

    But the server side dates may be in a different timezone.

     

    Is this all handled correctly by the sync framework?

     

    TIA!

     

    ~ Darrin

    • Moved by Max Wang_1983 Friday, April 22, 2011 8:14 PM forum consolidation (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Tuesday, March 18, 2008 10:58 PM

Answers

  • Are you using SqlCeClientSyncProvider?

     

    Change tracking is done using timestamp. Timestamp is a monotonically increasing number that is not correlated in any way with the current date or time.

     

    Thanks

     

     

    Wednesday, March 19, 2008 3:21 AM

All replies

  • Are you using SqlCeClientSyncProvider?

     

    Change tracking is done using timestamp. Timestamp is a monotonically increasing number that is not correlated in any way with the current date or time.

     

    Thanks

     

     

    Wednesday, March 19, 2008 3:21 AM
  • Okay, that makes sense but what about the client (SSCE) which does not support the timestamp data type?  It only supports the datetime data type.

     

    Thanks

     

    Wednesday, March 19, 2008 3:37 AM
  • Actually, it does now. That's how SqlCeClientSyncProvider uses.

     

    Thanks

     

    Wednesday, March 19, 2008 4:40 AM
  • But the SSCE database does not have a data type of timestamp.  Does that matter in this case?

     

    Wednesday, March 19, 2008 4:58 AM
  •  

    sorry folks. why you need to call getutcTime(), or timestamp value on the SSCE db ? the anchor value was created on the sql server anyways, right ? doesyour app download the tracking columns to the client db?

     

    thanks

    Yunwen

    Saturday, March 29, 2008 2:33 AM
    Moderator
  • SSCE 3.5 supports rowversion (timestamp) data type

     

    Sunday, March 30, 2008 8:27 AM