none
How to prevent insert data at the first synchronization process? RRS feed

  • Question

  • I have a database server and a laptop database. The database server has data and the laptop database is empty.

    At the first synchronization, the laptop database will have the data from the database server. But I do not want this. I like the laptop database is still empty. From then on, any changes on server or laptop will replicate to other.

    Could you please advise how I implement this?

    Thanks!

    jz

    Monday, February 25, 2013 11:28 PM

Answers

  • Some lookup tables will be same on the server and client, but client laptop does not need other data on the server. I will look into this according to your input.

    By the way, I only need to do this on the first time correct? Then, the client and the serever will have the same version. Then the new changes will replicate. Could you please confirm this for me?

    Thanks!

    jz



    • Edited by jz2012 Wednesday, February 27, 2013 11:09 AM
    • Marked as answer by jz2012 Wednesday, February 27, 2013 2:26 PM
    Tuesday, February 26, 2013 8:29 PM

All replies

  • so if you skip the first sync, what would be your expected behavior if an update is made to a row in the server and you sync, but there is no row in the client?

    if you really want to do this, you can intercept the changes in the ChangesSelected event of the sync provider pointing to your server on first sync and clear the dataset/datatable of rows...

    Tuesday, February 26, 2013 11:00 AM
    Moderator
  • Some lookup tables will be same on the server and client, but client laptop does not need other data on the server. I will look into this according to your input.

    By the way, I only need to do this on the first time correct? Then, the client and the serever will have the same version. Then the new changes will replicate. Could you please confirm this for me?

    Thanks!

    jz



    • Edited by jz2012 Wednesday, February 27, 2013 11:09 AM
    • Marked as answer by jz2012 Wednesday, February 27, 2013 2:26 PM
    Tuesday, February 26, 2013 8:29 PM
  • you don't have to put all tables in one scope. if you have lookups that are just readonly in client and is simply downloaded from the server, you can put them in a separate scope. 

    have a look at this one: SYNC FRAMEWORK SCOPE AND SQL AZURE DATA SYNC DATASET CONSIDERATIONS


    Wednesday, February 27, 2013 11:09 AM
    Moderator