Database "version control"

I enjoyed this Coding Horror blog post and the associated comments. If you went by the post title alone, you might get a distorted view of what it's about. (i.e. Should I be able to roll back any database transaction at any point in the future? No, that's not what we're talking about!)

What Coding Horror is talking about is keeping your database schema under version control. This begs the question: is anyone not keeping their database schema under version control? Hell, I'm a frickin' newbie, and even I figured out (by myself) that I should have a couple of SQL DDL scripts that allow me to recreate my database schema. Those scripts are easy to load and diff in version control. And, it makes deployment easy -- just send the scripts off to your DBA.