How can we improve SQL Source Control?

workspace per database, instead of per user account

At current we have SQL source control running in a remote environment. However, a DB - SVN link is stored for each user account, and is not transparent to the other developers.

Worse yet, with each developer having their own workcopy in their local profile, the same data will be duplicated several times. Also: conflicts will arise since each workspace updates on its own, while the DB might already be updated from another workspace.

Therefor: Suggest to keep 1 workspace per DB, to prevent issues of multiple workspaces or repositories linked to the same DB.

7 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…)
    SartriXSartriX 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...
      • MarbryMarbry commented  ·   ·  Flag as inappropriate

        This makes a lot of sense, and was initially how I thought the "shared" model worked. We created a standard location in TFS for the repository, so we can at least know where to link it to.

        It also makes developers who are somewhat resistant to using new products, however easy to use, less liable to actually utilize it if they have to manually add each DB themselves. A minimal change to workflow would help to ease the transition.

        If someone else adds a shared DB to source control, I should really be able to see that as being under source control without having to do anything else myself I would think. It would be very useful to at least have this option.

      Feedback and Knowledge Base