There's an article at Forbes about the Five Things Business Leaders Should Know about Databases. Disclosure, it's by my boss, but I think it's still a good read. These are points we've learned from research and work with customers and prospects at Redgate Software. These points come from you, as well as from executives with whom we work, but there are so many people in organizations who don't think about the complexity of data, so it's a good one to pass along.

The five things are (if you don't want to read): data is growing, getting more complex, there are multiple database platforms in most estates, teams struggle (duh), and data is a business issue. Most of us know about the fourth one, often because we may feel overloaded with work. We might also feel a lot of stress in trying to keep up with not only the workload but also trying to learn more to support the ever-growing variety of systems it seems our employer wants to put into production. I regularly talk with customers whose developers keep wanting to try out a new, shiny database platform in the cloud (or add new features from their existing platforms).

Wait, not try out. They've already deployed some production data there and now want other developers or operations people to work with their system.  Often lots of the staff isn't familiar with the platform or feature, even the people who decided to implement it. Is anyone familiar with that situation?

The digital transformation and importance of software isn't lost on most executives, but I find far too many that don't place the same importance on the data that powers their software or the database platforms that support all software. Data is important, and ensuring it is available to software, protected, secured, and available is critical. That also means that the process of developing and managing the database portion of your software matters.

I think Database DevOps is important, but it's not a panacea to buy a product. I'd love to show you what Redgate Software can do here, but the main thing I stress to clients is that you need to get your database development into the modern era and match what software developers do. That means a smooth process, with version control, that ensures you deploy changes in a way that doesn't impact customers.

This doesn't mean just go faster. This means bringing along data modeling, good architecture, and performance testing. Those are the same things we've been doing (or should have been doing) for decades, but we need to ensure these are still a part of whatever process we choose and included in any automation we implement.

Pass the article along to your management, and be sure they understand that all these points are important. Particularly the fourth point because if your staff isn't supported and trained, the rest of the business will suffer.