Thursday, December 27, 2012 1:55 PM
I'm currently investigating moving over our home-grown deployment scripts to SSDT and DACPACs and have a couple of questions. Consider the following scenario:
- Database deployed version is 1.0.5
- DACPAC version is 1.0.3
When I do an upgrade of the DACPAC either via sqlpackage.exe or SSMS this will just downgrade the database to the 1.0.3 version as it detects the changes. What I would like to see is that the upgrade mechanism blocks because the registered (deployed) version is higher than the package. Is this something that is possible or should the deployment be wrapped in a Powershell script? (not really desirable)
- Moved by Sethu SrinivasanMicrosoft Employee Wednesday, January 02, 2013 3:20 PM DAC (From:SQL Server Tools)
Monday, December 31, 2012 3:03 AMHi Sander,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
TechNet Community Support
Thursday, January 03, 2013 3:57 PMOwnerSorry, we do not have anything at this point that blocks based on the version of the DACPAC/registered DAC.
- Marked As Answer by Janet YeildingMicrosoft Employee, Owner Saturday, March 09, 2013 12:41 AM