Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Require lesser SQL Server permissions than dbo to use

The permission of dbo required to use SQL Source control is not good and indeed a lot of dba's do not like the idea of having to grant dbo permission for users who wish to use the source control. In some companies it would not be possible to grant dbo permission.
Could SQL Source Control be changed to not require dbo but perhaps something lesser. Indeed give the option to not writes extended properties at the database level.

14 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Jimbo shared this idea  ·   ·  Report…  ·  Admin →
completed  ·  AdminMichael Upton (Development Lead, Redgate) responded  · 

I’m pleased to say that the latest version of the migrations feature no longer requires extended properties on your database.

This means that as of version 5.1.1 of SQL Source Control, Alter Database/dbo permissions are no longer required.

Mike Upton
Technical Lead | SQL Source Control

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Jimbo commented  ·   ·  Report

    I agree. The level of permission required is ridiculous and would prevent the tool being used in a lot of companies.
    Granting a user db_owner permission just to use the tool is real overkill and is VERY disliked by DBA's.

    Please revisit this issue as I can see no sane reason for such an elevated level of permission.

  • Joel Miller commented  ·   ·  Report

    I agree 100%. I ran into this requirement today after just purchasing only a few weeks ago. Had I known this in the first place, I would have probably looked a lot harder at alternatives.If it is still this way at renewal time, I will probably try to find a new vendor to migrate to.