Comments
Sort by recent activity
Thanks! We'll give this a try / comments
Thanks! We'll give this a try
I am having the same issue with a SQL Login/user I created to mimic the setup that a fwe developers are going to be using to work on a shred database.
It works when I give this Test login the db_owner role, but I don't want the developers to have that in practice because we are not version controlling database users and I am concerned that they wil accidentally check in a user when checking in a proc (since SQL Source control prompts you to checkin users that have explicit rights to an object, as we do) The script that gets generated by SQL Source control when checking in a user has "create Login" code in it, which is a big potential security issue if developers can create a SQL Login/PW at the server level and get it deployed to other environments via checking in a database user.
I suppose another way to solve this problem would be if there is a way to suppress the Create Login part of the script when checking in a user, is that possible? / comments
I am having the same issue with a SQL Login/user I created to mimic the setup that a fwe developers are going to be using to work on a shred database.
It works when I give this Test login the db_ow...