I work regularly with a number of customers on improving their database change processes. This has been the goal of Redgate's Database Change Management over the years, helping database systems work more like application software with DevOps principles. The idea is to move quicker, respond better to demands, while providing safety and governance. A database is a stateful machine, which is a challenge to evolve and maintain, but with good data modeling, testing, code analysis, and automation, your database change process can coexist with your application software.
That being said, most of the solutions for managing database change focus on the database itself and everything inside it. After all, that's where the data is. I understand people wanting to solve that problem, but there are plenty of things that need to be managed for a database server (or instance for MSSQL) outside of the database. We have security, configuration, and in the case of SQL Server, jobs. That might be the number one request is a way to manage jobs across systems.
Podden och tillhörande omslagsbild på den här sidan tillhör
Steve Jones. Innehållet i podden är skapat av Steve Jones och inte av,
eller tillsammans med, Poddtoppen.
