How can we improve SQL Source Control?

See incremental changes made before committing

When working with an object, there is a chance that another developer has made modifications as well since many developers work off of the same database.

When committing, it would be nice to be able to see a history of modifications. Each time an object is modified (F5) take a commitable snapshot of that object.

When a developer goes to commit, they could see the different times an object was modified and commit all at one time or commit the individual changes made over time. Doing a commit will roll-up all previous commits made.

Example:
Day 1: Dev A: Adds Parameter
Day 2: Dev B: Sets Default Parameter value
Day 3: Dev A: Changes the default

Dev A forgot to commit their initial change, but would like to log a commit for it.
Dev A could open up SQL Source Control, find that Pending object and "commit" his Day 1 change to SQL Source Control WITHOUT affecting any current changes made.

This isn't a great use case for an example, I'm sure others can come up with better examples.

You would need the ability to use Modification Date for the commit date, see my other suggestion:
https://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/19443883-option-to-use-modification-date-as-the-commit-date

14 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…)
    Aaron BaumanAaron Bauman shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    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...
      • Mike OxwellingMike Oxwelling commented  ·   ·  Flag as inappropriate

        I'd have thought that it's a dev's responsibility to pull back before committing changes, at least that's how I've always worked. It would be nice to have fail-safes in place but I imagine it would be a significant overhead.

      Feedback and Knowledge Base