Published 16 July 2015
The permissions you need to use SQL Source Control depend on the objects in your database schema. If you don't have sufficient permissions, objects may be missing from the change list. For example, user defined types won't be listed if you don't have permissions for the schema they belong to.
dborole on the database you want to link to source control
This is needed because SQL Source Control writes extended properties at the database level.
- permission to read the default trace
permission to make all the listed changes in a commit or get latest
If you don't have these permissions, committing or getting latest can fail. If this happens, SQL Source Control uses transactions to try to roll the changes back, but won't always be successful.
- if you have encrypted stored procedures, you need
sysadminpermissions to commit or retrieve them
SQL Server 2008 and later
Additionally, if you're using SQL Server 2008 or later, we recommend:
SELECTpermission for the system view sys.sql_expression_dependencies. You may experience poor performance if you don't have this permission.
VIEW SERVER STATEpermissions to commit or retrieve some encrypted objects
For more information about permissions, see your SQL Server documentation.