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.

9 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 →

    3 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...
      • Robert NowakRobert Nowak commented  ·   ·  Flag as inappropriate

        @David Atkinson I'm also interested in more specific details of hybrid of SQL Source Control and ReadyRoll.
        I use Entity Framework but i need to manage changes using SQL Source Control and update EF classes.

      • NathanNathan commented  ·   ·  Flag as inappropriate

        We purchased SQL Source Control (as part of SQL Developer Bundle) with the promise that it would work in the future with systems like GIT/Mercurial branches more natively. The eventual use of working directories still does not fulfill this promise fully, so it's disappointing to see RedGate roll out a totally separate ReadyRoll that supposedly works better across branches and commits, but isn't even included in the SQL Developer Bundle.

        In the ReadyRoll FAQ, they compare to SSDT and say that ReadyRoll is better than SSDT because SSDT is state-based and ReadyRoll is migration based (http://www.red-gate.com/products/sql-development/readyroll/faq#faq-3). The migration scripts in SQL Source Control are not the full DbUp, so it's still very much state-based. The FAQ doesn't even compare to RedGate's own SQL Source Control tool.

        The two are so similar, they really should be the same product.

      • 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