New Reply

Good news! We have migrated all the Q&A on this site to, and are currently monitoring questions there!

Here are some important links:

All posts here are permanently locked (and will be redirected soon), and if you have any issues with the new site, please submit a support ticket, use the contact form, or visit our Slack Workspace.

I read here: that the only permissions needed to deploy DB scripts to SQL Server is the BuildMasterUser_Role. What if this role does not exist? How is this role created if the Service Account doesn't have permission to the SQL Server already?

We are trying to automate deployments to SQL Server and I initially provided the account "dbcreator" role but that failed. I couldn't find any documentation but for the link above. I had to grant it sysadmin privileges temporarily, and obviously that is not a good long-term solution.


Good question – we’ll have to fix this in our documentation. The BuildMasterUser_Role is for the BuildMaster Application (WebApp/Service) talking to the BuildMaster Database – doesn’t have really anything to do with deploying to databases.

The database deployment bits of BuildMaster need only the permissions that the scripts need to run. You set up the database credentials in a your connection string (or, if you’re using integrated authentication, the service account) – so it’s really up to you. We generally recommend giving db_owner against the target database, since your scripts will generally do a bunch of things like create, alter, etc. But that’s up to you. The script will just error out if permissions aren’t there.