Database migrations help to keep database schema versioned, by documenting database changes in source control. But how should you test if those migrations are correct and will work against production consistently? In this article we are going to explain how we test database migrations using Flyway as our database migration tool and Spawn as our database provisioner.
Spawn is a cloud service provided by Redgate Foundry. It allows you to create ephemeral databases on demand that can be used for both development and for testing in CI pipelines.
Spawn uses 2 components to work, and these should be familiar to anyone who has worked with Docker before. …
SQL Operations Studio is a modern, extensible developer/DBA tool for building and managing your SQL Server databases. SQL Search is a free tool provided by Redgate to search SQL across SQL Server databases.
We would like to share with you what we’ve learned and how we went on to build this extension.
When starting to build your first extension there might be a lot of concepts that are new to you.
Why Docker and Kubernetes?
Containers allow us to build, ship and run distributed applications. They remove the machine constraints from applications and lets us create a complex application in a deterministic fashion.
Composing applications with containers allows us to make development, QA and production environments closer to each other (if you put the effort in to get there). By doing so, changes can be shipped faster and testing a full system can happen sooner.
Docker — the containerization platform — provides this, making software independent of cloud providers.
However, even with containers the amount of work needed for shipping your application through any cloud provider (or in a private cloud) is significant. An application usually needs auto scaling groups, persistent remote discs, auto discovery, etc. But each cloud provider has different mechanisms for doing this. If you want to support these features, you very quickly become cloud provider dependent. …