It never is. 🙂 There are other options out there, too. DBUp integrates more into the coding area and usually is written to include rollbacks as well. DBDeploy - stage a bunch of scripts, but let it handle pushing them. I think there's a way to specify rollbacks there as well, but never tried to use it too heavily. I don't know how well either of those would work if you ever needed to cherry-pick DB changes. That gets tricky very fast.

Similar to SSDT - Red Gate has SQL Source Control. If you're in the Red-Gate environment, that can be useful. You will need to make sure your local/Dev database is set to the right schema to get the changes captured correctly using SQL Source Control if I understand how that works. Switching branches could be problematic there unless you're editing the files themselves.

I'm writing from my experiences so definitely biased towards SSDT/Datadude, but I realize it's not for everyone and it can be tricky to get started. Once you get set, though, it's well worth the effort.