How can we improve SQL Source Control?

add native support for Seapine Surround and...

Currently the XML hooking method for non-native Source Control Systems is not very usefull for Surround SCM. I would like to suggest maybe adding more support to it. Also when linking a database to the Source Control System It would be nice to have the option to link tables, stored procedures, views..so on to specific repositories, instead of everything going into the same place. Also to be able to rename the default folders that the tool creates in the working directory would be nice in case there is a special naming convention(for instance procedures instead of stored procedures). A moule to create a deployment list...let's say you have 100 objects but you want to release just 10 of them, an option to create that list with priority of whch one goes first and also being able to export that list to have it like a log of the releases for the auditors or for department order.

56 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…)
    Alejandro CorderoAlejandro Cordero 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...
      • Michael ZordeMichael Zorde commented  ·   ·  Flag as inappropriate

        We need full/relative(to the working folder) file path for the check-in method, otherwise the system will check in on the working folders root.
        We need variable of the repository/folder.

      Feedback and Knowledge Base