locked
Client does not detect changes on MS SQL 2005 Server RRS feed

  • Question

  • Hello,

    I am working with the Sync Framework to develop an application
    using serval Windows Mobile 6.1 clients syncing with a MS SQL 2005 server
    via webservices.

    So far my application works fine. The synchronization process downloads
    the database-content from the MS SQL2005 server, the clients make changes
    and synchronize these changes back to the MS SQL 2005 server.

    BUT...

    If I change any data in the MS SQL 2005 server database, then the
    clients cannot detect these changes.

    I guess that I forgot anything to implement or activate on the MS SQL 2005 server.
    Can anybody give me a hint?

    As far as I know server change tracking does not work on 2005, only 2008?


    Regards,
    Martin
    • Moved by Hengzhe Li Friday, April 22, 2011 5:05 AM (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Tuesday, March 24, 2009 11:43 AM

Answers

  •  I assume you are using the sync service.

    you will need those columns for change tracking purpose.

    thanks
    Yunwen
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, March 25, 2009 10:53 AM
    Moderator

All replies

  • Ok I found it. It was a problem with the an unchanged CHANGE_DATE column.

    By the way... why does the framework use the CHANGE_DATE /CREATE_DATE columns if it uses logical clocks?

    This is not really clear for me until now.


    Regards,

    Martin
    Tuesday, March 24, 2009 3:12 PM
  •  I assume you are using the sync service.

    you will need those columns for change tracking purpose.

    thanks
    Yunwen
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, March 25, 2009 10:53 AM
    Moderator
  • Ok. When CHANGE_DATE and CREATE_DATE are used for change tracking, then I really do not understand why logical clocks are needed.

    Because when I use DATETIME columns for change tracking, then I still have the problems with a possible wrong configured time on a device.
    Tuesday, March 31, 2009 8:37 AM