Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Auto checkout from TFS on modify of sql object. and show the object as checked out in SQL Mgt Studio

Auto checkout from TFS on modify of sql object, and show the object as checked out in SQL Mgt Studio for other users in case of shared configuration.

76 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…)
potla shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

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
  • vt commented  ·   ·  Report

    would be useful

  • Marc Baehr commented  ·   ·  Report

    We are using Vault but need exactly the same functionality

  • Moacir Mendonca commented  ·   ·  Report

    This feature is a must! I can not begin to understand how a source control tool does not have a checkout/checkin mechanism! Is that not a given?

  • Marty U. commented  ·   ·  Report

    This is a big deal of us as we are working to migrate to SSC. For a product to be focused on source control integration I would hope this would be at the top of the list for Red Gate to deliver.

  • Brad commented  ·   ·  Report

    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.

  • Anonymous commented  ·   ·  Report

    Yes. It defnitely helps developers in team to make sure it don't overwrite the changes.

  • Anonymous commented  ·   ·  Report

    This is definitely needed. We are deciding whether to purchase the SQL Source Control and this may force us to wait for this feature to be available.

  • Eric Wahner commented  ·   ·  Report

    This goes hand in hand with an explicit check-out of an object and should be configurable, just like most source control solutions. Obviously in some scenarios it makes sense and in others it might not. Code related objects makes huge sense, but maybe on filegroups and other objects where your production environment might not completely mirror your dev it might make less sense. For that matter let me choose which objects I want under source control.

  • FunkyDexter commented  ·   ·  Report

    This feature is an absolute must for us before I'd take the product up. I've had too many bad experiences with careless devs not bothering to understand the code their merging in to and mucking up other peoples changes to advocate the edit-merge-commit model. Checkout-edit-checkin might prevent parallel development but it's nice and safe which is a far higher priority for me.

  • AdminRedgate Administrator (Admin, Redgate) commented  ·   ·  Report

    The blue circle in the ObjExp just identifies local changes that have not been committed yet. v1 of SQL Source Control uses the edit-merge-commit model instead of the checkout-edit-checkin model. Keep voting here or http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/802123-tfs-exclusive-checkout-svn-lock if you need this feature.

  • Claes Wedin commented  ·   ·  Report

    In the Object Explorer a blue circle is shown on the object when you update an object in your database. Why is the object not shown as checked out i the VS Source Control Explorer?