Change is hard. Change in software is even harder, so with any software project, engineers set up a process for change management using a series of tools such as Git, GitActions, AzureDevOps, Jenkins, CircleCI, Terraform, and many many more. However, missing from these toolsets is the core concept of managing database-level changes over time. This becomes a different animal because while most software code is stateless, databases contain large amounts of state that is crucial to keep intact as database functionality changes and grows with a business. In the Microsoft world, Visual Studio and SQL Server Data Tools were pretty good at having an end-to-end database management and deployment framework to ensure your database could deploy changes from multiple teams without breaking in production. But what about the rest of the world? This is where Liquibase comes in.
Project: Analyzing Students??? Mental Health in SQL
Can attending a university in a foreign country impact one’s mental well-being? In 2018, a Japanese university with a diverse student body conducted a…