SQLPackage and Deployment plan modifiers
-
7 марта 2012 г. 7:09
Hi
does SSDT and more specifically SqlPackage.exe support deployment plan modifiers in the same way that VS2010 & VSDBCMD does ?
Dave
Dave Ballantyne ---- http://sqlblogcasts.com/blogs/sqlandthelike/
Все ответы
-
7 марта 2012 г. 16:41Владелец
Hi Dave,
SSDT (and SqlPackage) does not yet support Deployment Contributors like could be created and used in the existing VS2010 Database Project system. We are considering plans for incorporating these extensibility points into the product for a future release.
Thanks for your feedback,
Adam
Adam Mahood - Program Manager - SQL Server Data Tools
- Предложено в качестве ответа Adam Mahood [MSFT]Microsoft Employee, Owner 7 марта 2012 г. 16:41
- Помечено в качестве ответа Dave_Ballantyne 8 марта 2012 г. 10:26
-
8 марта 2012 г. 6:29Модератор
Dave,
Out of interest, what are you using Deployment Contributors for in VS2010 database projects?
Want to make sure we can support that scenario going forward.
-GertD @ www.sqlproj.com
-
8 марта 2012 г. 7:23
Hi Gert,
So, the issue we have is that we developing an automated
deployment solution using vs2010 at the moment.
Our big headache has been the artefacts that are required by
replication and ensuring that these are not changed by such a deployment. Mostly this is fine , we have ‘hidden’ many
objects using the extend property of Microsoft_system_.. (something :;). But the issue I am with right now is the
check constraint used in merge replication ( MSRepl_XXXX something…) , which I was
hoping to be able to mask with the modifiers.
Plan b is to have a powershell script to update the source
(dacpac / dbschema) with the live constraint name and constraint condition , so
it is seen as a ‘no change’ item.Dave Ballantyne ---- http://sqlblogcasts.com/blogs/sqlandthelike/
-
10 марта 2012 г. 19:25Модератор
Hi Dave,
In SSDT we added a deployment option named, to ignore replication related objects, named "Do not ALTER replicated objects", I would first try if that helps you.
You can use this option both from MSBuild using the publish profile or using SQLPackage.exe
In general sqlpackage.exe will give you more freedom (less dependencies to install, only DACFramework.msi) and options over MSBuild /t:deploy besides that you can use it from an API and are not tight to the MSBuild environment.
Let me know if this helps,
-GertD @ www.sqlproj.com
-
11 марта 2012 г. 11:14
Hi Gert,
Things have moved on, extensions with a RegEx pattern is working just fine to exclude certain DDL that is produced by the MSBUILD /t:deploy setting. Being tied to MSBuild is not an issue for us ( at least at the moment :) ).
Thanks for the info, for completeness ill try the option and see what coverage , in terms of exclusions, we get
Dave
Dave Ballantyne ---- http://sqlblogcasts.com/blogs/sqlandthelike/
-
18 сентября 2012 г. 19:07I have the same question. When will SSDT support Build and Deployment Contributors like VS2010 Database Projects does?
Brian Barnett
http://www.profisee.com
“As the original creators of Microsoft MDS, Profisee's Master Data Maestro provides a range of enterprise-grade functionality to ensure MDS project success.”

