How can we improve SQL Source Control?

Allow changes to comments in code to be committed

SQL Source Control doesn't recognise changes to objects when the only change that has been made is in comments. The change is marked in object explorer when initially made, but clicking refresh in the source control window then ignores the change and removes the indication that the object has changed. There doesn't appear to be any setting to remove this filtration. The only other option is to alter the object's functionality or definition, commit, then change the definition back and re-commit. This is inherently risky, and should be unnecessary.

We use comments as a key part of our system documentation, and I'm sure they are integral to many other developers too, so it makes no sense not to be able to commit these code changes.

1 vote
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…)
    JoshJosh shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    2 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...
      • JoshJosh commented  ·   ·  Flag as inappropriate

        Further clarification - this issue only appears to occur where the comment is not in a BEGIN... END block within the object definition. E.g. as standard our procedure headers sit between the 'CREATE [object]...' and 'AS' lines and changes are not detected by Source Control

      Feedback and Knowledge Base