locked
Best Practice for Schema Changes? RRS feed

  • Question

  • What is the recommendation for handling schema changes on the server database? For instance, if a column is added at the server, how can that be propagated down to the client with Sync Services? I know deleting the table will cause Sync Services to recreate it from scratch, which would inherently give you the latest schema. But is there a more efficient way of handling this? And is there someway of knowing whether or not the schema at the client level matches the one at the server level?

    • Moved by Max Wang_1983 Friday, April 22, 2011 8:58 PM forum consolidation (From:SyncFx - Microsoft Sync Framework Database Providers [ReadOnly])
    Wednesday, October 31, 2007 6:22 AM

Answers

  •  

    Hi Vesigo,

     

    Schema changes are not automatically replicated/synchronized to the client db in the current release. drop the table and reapply everything from the server would be easiest way to do. if the cost is too much ( e.g. table is too big ), you can add the column on the client db manualy and then change the commands on the server provider accordingly so get the data for the new column replicated down to the client.

     

    Best wishes,

     

    Yunwen

    Friday, November 2, 2007 4:47 PM
    Moderator

All replies

  •  

    Hi Vesigo,

     

    Schema changes are not automatically replicated/synchronized to the client db in the current release. drop the table and reapply everything from the server would be easiest way to do. if the cost is too much ( e.g. table is too big ), you can add the column on the client db manualy and then change the commands on the server provider accordingly so get the data for the new column replicated down to the client.

     

    Best wishes,

     

    Yunwen

    Friday, November 2, 2007 4:47 PM
    Moderator
  • That is what I was hoping would be a bit more automated in Sync Services. If it's not going to do this for us, I was hoping to get a little direction on what would be the best practice for maintaining the schema across updates so that what we do now is in line with what sync services will eventually do.

     

    Saturday, November 3, 2007 2:53 AM
  • there is a session in the BOL talking a little bit about handling schema changes.

    ms-help://MS.SynchronizationServices.v1.EN/syncdata1/html/b654dfeb-8bdd-4f0c-b9d9-097b680dd50c.htm

     

    thanks

    Yunwen

     

    Sunday, January 20, 2008 7:47 PM
    Moderator