How is SQL Change Automation helping you? Share to win DevOps books.

Azure Devops - Change Automation - Release - Comparing data all of a sudden and no disk space

We use Azure Devops and have a Redgate SQL Change Automation: Release task (Task Version 4.*) which has been working fine for ages.

All of a sudden on Friday morning (4th September 2020 AEST), these tasks started failing, taking 16 to 20 hours, and seems to now be comparing data between the source artifact and the target database.  Previously, the task was only ever comparing the Schema and applying schema changes.

Fails due to disk space, as it is obviously comparing millions of rows on the target database compared to no records in the build artifact.  

Why is this all of a sudden comparing data in the release task?  Did the "SaaS" automation task in DevOps change a minor version?  Could not find anything in release notes.  New options available to change so it does not compare data?  A little bit scary if it automatically started to try and apply data changes also. 


Answers

  • StefanZStefanZ Posts: 5 New member
    I noticed a "Ignore static data" checkbox in the task setup.  Is this new?
    I have now checked it, saved, and released, and only takes a few minutes again.  Is it possible to get some information please on the above checkbox, and when that was made live?

    Kind regards.
  • This is caused by an issue in the latest version of SQL Change Automation Powershell which we are now investigating.
    To workaround this issue please specify a previous version of SCA PS on the Azure DevOps task (for example: 4.3.20234
    "Ignore Static Data" causes SCA Powershell to not compare and sync Static Data, that's another viable workaround since this issue appears to be related to Static Data.
    Sergio
    Product Support Engineer
    Redgate Software Ltd
    Please see our Help Center for detailed guides on how to use our tools
  • ViKeRViKeR Posts: 1 New member
    We have the same issue, but in this case with Octopus. We've now use the workaround by forcing the previous version when we encounter the issue, but it cost a lot of time and effort to change the settings. 

    Any update on the progress of the investigation @Sergio R ?
  • We're investigating but haven't been unable to identify the cause yet.
    Sergio
    Product Support Engineer
    Redgate Software Ltd
    Please see our Help Center for detailed guides on how to use our tools
  • HiralMHiralM Posts: 3 New member
    We have the same issue.  @Sergio R - can you please let us know when you have an update?

  • I can confirm that specifying the earlier SCA version is working currently as a work around for us.
  • HiralMHiralM Posts: 3 New member
    @Sergio R 
    - We see that a new version of SQL Change Automation was released yesterday - 

    4.3.20259 - September 15, 2020

    Improvements:

    • Updated SQL Compare Engine to 14.4.3.16730
    Is this the fix to the problem? 
    We have currently hardcoded all our releases to run on version 4.3.20234.
  • This issue has been fixed in the latest version of SQL Change Automation Powershell (4.3.20260).

    This version is now available from the Powershell Gallery so if you set the task to use the latest version it should pick it up.

    Sergio
    Product Support Engineer
    Redgate Software Ltd
    Please see our Help Center for detailed guides on how to use our tools
  • HiralMHiralM Posts: 3 New member
    @Sergio R 
    - Great!! thanks a lot :)
Sign In or Register to comment.