I saw this comment in a post a short while back. A reader said "I'm still trying to wrap my head around "devops" as it pertains to database deployment. ... how do you deal with those potentially dangerous/destructive changes without manually coding? ... what tools are there that help in that regard? That's what database developers really need. The only tools I've found that' [are] useful so far are experience and care."
We have some tools over at Redgate software to help with database DevOps, but there aren't any magic solutions that can alter your database in some way that doesn't impact users and preserves all data. In fact, if anyone claimed to have a tool, I wouldn't trust it because there are just too many variables in database deployments. I certainly wouldn't trust a tool with automated rollbacks. Ultimately, experience and care are needed to build better software.
And, by the way, DevOps doesn't solve deployment issues. All DevOps does is help you automate the tasks you'd run manually in a reliable, repeatable fashion. DevOps teaches you to learn from your actions (gaining experience) and experimenting with small changes so that your mistakes aren't as impactful (developing with care). DevOps isn't magic, it's good, solid, learning from what works and what doesn't, altering our habits, and striving to be better. DevOps is often just providing a reliable, repeatable way of automating the things you do manually now, not inventing new processes.
I do believe in DevOps and I think that it can work well, but it requires balance, commitment, and huge culture changes. Automating code deployment is easy with some tools. Getting people to write better code is hard. I can help with the former, and I try to help with the latter here at SQLServerCentral, but it's really up to most of you to make an effort to become better at your craft. Getting that to work in any size organization requires that your management supports teams learning to be better and tolerating a few mistakes here and there.
Many successful developers and DBAs have been practicing for many years (even decades) what the media and high profile companies have been calling DevOps for mere months. You can join them by looking to improve all parts of your software development pipeline through collaboration and automation. Just don't forget to also learn to write better code along the way.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
Write, format, analyze, and refactor SQL fast with SQL Prompt
Writing SQL is 50% faster with SQL Prompt. Your SQL code can be formatted just the way you like it, you can create and share snippets with your team, and with code analysis you get suggestions to improve your SQL as you type. Download your free trial
How to track every change to your SQL Server database
See who’s changing your database, alongside affected objects, date, time, and reason for the change with SQL Source Control. Get a full change history in your source control system. Learn more
Not having instant file initialization turned on slows down the process of adding pages to your database, because prior to allocating the data pages to your database, SQL Server needs to zero out the newly allocated pages. More »
Dynamic Management Views (DMVs) are a significant and valuable addition to the DBA's troubleshooting armory, laying bare previously unavailable information regarding the under-the-covers activity of your database sessions and transactions. More »
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.