Visual Studio 2008 Database Edition GDR - Finer Grain control of User, Schema, & Permission scripting - by mweber3

Status : 

  Postponed<br /><br />
		Due to current priorities, the product team decided to postpone the resolution of this item.<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 424035 Comments
Status Closed Workarounds
Type Suggestion Repros 1
Opened 3/16/2009 7:26:24 AM
Access Restriction Public


In our organization, the development team does not manage users for databases.  This means we don't have any user objects in our Visual Studio 2008 Database Edition GDR projects.  We do have database roles and mappings of permissions to objects to those roles.  The DBAs would then grant users access to roles after deployment.  With the GDR we need the ability to suppress the DROP USER, DROP SCHEMA, and REVOKE CONNECT scripts that are output to the difference script during deployment using VSDBCMD.  There is an option to IgnorePermissions in the *.sqldeployment file that will suppress the REVOKE CONNECT scripts but this also removes any permissions we grant to database roles for objects in the *.sqlpermissions file which we do not want.  In addition there isn't any option to "Ignore Users" or "Ignore Schemas".
Sign in to post a comment.
Posted by Biswajit Pattanaik on 8/6/2013 at 10:11 PM
Hi All, Do we have an update for this? We have around 20-25 DBs in our projects and facing a lot of issues during deployment.
Posted by noonie on 4/28/2010 at 9:58 PM
The ability to omit the DROP user statements from the deployment sql file is very important to us, especially for incremental deployments to multiple databases in multiple environments. We do not model users in our projects but use database roles and application roles for our applications. Users, and other security objects, are solely under the control of the administrators of our environments and frankly none of our (developers) business.

Presently we are working around this by turning off "Generate DROP statements for objects that are in the target database..." deployment option and handling the dropping of schema objects in pre/post deployment scripts but this is not ideal.
Posted by Microsoft on 3/4/2010 at 3:22 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 the Visual Studio Database Development Tools.

In VS 2010 we have added some lower level drop options for deployment that allow dropping indexes and constraints not defined in the project. We will consider expading this to also include the users, schemas, etc, options as well.


Barclay Hill
Program Manager | Visual Studio Product Team (Team Engineering - Database Tools) | Microsoft Corporation
Posted by Microsoft on 3/17/2009 at 3:24 AM
Thanks for your feedback. We are escalating your feedback to the product unit who works on that specific feature area. The product team will review your feedback and make a decision on whether they will fix it or not for the next release.