Migration Based Deployment System

I’m searching for an option that the database keeps a log of the migrations (scripts) that are already performed. When I’m deploying new migrations it can simply look which migrations are already done (or set to not done) and continue from there.

When my colleague is then updating his database he can execute all scripts which aren’t yet done on his database. This will results in his database being completely updated while saving, updating of removing the data (This is done without a compare (just script executions) which is great, because his changes aren’t removed). Then he simply add a new migration script with his changes as the newest script.

Isn’t there an option like this that devart adds an extra table to my database which keeps the executed migration scripts? And maybe a bit that we can set to zero to execute a migration again?