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.

49 results found

  1. Include the name of the object that failed to deploy in SQL CI error messages

    I want to know which object failed to deploy when a SQL Server error is thrown during validation.

    6 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Reduce Unnecessary Statements In Deployment Scripts

    When deploying database changes (we are using the plugin for Octopus Deploy), it would be useful if there were not so many superfluous statements included in the deployment script. This is particularly prevalent when deploying static data, it appears that the deployment script will drop constraints on a table where it is updating table whether the constraints are material to the update or not. The code seems to be going down the path of least resistance which makes for bloated and hard to read code whereas I would like it if the code were as lean as possible to allow…

    0 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Team City Plugin - Timeout Field

    During the build portion of our pipeline, builds occasionally fail due to timeout while inserting static data. There is a work around where you open up the powershell scripts underneath DLM to specify the timeout, but it would be much more useful to have this as a field in the Team City plugin.

    I'm sure other plugins could use this as well.

    4 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. Incorporate new/improved SQL Compare differences views into DLM Automation Changes.html

    The latest version of SQL Compare introduced improvements to the SQL View as well as a new Summary View, as detailed here: https://www.red-gate.com/hub/product-learning/sql-compare/sql-compare-summary-view

    It would be good if the Changes.html file generated by DLM Automation could also display the results in the same format so that it is easier and clearer to see the changes that are being deployed.

    It would also be better if changes to static data were broken down so that for each static data table modified it explicitly states which records have been added/removed/modified/remain identical.

    6 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Support publishing custom schema names to DLM Dashboard

    Please make it possible to specify a custom schema name when publishing a build to DLM Dashboard. The current implementation only supports using the nuget package version which has restrictive formatting rules, so for example it does not work for apps which use a four-part version number.

    9 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Add database connection for database testing in VSTS extension

    Currently if you use the VSTS extension you can't ask it to run Tests against a database connection. If you allowed this then it would provide more flexibility.

    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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. Add the option to skip delete operations

    It would be good if you could skip delete operations when deploying database changes automatically. This means if we update our application code and database changes then old versions of the application code can continue to use the old database functionality.

    2 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Disable check constraints

    When importing static data on a sync operation, I'd like the option to disable (and re-enable afterwards) check constraints.

    At the moment the only option I have is to ignore them which means my CI database is not built correctly

    3 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. As an build engineer I'd like to be able to override the package version number in the TeamCity plugin

    We are currently using GitFlow for a small POC and have hit an issue as we are unable to use a NuGet safe version number for our package name without going through some hoops.

    Adding support for an optional version number field in the SQL CI TeamCity plugin would be a nice addition and allow us to drive this from another variable.

    5 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…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
1 3 Next →
  • Don't see your idea?