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.

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.

  1. Please re-add the condition feature in the migration script in the packaged script

    SQL Change Automation idea: Please re-add the condition feature in the migration script in the packaged script since this was working before in ReadyRoll.

    More details in https://productsupport.red-gate.com/hc/en-us/requests/133672?page=1

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Set CodeGuard Checking Default to Off

    We use TeamCity and there seems to be no way (or no simple way) to disable CodeGuard checking. It's not really useful there for us (and we use SonarCloud which has nice integration/quality gates for GitHub).

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. DevOps plugin - Options to disable cleaning and rebuild

    DevOps plugin for tSQLt is cleaning and rebuilding database prior to running tests.
    Since test step usually follows a build step, that just cleaned and rebuild the database, there's no need for the test step do it again.

    Add parameter for disabling this?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. PackageVersion SQLCMD var should be set in PackageScript.sql when calling Export-DatabaseBuildArtifact

    Since we are already required to provide a PackageVersion parameter to Export-DatabaseBuildArtifact, I would like to see the PackageVersion SQLCMD variableset to that input value in the PackageScript.sql with in the build artifact.

    I would also like to see a new parameter for Invoke-DatabaseBuild, SQlCmdVariables, that wouldd allow us to pass in ReleaseVersion, PackageVersionm, and other SQLCMD vars that would be set in the PAckahgeScript.sql (and the PackageScript property of the returned BuildArtifact object.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Visual Studio Improvements

    I would like to see a few filters added that would make working with the Main table of objects easier.
    Filter by Object type: Table, stored procedure, etc
    Filter Object name: Ability to type / paste in a partial name.
    Filter to show tables with data. With data, without data, all

    I have a project with 575 objects and growing. My main reason for this is working with tables that include data. It is hard to tell which tables include table data. We need a quick reference to see which ones are under source control. As I go through and…

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. New powershell cmdlet: Export-DatabaseDocumentation

    I would like the option of creating my documentation outside of a database artifact. I would rather it not be embedded in a nuget or zip file with the deployment files. Currently the object created by New-DatabaseDocumentation can only be passed to New-DatabaseBuildArtifact. It would be great to just pass it to a new export cmdlet so it can be saved to disk.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add SqlCmdVariable parameter to Build procedure

    We would like to add SQLCMD variables to our SQL Change Automation projects to denote whether a deployment is applying to a Local environment or to our production pipeline (isLocalDeployment). Our thought for how to do this with the least amount of changes required was to default the variable to be isLocalDeployment = FALSE. This would mean that if we are doing a deployment to a local developer database we would run additional scripts to configure that environment, but once the project is deployed into our normal production deployment pipeline those scripts would no longer run and we wouldn't have…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. file group

    DLM Automation (and related, SQL Compare) needs to have support for custom filegroups, as well as other database-level setting definitions. Right now, any database that has a single object that references a custom filegroup fails validation against anything other than a pre-staged validation database with a bunch of the settings already baked in. There's no scenario in which the product can create a new database, from scratch, if there is a dependency on these objects.

    The DevOps story the products are trying to tell breaks down at scale if the whole of the database isn't manageable from the tool.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. ReadyRoll .sqlproj please sort the ExcludeObjectsFromSync section

    The ReadyRoll .sqlproj file is a regular bugbear for merge conflicts when different work streams combine to create a release. We have old databases with many legacy objects that no longer compile, and these have to be included in the ExcludeObjectsFromSync section. ReadyRoll appears to update the entries in this section in random order. When resolving merge conflicts this makes it very difficult.

    Please sort the ExcludeObjectsFromSync section in name sequence, or in name within object type to make it easier to resolve merge conflicts.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Offer environment variable as a Build Package Version Number source

    For the build package task it would be helpful to offer an environment variable as the version number. Same options as the nuget package task that's already available for standard nuget package builds.

    Many people generate version numbers during build, so we cannot know the build number before hand.

    Another option that would be nice is a substring of the build number, which is where many people append their version numbers.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Build Plugins - Ignore Static Data

    When performing a database build for Continuous Integration Plugins can we have a setting to ignore static data?

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add AzureAD authentication

    Add the ability for the DLM process to connect to Azure DBs using Azure AD authentication. To me this makes sense as you have already added this functionality to SQL Compare.

    We are moving to Azure and this is the preferred way for us to connect to these databases. Without this functionality, we have to setup a SQL user for our VSTS user so that the DLM process can deploy the database

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Ignore Static Data on VSTS Online Build

    It seems like recently the feature of including static data during the build process was added. However there seems to be a bug with it and I've opened a ticket for it. Also, some of us may not want to always push our static data. In our case we have our base data for a new environment and we want VSTS Online to have an option to TURN OFF static data during the DLM Build process in VSTS Online.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Expose SQL Multiscript functionality via DLM Automation cmdlet

    I need to execute Use-DlmDatabaseRelease against hundreds of databases per server (times a dozen or more servers). None of the Powershell multithreading approaches I've found matches the speed of SQL Multiscript. It would be a huge performance boost to be able to feed a Use-... statement or a generic script block to a Multiscript cmdlet for swift parallel handling.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

SQL Change Automation

Feedback and Knowledge Base