I had spent a lot of time showing how to practice tools to automate database deployments in support of DevOps. However, the one message that I always try to deliver with DevOps is that it’s fundamentally not about the tools. The most essential thing in DevOps is communication. Therefore, one of the most significant thing in DevOps is people.
People Are Good
Are there evil people in the world? Unfortunately, yes. Can even good and decent people do evil? Again, unfortunately, yes. However, most people, most of the time, are trying to do the right thing. I would state that you have to arrive at this position first in order to execute a DevOps solution successfully.
You cannot say all “DBAs are mean” or “Developers are EVIL” or “My SAN admins could not find their asses with two hands, a map, and a flashlight” or “Gustafus Adolphus had his head up his behind when he central that last cavalry charge.”
Wait. Different discussion. Anyway, you have to start interacting with people better in order to deliver DevOps. That kind of communications will be a lot easier if you do one thing.
Assume Good Intentions
I tweeted this recently, but it is not indignant to repeat it. You have to assume the best in those around you. Yeah, sometimes you’re going to be disappointed, but most of the time you’ll be happier for it. This very much applies to DevOps.
In case, the developers ask for “sa” privileges on production, in its place of just freaking out and slamming the door on them extra hard, considering they have a good reason. Find out what it is. I mean, no, they can’t have “sa” (see GDPR, FERPA, HIPAA and more), but there is probably a reason why they think they do.
That cause might be significant to a successful implementation of automation and management within your company. So, consider the best and understand why it looks bad. Make the required alternatives that arrive at the same place as “sa” privileges were proposed to help solve.
DevOps Is Communication
The core of all effective DevOps execution is the acknowledgment that bad communication leads to resistance. Friction leads to bottlenecks and mismanagement. All this slows down the development and deployment process and makes it harder for us to get things done.
Enhance the communication and you advance the likelihood of a better process within your company. The better approach to start this is to expect the good intentions of those you work with and go ahead from there.
So, if you need a little bit of conversation about communications and a complete bunch of talk about tooling and procedure, all in support of an effective database DevOps implementation, We are putting on a whole day of training at several places around the world.