Sync Framework dos and don'ts RRS feed

  • Question

  • Are there any dos and don'ts which a database should follow in order to be successfully synced by the SyncFx?


    I know primary key must exist on all tables being synced. Is there a list of such do's and don'ts for the Database Schema Creators and Programmers?

    Wednesday, March 2, 2011 1:00 PM


All replies

  • It is a bit too broad of a question.

    Take a look at some of the compiled Considerations for Application Design and Deployment. But this may or may not be what you are looking at.

    This posting is provided AS IS with no warranties, and confers no rights
    Thursday, March 3, 2011 7:29 AM
  • What question was specific what things a table creator should do (or should not do) when he is creating a table.

    Upon reading the URL above, I got two things


    1. Use primary key

    2. Avoid identity keys because upon replication identity keys increase the chance of conflict.


    Anything else which I missed?

    Friday, March 4, 2011 7:49 AM
  • - Truncate does not work

    - Schema changes need de-provision provision of scopes.



    - Paras Doshi, Blog: http://www.parasdoshi.com
    • Marked as answer by MSDN Student Sunday, March 13, 2011 12:19 PM
    • Edited by Paras Doshi Monday, July 16, 2012 4:33 AM
    Sunday, March 13, 2011 12:09 PM