Database Project enhancement - by Michael Bulava

Status : 

  Other<br /><br />
		This item had a custom resolution.<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 637817 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 1/24/2011 6:02:01 AM
Access Restriction Public


We are starting to use database projects within our orginization, we created baseline dbschema files from our production environment to create a base version.  We now are using a custom tool based on vsdbcmd.exe to create static scripts to alter our databases in Devint and QA and eventually production.  These releases are iterative, and once a schema change is made in say build 1 we would like for the script generated in Build B to validate if the change has occured before attempting to execute the alter command again.  This is really only important for scheam type changes, column, Constraints, Forgein Key or Index additions.  We've started a Custom Deployment Plan Modifier Extension to do this (  But it's far from perfect, an option built-in to Visual Studio would be best.

Discussion started at:
Sign in to post a comment.
Posted by Barclay [MSFT] on 3/25/2011 at 2:52 PM

Thank you for submitting this feedback. We have captured this feedback in our product backlog and it will be considered for future improvements to Visual Studio Database Development Tools.

If you specify a target database before you generate a script it will produce a one way script including only the net difference between the model and target databases.

If you want to do something customer you may want to review this post:


Barclay Hill
Sr. Program Manager | Visual Studio Product Team (Data Tools) | Microsoft Corporation
Posted by Microsoft on 1/24/2011 at 6:12 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(