"There are good techniques for modifying our objects, and helping to ensure we don't break systems, but we often do need some cooperation and collaboration with application developers to implement those changes. Much of DevOps avoids talking about the database, but we shouldn't. Instead, we ought to embrace database refactoring patterns, both at the database and application levels, ensuring that our systems can survive for as long as we need them while adapting to the changing requirements of our clients."
Well before the current term DevOps became popular our DBA group was essentially the only source for SQL code and stored procedures on which all our applications were based. There was essentially zero embedded code in the applications. Besides the design and development of databases, we provide the application developers with hundreds and hundreds of stored procedures we created and tested on development systems, which were then released to QC teams with front-end application code for final testing. DBA's 'owned' the code libraries and all SQL that was released to production.
One of the best days of my IT career was the day I told my boss if the problem was so simple he should go fix it himself.