Search

Database Publish needs an option to Ignore Users in target by mstout

Closed
as Won't Fix Help for as Won't Fix

1
0
Sign in
to vote
Type: Suggestion
ID: 779838
Opened: 2/22/2013 1:19:07 PM
Access Restriction: Public
0
Workaround(s)
When publishing a database from SSDT there is no configuration which will drop old tables, procs, etc. but preserver the database users. This is somewhat critical for scenarios where the same database needs to be deployed to multiple servers, with a different user base in each location.

The current functionality either requires manual editing of the deployment script before publishing, or risks wiping out any user access which was not part of the development project.
Details (expand)

Product Language

English

Category

Developer Tools (SSDT, BIDS, etc.)

Proposed Solution

An additional An additional option to ignore users not in source would be the best solution.

Primary Benefit

Improved Administration

Other Benefits

Allows DBAs to configure security for each environment and then reuse the same deployment script throughout the course of their migration process.

Faster Development, the developers do not need to worry about every user who may end up accessing the database in each environment.

Better support for CI builds and automated deployments, less concern that an automated process is going to wipe out user permissions that were added by the DBAs.

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/26/2013 at 10:00 PM
Hey mstout,

Thanks for your feedback regarding the ability to drop all objects in target not in the source except for users/security objects. The team is not currently pursuing the addition of this feature to the DACFx deployment pipeline, however we have an item tracking it should it come up for future consideration.

The current workaround is to manage the deployment of environment specific objects via the Post-Deployment Script, potentially leveraging SQLCMD variable functionality if that is suitable for your scenario.

Let us know if you have any additional questions or feedback regarding SSDT or DACFx.

Thanks,
Adam Mahood
Program Manager
SQL Server Database Systems
Sign in to post a workaround.