There's no particular reason to keep a whole table for this, since all you really want to know is what version you're at. We use a UDF called VersionNumber tha

There's no particular reason to keep a whole table for this, since all you really want to know is what version you're at. We use a UDF called VersionNumber that returns an integer. When the continuous build processes a new database change script, that function gets modified to increment the value it returns. So you can always call VersionNumber() on any of our databases and know which version you're looking at. The builds actually use it to decide which scripts they need to run to get from where they are to where they need to be. You already have all the commentary you need in source control and in the change scripts themselves. I don't see a reason to duplicate it in the database as well.