WHAT ?
I'm working pretty much in an environment described in the article. Big bank, complicated database setup with multiple replicates and databases up to a size of ~25TB.
On a (pre defined) release weekend there are essentially two entities to be released: The application (obviously) and the database changes.
For any DB change a patch is created and tested through an environment of half a dozen instances. If bugs are found on already deployed db patches they are never fixed in the patch, but a subsequent patch (also tested through all environments) is created.
Needles to say that anything provided, which applies database changes is version controlled.
The idea to apply database patches manually is so damn outlandish to beggar believe.
Anybody doing this on a production database without a strictly controlled (and tested!) break-fix should be fired on the spot.