Robin35 (12/9/2016)
Eric M Russell (12/9/2016)
Where I work, we use Octopus and Chef for automated deployments. If what you need is an account that can create a database, create objects within that, and then assign users access and permissions on that, then the dbcreator server role can do this as it becomes owner of the databases it creates.NOTE: The account does not have access to other databases it didn't create, however, it can drop other databases. I have confirmed by adding a dbcreator account on my local 2014 instance.
we are planning to implement the Octopus deploy in our environment but it's not live yet and also not sure if it's applicable to existing database ?
For deployment accounts, I've been granting account membership in dbcreator server role and then for any pre-existing databases for which the account may deploy to, I add account to those specific db_owner database roles. However, it depends on the nature of your deployments.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho