How can we improve SQL Source Control?

ReadyRoll integration with Source Control

ReadyRoll looks great but one of it's downsides is that you have to use Visual Studio. If mostly work gets done using SSMS, then switching to Visual Studio is not a great experience.

Both ReadyRoll and SQL Source Control use the same comparison engines, they both output objects as files on disk and support migrations.

To satisfy both worlds (making great experience when using Source Control on SSMS) and have a proper way to automatically update databases from source control files using migrations (like ReadyRoll does), SQL Source control should integrate with ReadyRoll - after each commit, a migration script would be generated, .sqlproj created or updated. Sql Source control would need some additional options (such as pre-deployment or post-deployment scripts), shadow DB options for comparison, etc.

3 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…)
    APAP 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...
      • David AtkinsonAdminDavid Atkinson (Admin, Redgate) commented  ·   ·  Flag as inappropriate

        @AP Thanks for the feedback. When Redgate acquired ReadyRoll this was indeed the intention and we're actively researching how to unify the two approaches under a single tool. I will contact you individually about our early access program. If anyone else is interested in knowing more, please post vote and post a comment and I'll get in touch with you.

      Feedback and Knowledge Base