The permissions required to use SQL Source Control depend on your version of SQL Server and the objects in your database schema. If you don't have sufficient permissions, some 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:

• dbo permissions for the database you want to link to source control. This is 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

  Committing or getting latest can fail if you don't have these permissions. When committing or retrieving fails, SQL Source Control uses transactions to try to roll the changes back; however, this won't always be successful.

• if you have encrypted stored procedures, you need sysadmin permissions to commit or retrieve them

Additionally, if you're using SQL Server 2008 or later, we recommend:

• SELECT permission for the system viewsys.sql_expression_dependencies. You may experience poor performance if you don't have this permission.

• VIEW SERVER STATE permissions to commit or retrieve some encrypted objects

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