SQL Source Control 7


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.

You need:

  • VIEW DEFINITION for all objects

  • 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.

  • permission to read the default trace

  • if you have encrypted stored procedures, to commit or retrieve them you need sysadmin permissions
  • Execute and Alter permissions on TempDB

We also recommend you have:

  • SELECT permission for the system view sys.sql_expression_dependencies 
    SQL Source Control will work without this permission, but it'll have poorer performance.
  • VIEW SERVER STATE permissions, especially if you want to commit or retrieve encrypted objects

For more information about permissions, see your SQL Server documentation.

Didn't find what you were looking for?