How can we improve SQL Source Control?

TFS - Exclusive Checkout / SVN - Lock

It would be really nice if there was a way to checkout or lock db objects so that I know that I'm the only person working on this object and I will not experience any conflicts when I go to commit the object.

226 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Red Gate AdministratorAdminRed Gate Administrator (Admin, Red Gate) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    35 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • dave mouledave moule commented  ·   ·  Flag as inappropriate

        Yes definitely need locking. It is a standard part of doing a checkout for many organisations.

      • Anonymous commented  ·   ·  Flag as inappropriate

        It's almost silly that we need to vote on this. It's a huge missing part of the application that has made our company decide to hold off on this tool until it has been added.

      • Jack SudolJack Sudol commented  ·   ·  Flag as inappropriate

        It's almost silly that we need to vote on this. It's a huge missing part of the application that has made our company decide to hold off on this tool until it has been added.

      • StephenStephen commented  ·   ·  Flag as inappropriate

        I like @Andrew Hartley's suggestion of a manual flag. Having developers working in two locations a thousand miles apart means you can't exactly call over the cube for a quick "anyone changing XXX?" Manual "mark this as being worked on", with a userid of course, would be very helpful shy of exclusive checkouts everywhere.

      • Andrew HartleyAndrew Hartley commented  ·   ·  Flag as inappropriate

        Happy to compromise on a manual flag option as I'm sure an auto exclusive checkout will require a completely different mechanism to identify changes. We need to be able to flag an object as being edited so that other devs can see and at least have a conversation about whether to merge changes or wait for one change to be checked in before starting the next. We would use this for about 5% of our changes, but they are the time consuming complex headache-generating changes that we don't want to be made even more complicated by sifting through a merge process - please...

      • samsam commented  ·   ·  Flag as inappropriate

        yes I would like exclusive checkout to prevent others from overwriting my code in shared environment.

      • SethSeth commented  ·   ·  Flag as inappropriate

        In response to David's question, I think it is important to support both the ability to lock an object as well as allow multiple people to work on the same object. In the second scenario, I think it is important to alert them that something they are working in is checked out by another developer; in a fashion for than just an indicator on the object. They should have to perform a check out and get notified that "<user> also has <object> checked out."

      • HYHY commented  ·   ·  Flag as inappropriate

        We are delaying the purchase of this product to my whole team because of this missing feature.

      • BradBrad commented  ·   ·  Flag as inappropriate

        This will be a great feature and a deal clincher with management to purchase this product. Trying to resolve conflicts and merge changes of parallel development has wasted too much time in the past and it would be far nicer, safer and simpler if changes were done exclusively. If that's not possible, then even a notification that someone else has made changes that haven't been committed yet would be a good start.

      • David FeilerDavid Feiler commented  ·   ·  Flag as inappropriate

        I agree; we need this lock functionality, or we won't really be able to use the integration. We rely on this to avoid conflicts

      • zacukezacuke commented  ·   ·  Flag as inappropriate

        We are considering using SVN-Lock to prevent multiple people from editing one object in a shared database environment.

      • SethSeth commented  ·   ·  Flag as inappropriate

        I too vote for this. Being able to lock an object you are working on so that other developers know that you are working on it is a must. We still use the product and like it a lot, but this would be a great feature to have.

      ← Previous 1

      Feedback and Knowledge Base