How can we improve SQL Source Control?

If user has SQL Prompt installed, apply formatting automatically to SQL prior to checking in

Say for example that View was created manually using formatted code (from SQL Prompt for instance) and checked in, the original version in Source Control is nicely formatted and so on. However, someone then comes along, makes a small change inside mssmsand hits save on the view, the code is mashed and FAR more lines are detected as being different when that revision is next checked in. When you script items for comparison to SVN, formatted versions should be compared. Obviously if you want to check in a layout change, there will need to be an option for that too.

46 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…)
    Jordon PillingJordon Pilling 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...
      • SimonSimon commented  ·   ·  Flag as inappropriate

        This provides a great way to standardise code styles; trying to clean up a legacy database prior to adding it to Source Control could be a monumental task, but if the option were there to automatically apply the rules in SQL Prompt (which ideally would already be shared by the developers anyway) would mean the entire code base could easily be standardised.

        It's 'one less thing to have to remember' too.

      Feedback and Knowledge Base