About ten years ago I worked at a company with a DBA who saw gatekeeping everything database related as a form of job security. But he also complained bitterly about how often he was interrupted. Even simple things like adding a column to a table required his participation. When developing, these types of changes are frequent and often blocking, so creating something like a ticket queue wasn't a good solution. Our manager was not only aware of the situation but seemed entertained by the inherent conflict it created.

Since going through that extreme case of blocking through gatekeeping, I try to keep my eyes out for ways to allow other to self-service as much as possible. It's not possible to eliminate all interruptions but it's often worth spending a bit of time examining how the interruption could have been avoided in the first place and if similar interruptions are likely, invest in creating something more self-service. At least in the DBA situation I was in back then, simply allowing developers to have local database or even control over development database on a dedicated database instance would have eliminated most of the blocking and interruptions.