Skip to content
← SQL Change Automation

How can we improve SQL Change Automation?

SQL Change Automation

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Add SSC database project

The SCA database project only supports the migration approach. I would like to have is support the SSC (state/model approach) style project. My Devs are far more comfortable using Visual Studio to interact with the DB than SSMS+SSC. As long as the correct script is in source control - I don't really care how it gets there and is updated (SSC or VS).

1 vote
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Paul Hunter shared this idea  ·   ·  Report…  ·  Admin →

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
  • AdminKendra (Admin, Redgate) commented  ·   ·  Report

    Hi Paul, thanks for this suggestion.

    We have recently added the ability for a "Hybrid" development model where a SQL Source Control project may now be considered the development "source" for a SQL Change Automation project.

    An article on the hybrid model is here:
    https://www.red-gate.com/hub/product-learning/sql-toolbelt/a-hybrid-approach-to-database-devops

    I believe that this meets the spirit of your request, so I'm going to mark this one completed. We very much welcome your further feedback on this and whether the hybrid model meets your needs, or if you have further ideas to refine it. We do have plans to iterate on this model further in 2021.