How can we improve SQL Source Control?

share information about environment between red-gate tools

SQL Source Control and SQL Prompt may not know about an environment (i.e. a developer not having access to staging or production server) and there's not really a facility in either tool to store information about the version of any environment.

Thus, SQL Source Control has to ensure backward and forward compatibility when creating migration scripts - which then triggers Code Analysis Errors in SQL Prompt...! It is a mess to clean up, and frankly a waste of time.

I suggest a feature where I can define my environments in the Tab Coloring in SQL Prompt including a listing of what version things are and then have this information shared around.

Another possibility is some "future shared utility" where it has useful information that it passes to each tool.

1 vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Hans shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base