Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control: Initial Setup

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Red Gate Source control should only need one workspace

Red Gate Source control should only need one workspace. Is there a specific reason Red Gate creates multiple workspaces per database linked? This is creating a mess of my workspaces.

58 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Jason Williams shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • T Walstad commented  ·   ·  Report

    Any feedback from redgate on this? This has been going on for years. From what I can tell this was an issue in Version 3 that was supposed to be fixed. Why are we still seeing this issue with the current version. I have over 500 workspaces created from my SQL devs!

  • Michael Hotek commented  ·   ·  Report

    I'd agree that this is a mess. I have 1 workspace already on my machine that has our entire TFS structure pulled into it. I then hook up SQL Source Control and I suddenly have 148 additional TFS workspaces created on my machine (74 databases). Every database I add to source control produces 2 more workspaces. As a TFS admin, this is a ridiculous mess.

  • Dwaine Wright commented  ·   ·  Report

    Wow, I didn't even notice this until I read the post!!!

    First, I'm concerned that you've added the comment "Used by SQL Source Control – do not modify" to each workspace. Please explain. It it means what it says, that's bad form in my opinion. Once code is in TFS, why would a workspace matter at ALL? I'd like to delete them all! Are you suggesting that would break SSC functionality? You aren't even working inside of VS!? If my dev machine died and I had to build from scratch? A new dev starting from scratch and pulling the branch... they have no worksapce to start with.

    Second, I'm confused, why even use a workspace? AFAIK, TFS workspaces should be defined and controlled by the user, NOT a TFS client. The SQL folder/file structure should live under and play nice using the same model. If you need a scratch area, you have at your disposal USER\AppData\ or ProgramData, which are the only appropriate places an app should save data as per industry standards. Please explain.

  • Kieron O'Connor commented  ·   ·  Report

    This also causes a problem if you use the gated checkin feature in TFS. When you have to reconcile the changes, it asks you to pick a workspace. This would normally be fine but 12 local databases source controlled.

  • Ben Sproat commented  ·   ·  Report

    It should be able to use one workspace for all linked databases and just use an appropriate folder structure.