Yup, we did. The rationale behind removing it was that it was too hard to figure out how to integrate it, but somebody (and me) helped out so problem was evaded.
Actually the DBAction is quite smart as it will back off if there are too many connections hitting the DB, thereby increasing performance under load instead of failing with timeouts. Adapted from @huntc predicated action...