Skip to content

SQL Change Automation

SQL Change Automation works with your CI server and release management system, so you test, build, and release your database alongside your application code. To find out more please visit our website.

We need your help to shape SQL Change Automation into a great product that helps database professionals. We’d love to hear about your feature ideas and suggestions, so please enter them below.

If you have any questions or need help with SQL Change Automation, please visit our support forums.

SQL Change Automation

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve SQL Change Automation?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

4 results found

  1. Sell it separate and not part of an expensive collection

    Sell it separate and not part of an expensive collection.

    60 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…)
    0 comments  ·  Admin →

  2. Deploy static data in commit order

    Static data should be deployed in commit order rather than at the end of the deployment script.

    It is currently impossible to write a migration script which depends on static data as the static data will not exist at the point the migration script runs. The migration script can't insert the static data it needs as deployment will then fail later when inserting the new static data which now already exists.

    15 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…)
    declined  ·  3 comments  ·  Admin →

  3. Change DLM licencing

    Please re-visit and change your stupid, ill thought, money grabbing licencing on DLM Automation.

    Having licenced SQL CI coupled and individual SQL Source Control licences all with maintenance on advice of Redgate sales we've been merrily using this until now. Needing to buy additional licences for SQL Source Control we are now hit with an eye watering quote to have to upgrade from SQL CI to DLM automation.

    Apart from the fact that the product recommended to us originally has been superseded twice with no contact from Redgate, there has been a sneaky shift to a per user licence fro…

    33 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…)
    2 comments  ·  Admin →
    declined  ·  AdminDavid Atkinson (Product Manager, Redgate) responded

    We have experimented with a number of different licensing models and the reality is that server-based licensing option did not make for a viable business.

    Instead, to cover the entry level market, we now offer Flyway Community and Flyway Teams.

  4. SQLCI to support Oracle

    Provide a version of SQL CI that supports Oracle

    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…)
    0 comments  ·  Admin →
  • Don't see your idea?