You may also like

• 

  Article

  New in Flyway: Pre and post deployment scripts for state-based deployments via callbacks

  Flyway provides a lot of flexibility for releasing database changes in a safe and repeatable manner. Earlier this year, we added the ability to automate state-based deployments. This means the structure of the database is defined in version control and Flyway handles updating a target database to match it. The Flyway comparison engine does all

• 

  Article

  Using Flyway Teams with SQL Change Automation PowerShell Cmdlets

  Use Flyway to run your database migrations, each time automatically creating a SQL Change Automation release object to provide object-level scripts and a build script for the new version, along with change reports and code analysis reports.

• 

  Web Panel

  Accelerating Digital Transformation: The Role of Automation in Database DevOps

  Across every industry sector, Technology teams are under pressure to release features faster and deliver value to customers sooner. Often the database is excluded from the software delivery process, increasing the risk of failed deployments that negatively impact customers. To overcome this challenge, development and operations teams rely on solutions like Flyway to bring DevOps

• 

  Article

  Searching Flyway Migration Files using Grep and Regex

  This article demonstrates a cross-RDBMS way of searching through a set of SQL migration files, in the right order, to get a narrative summary of what changes were made, or will be made, to one or more of the tables or routines within each migration file. Getting these summary reports, even from a set of SQL migrations, isn't difficult, but having a few examples makes it a lot quicker to get started.

• 

  Article

  Exploring the Flyway Schema History Table

  Flyway uses a schema history table to track the version of each database, recording in it every versioned migration file applied to build that version. It's worth understanding exactly how Flyway uses this table, the possible dangers of moving it to a non-default location and how to do it safely, if required.

• 

  Live training session

  Bare Bones of DevOps in AWS

  In this session Grant Fritchey introduces the absolute baseline needed to start your database DevOps journey within the AWS ecosystem. He starts with how you can get your database into source control and ends with the start of a Continuous Integration (CI) process. These are the fundamentals of any extended DevOps process including CI and Continuous Delivery (CD). With the fundamentals in place, building more advanced processes is simply a matter of the labor to build on that foundation.