Can I generate the configuration file from an existing, provisioned database?

الإجابة Can I generate the configuration file from an existing, provisioned database?

  • Sunday, October 31, 2010 7:39 PM
     
     

    I already have a solution deployed with Sync Framework 2.1 and was wondering how I can most easily make the move into the 4.0 world. It seems to me that generating the configuration file from my existing, provisioned database would be very useful.

    Is this supported? Is there a better approach?

    Thanks,

    Scott


    MCPD Enterprise Applications

All Replies

  • Monday, November 01, 2010 8:35 AM
     
     
    I suggest you to wait for the advertised update which just arround the corner and which is said to include a GUI for database provisioning. Probably this doesn't let you reuse your existing provisioning but at least it should ease the creation of the required configuration.
  • Monday, November 01, 2010 9:05 AM
     
     

    Thanks for the reply M.Bi. I had seen a PDC video where the new UI was demoed but could not see any means of generating a config file from an existing, provisioned scope.

    Maybe this is what they are working on now ;)


    MCPD Enterprise Applications
  • Monday, November 01, 2010 4:46 PM
    Owner
     
     Answered

    Hello Scott,

    If you have provisioned your database with 2.1 already, there is nothing you need to do - you can go ahead and have the 4.0 sync service work with the provisioned database.

    However, if your provisioned database is a production database, I would suggest you do not use that in your development and prototyping. Instead, start with a development database, which could be a copy of your production database.

    thanks

  • Monday, November 01, 2010 5:39 PM
    Moderator
     
     

    Scott,

    The UI will let you build Scope definitions from scratch and include all tables. The idea of sucking in an existing scope as a config is a nice idea and I will add this to the requirements for the next refresh. Like Sid mentioned please make sure you start from a backup of the database to ensure that you are not really messing with production data.

     


    Maheshwar Jayaraman - http://blogs.msdn.com/mahjayar