Published “Database Schema Versioning” article
Versioning database schemas is a genuinely difficult task. Being difficult, it is often left until “later” in projects, which ultimately gets converted to “never”. This leaves a huge gap in making your application deployments predictable and low risk. Today I published an article describing how this gap can be closed.
Storing the source code of an application in a version control system is nothing controversial. It is a universally accepted practice. There is a small detail, however, which makes the version control of applications difficult. I am talking about the database schema. If the application has to manage state, doing it in a database is a very common approach. We must consider the database schema as part of the source code of the application, and as a consequence, it must be stored with the rest of the source code.