Everyone who has successfully implemented Continuous Delivery in their organization talks about how it dramatically improved the way they deliver software. What they don't tell you though, is how they managed to continuously deploy their SQL database. Surely the vast majority of applications and services need to have one, and yet, few ever mention it in the CD discussion.
It seems that the good old SQL database is often left out of the agile software development house party. Why is that? Are the tools not mature enough or is the relational model simply too rigid to fit in the fast-paced ever changing world of Continuous Delivery?
In this session we'll look at the challenges of continuously deploying a SQL database. We'll explore issues such as packaging and versioning, handling schema changes, migrating data and recovery. What tools do we have at our disposal? What strategies can we put in place to prevent us from having to bang our heads against the wall when something goes wrong?