DacFx 3.0 performs poorly when dacpac has a medium-large schema - by mistermanager

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 811990 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 12/19/2013 7:22:27 AM
Access Restriction Public


I see no option for windows 8, but I am on windows 8 with Visual Studio 2012 Ultimate. 

When using the DacFx 3.0 API (http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.dac.aspx) the DacServices.Deploy and DacServices.GenerateDeploymentScript commands perform poorly when a dacpac is of a reasonable size. This is a curious problem as it is my understanding that DacFx 3.0 is backed up with dbSqlPackage, which has no issue whatsoever with the exact same dacpac. 

A script generation or deployment can take as much as 20 minutes to run, which is obviously unacceptable. If this were addressed it would make the DacFx 3.0 API an extremely powerful tool.
Sign in to post a comment.
Posted by Jing [MSFT] on 1/26/2015 at 1:33 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server.  The reasons for closing these bugs are following:
1.       The fix is risky to implement in the current version of the product (service packs)
2.       Scenarios reported in the bug are not common enough
3.       A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.
Jing Sun
SQL Server Tools Dev Team