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

  1. Currently when deploying clones from SQL Clone images, the database level extended property IsSQLCloneDatabase gets set to 1. It would be helpful to be able to see the image name the clone is created from.

    This would allow for handling "sliding window" scenarios in terms of phasing out out-of-date images when you have a weekly image created in a graceful/programmatic way).

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. We have a very modular structure, with multiple SCA projects all targeting the same database. Each module can (and are) be independently releases. Each module in turn actually consists of 3 SCA projects, the Database Module Project, the Tsqlt Unit Test Project, and the Tsqlt Release Test project (smoke/regression/reconciliation tests).

    it would be ideal to have cmdlets that lets us quickly create, in a programmatic way, projects with the settings we have for each of these (references, clone image baseline provisioning, semantic versioning, dataspace, migration log schema etc, filter file etc).

    Include tsqlt files in test projects would be a…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. The default script options for creating additional files and filegroups relies on the $(DefaultDataPath) variable. This value is given by the server.

    But: if you are using SQL Clone, using this value, you get orphaned files when the clone is either dropped or reset.

    If you place the files within the vhd of the clone however, reset and dropping the clone works as expected.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Hi,

    I would like to see a VS Code project option, with a much easier to maintain project file, potentially even splitting configurations into separate settings files using yml or similar.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. When maintaining a database, like to assign names to unnamed default constraints. However, generated script only works if the target database has identically named "unamed" default constraints.

    To add robustness to the script, I modify these to a short snippet that works on the schema+table+column. (Using a snippet in SQL Prompt to speed the process :)
    But why do I need to do this - after all it is replacing machine generated code?

    Here is the SQL Prompt snippet I use:
    >>>>>>>>>>>>>>>>>>>>>>>>
    DECLARE @cc NVARCHAR(1000);
    SELECT TOP(1) @cc= N'ALTER TABLE [$schema$].[$table$] DROP CONSTRAINT '+QUOTENAME(d.name)
    FROM sys.defaultconstraints d INNER JOIN

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. when working on a VS project that includes a SCA project it would be useful to allow the developer to "automate" the capturing of changes in their development database (e.g. connection string that is defined in the sqlproj.user file) through some form of automation either as:
    - part of a local build step (for example where a EF Core project has created and applied database a migration to a development database) that automatically generates and adds the new migration script to the SCA project; or
    - is triggered as part of a git pre-check-in command (e.g. SCA PowerShell?)

    It would…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Our Create a hot fix procedure is:


    1. Create and get a bug fix into master using the procedures for making changes

    2. Create a local hot fix branch from current/test or current/production annotated tag

    3. Cherry pick bug fix commit(s) from master to the local hot fix branch

    4. Run a full build, all automated tests, and all migrations

    5. Push the local hot fix branch to the remote repository

    6. Build & release pipelines are triggered

    This procedure will help prevent regressions due to developers forgetting to merge hot fixes to master.

    This feature request relates to step 2. The CI/CD release pipeline will…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. When the Hybrid Model is used (where state-based changes are managed using SQL Source Control) and SQL Change Automation draws from SSC as its Development Source, it would be great if SQL Change Automation could detect changes to static data scripts in SSC and automatically create migrations for them. As it stands, the SCA user must manually code those migration scripts. Not a huge deal, but it would seem like a natural capability to add to the Hybrid Model given the way it already nicely handles structural (aka DDL) changes made in SSC.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    While this item isn’t specifically on our roadmap at this time, we have plans to improve and evolve the hybrid model in our offerings in 2021, and this will be a good candidate for consideration.

  9. When using the Redgate Change automation plugin for Azure DevOps pipelines, I wish to be able to run the tests AND produce the code coverage.

    We can create the code coverage from SSMS, and it would seem to be available from Powershell, but it's not available from the Plugin.

    We wish to expose this so that we can add a code coverage quality gate on Pull requests.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. The name for localdb appears to be sqlchangeautomation + a guid. I'm using Azure Devops deployment using sql change automation, when I use an agent name that is longer than 4 characters and use localdb in the build, I get an error message that states there is a path error. The generated localdb name is in the pattern sqlchangeautomation + a guid. This causes by builds to fail because part of the path is longer than 256 characters when the product is putting the necessary object into the user temp directory. if the pattern for generating…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  11. Using the SCA SSMS plugin, the Version Control tab makes it very clear that you need to click "Push", but not so clear that you should commit changes before pushing. It would be helpful if it warned that you haven't commiited anything rather than just quietly saying "Push Successful".

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. The sqldoc executable has a filetype parameter that allows you to change the generated documentation's file type. Could you add the filetype parameter to the new-databaseDocumentation cmdlet to enable flexibility on the documentation type that is inside the build artifact? I realize that I could probably build the documentation on my own via the sqldoc command line, but I feel like if I'm going to just use the individual command lines it defeats the purpose of the module! Based on the initial pass I took through the schemaDocumentation object structure - I am optimistic that this is a reasonable ask.…

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Could you please add svn integration to Change Automation SSMS plugin.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Occasionally the only changes in a specific build is the addition to the PostScript post-deployment script. Since there are no schema changes, the PostScript change is not executed.

    Faking a schema change by adding a comment or something is a poor workaround in an automated CI process.

    A simple flag -AlwaysRunUpgrade to always run the PreScript and PostScript as part of the deployment would be ideal.

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Since there is no add-in for SQL Source Control for Visual Studio, there is no mechanism for effectively versioning changes inside Visual Studio.

    The SQL Change Automation Core (only currently available as part of VS 2017 Enterprise) provided a mechanism for maintain changes scripts that are fully integrated into VS Project (and therefore can be placed under source control as a part of the project).

    This combination is Developer focused (rather than dev-ops focus of full SQL Change Automation)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow project/assembly references to be nugets.

    This would allow better project/build separation and/or less staging work.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow a change script to run on Azure SQL Data Warehouse

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for this suggestion.

    In the year since your request, Redgate has acquired Flyway. Flyway is an automated deployment tool, and while it doesn’t offer help in authoring scripts or a full continuous integration process, it can help you automate deployments to Azure SQL Data Warehouse (now known as Azure Synapse).

    More information on flyway is here: https://flywaydb.org/documentation/database/azuresynapse

    Since this doesn’t offer the same level of full CI/CD support as in SQL Change Automation, I am keeping this request open for further comments and feedback.

  18. When deploying to HA environments with servers in multiple subnets, you get an error if the sqlcmd runs on the wrong one. Per support the functionality was added to the powershell but was not exposed to the plugin.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. In TeamCity plugin step "Redgate SQL Change Automation Build" build.version is being normalized to SemVer (for example 2.1 -> 2.1.0 or 2.1.0.0 -> 2.1.0).
    Because we use these nuget packages internally only we don't need to follow SemVer. It seems that Nuget team doesn't want to remove that normalization (https://github.com/NuGet/Home/issues/3050) so solution would be to create and use custom Nuget build. Thats how Octopu Deploy solved this issue: https://github.com/OctopusDeploy/Issues/issues/2898

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?