devops

State vs Migration for Database Source Control - decide based on one question

State vs Migration for Database Source Control - decide based on one question

One controversial topic in database development is how to properly store and deploy database changes.

This is generally described as choosing between two options, which are approximately as easy to understand as Greek philosophy:

  • State based - A Platonic view of the database as a snapshot of a set of forms in a given state at a point in time
  • Migrations - An Aristotelian view of the database defined as a series of scripts which generate change over time
Why To Do Some of the Grunt Work, Even If You Don't Have To

Why To Do Some of the Grunt Work, Even If You Don't Have To

Part of this past week I’ve spent doing a new SQL Server 2008 R2 installation and configuration on a Windows 2008 R2 cluster. I  haven’t done an install end-to-end in quite a while– I have teammates who take care of it while following our installation checklist document.