Changes to the Custom Provider for MySql (dbFullMySql)

Posted: Apr 29, 2009  1 comments  

Average Rating

Tags

During the RC release, we published a custom provider that will help you sync MySql databases. The limitaions of the provider was syncing from archive/package and syncing over the agent, since DeploymentObject.GetStream() method was not public in that release. We fixed this when we re-released RC, so now you can sync over msdepsvc (using computername=) using custom providers.

The sample along with the source code that allows you to utilize the GetStream() functionality is located here. It is very similar to the original sample for dbFullMySql provider, but for the fact that dbFullMySql now works over the agent like all other providers that msdeploy supports. It uses GetStream() inside of Add() to achieve this.

So now, with dbFullMySql you can do something like

1) Sync a local database to a remote destination

msdeploy.exe -verb:sync -source:dbFullMySql="server=localhost;database=gallery2;uid=root;pwd=iis6!dfu" -dest:dbFullMySql="server=localhost;database=gallery3;uid=root;pwd=iis",computername=iis-msd126,username=administrator, password=iis

2) Sync a local database to a .sql file on a remote machine, etc..

msdeploy.exe -verb:sync -source:dbFullMySql="server=localhost;database=g2;uid=root;pwd=iis6!dfu" -dest:dbFullMySql=c:\sql.sql,computername=iismsd126,username=administrator,password=iis

Comments

  1. Antoine.Mediana
    November 4, 2009

    Is this still necessary as the v 1.0 is released ?

Submit a Comment

Microsoft Communities