Ask HN: How do teams work with databases?

In my company we have 4-5 teams, 15-20 databases and 30+ services. When we start working on bigger features it gets harder for us to not break the other services that rely on the same databases.

We've talked about making each database be "recreatable" and spawning a new env. for each long lived feature, however getting to that point might be multi year effort. We also talked about doing multiple stored procedures for each iteration of the db, but that would mean we would all have to do a lot of extra work and that still doesn't guarantee we won't break a lot of services while in development.

So how do you approach database development in your company so you don't break things all the time?

p.s. any books/articles that can help guide us to improve our work are also appreciated.