If you use the dbup method to ensure the database is created if it doesn't exist, then it will connect to master. If you don't use that method, then I don't think you need master access. I resolved a similar issue by not using that method recently.
From: dbup-d...@googlegroups.com <dbup-d...@googlegroups.com> on behalf of Michael Strasser <mst...@thoughtworks.com>
Sent: Friday, May 17, 2019 7:51:22 AM
To: DbUp Discuss
Subject: Minimum permissions in SQL Server for DbUp
We are using Octopus Deploy to deploy Windows apps to a distant on-premises data centre with strict security controls.--
We want to run SQL Server migrations using DbUp but our attempts so far have failed. We believe this was because the user running DbUp did not have permissions to read the master database to confirm the existence of the database we wanted to modify.
We know that the user was granted the db_ddladmin role on the database but we think the public role had be altered to remove read permissions on master.
Can anyone confirm that we need to be able to read master for DbUp to do its stuff? If so, should we ask to be granted db_datareader role on master on the server?
ThanksMichael Strasser
You received this message because you are subscribed to the Google Groups "DbUp Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dbup-d...@googlegroups.com.