Settings and activity

1 result found

1. Prevent user from committing other user's changes

   79 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  SQL Source Control » Better Support for Shared Db Dev Model  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Kendra responded

   An update for users on the status of this suggestion:

   An ‘object locking’ feature was added to SQL Source Control following the creation of this item which can helps users working in a shared database environment not write over each other’s changes.

   This may help prevent accidental commits in some cases, as there is a “Locking” tab which allows users to see which other users are working on specific items.

   Locked items are still eligible to be committed, however, and there are cases where users will want to commit an item — perhaps to a specific branch in source control which is not ready to deploy — even if the item in the database is locked.

   We have found at Redgate that the easiest way to enable alignment with distributed source control systems such as Git is to empower users to use dedicated development databases rather than shared databases. Tools such as SQL Clone support this. With dedicated databases, each developer can have the version of objects which they need without worrying about whether someone else is changing things in the same database at the same time.

   An update for users on the status of this suggestion:

   An ‘object locking’ feature was added to SQL Source Control following the creation of this item which can helps users working in a shared database environment not write over each other’s changes.

   This may help prevent accidental commits in some cases, as there is a “Locking” tab which allows users to see which other users are working on specific items.

   Locked items are still eligible to be committed, however, and there are cases where users will want to commit an item — perhaps to a specific branch in source control which is not ready to deploy — even if the item in the database is locked.

   We have found at Redgate that the easiest way to enable alignment with distributed source control systems such as Git is to empower users to use dedicated development databases rather than shared databases. Tools… more

   An error occurred while saving the comment
   Sam commented  ·  Mar 30, 2011  ·  Edit…  ·  Delete…

   Completely agree. It would also be helpful if you didn't have to be an administrator to see who made changes. Right now, "Changed By" is populated with unknowns with no hopes of every receiving "Admin" rights.

   Save Submitting...
   Sam supported this idea  ·  Mar 29, 2011