sql server - Dacpac Upgrade database Times a little silly -
edit: updated state isn't hanging, takes ages!
i'm trying update existing sql server database using dacpac.
i can create new sql server database (stripped down) example below in 30 seconds. issue i'm having using same dacpac, rerunning procedure (so updating existing database rather creating afresh) takes 20 minutes.
is kind if time difference expected? having used redgate's sqlcompare comprehensively, i'm finding time unpaletable.
the third param of deploy method upgradeexisting i'm setting true - need or missing something??
void deploy(string targetconnectionstring, string targetdatabasename, string pathtosourcedacpac) { dacservices dacservices = new dacservices(targetconnectionstring); //set message , progress handlers dacservices.message += new eventhandler<dacmessageeventargs>(dbservices_message); dacservices.progresschanged += new eventhandler<dacprogresseventargs>(dbservices_progresschanged); //load dacpac dacpackage dacpac = dacpackage.load(pathtosourcedacpac); //set deployment options dacdeployoptions dacoptions = new dacdeployoptions(); dacoptions.allowincompatibleplatform = true; //deploy dacpac dacservices.deploy(dacpac, targetdatabasename, true, dacoptions); } //event handlers... void dbservices_message(object sender, dacmessageeventargs e) { outputthis("dac message", e.message.tostring()); } void dbservices_progresschanged(object sender, dacprogresseventargs e) { outputthis(e.status.tostring(), e.message.tostring()); } nb program disappears ether on dacservices.deploy line..
ok, silly times experienced while running through debugger (vs2012). once compiled times 25 or seconds when chosing memory dacschemamodelstoragetype, or 45 or seconds when chosing file dacschemamodelstoragetype .
i guess means debugging pain in whatsit!
Comments
Post a Comment