I saw a post recently from Grant Fritchey, Help Me, Help You, Deliver DevOps. In it, Grant shows that DevOps isn't making developers do everything, it isn't just giving developers more responsibility, and it isn't developers handling some of the operational staff responsibilities. It's about getting development and operations to work together. Hence, DevOps, not DEVops, or Dev ops.
In the post, Grant also links to some fundamental failures from companies that supposedly have adopted DevOps processes. Companies like Gitlab and Amazon. There are plenty more examples, which certainly make some people question whether DevOps is better than other methods of building and deploying software. How are the VSTS issues different from the Knight Capital debacle?
In some sense, they aren't. In many cases, we've had a software issue that affected customers. People were upset, services weren't delivered, and it's entirely possible that revenue was lost. However, one of the things that I think differentiates DevOps is that developers and operational staff can troubleshoot and determine a root cause much quicker. Since the entire commit, build, test, release pipeline is instrumented and documented, your staff can quickly determine what new items might have caused an issue. If it's not a new item, they can also quickly determine if that's the case.
However, once you've placed your system in production, DevOps doesn't ensure that your HA (High Availability) or DR (Disaster Recovery) preparations are adequate. Those are still the responsibility of your Ops staff, but by using DevOps, and storing configuration as code and provisioning your systems in all environments the same, hopefully you've taken advantage of this to actually ensure you have tested some HA or DR features in an environment outside of production.
However, DevOps isn't prescriptive advice. DevOps isn't a particular process or a tool that you use or install. DevOps is about learning and improving over time. For different companies, this means you'll be at a different stage in your DevOps maturity than other companies. Some have complete deployment processes, but limited instrumentation and monitoring in production. Some have tons of data and deploy code perfectly, but no HA. Some have great HA, but poor deployment processes.
DevOps is about constant improvement and advancement to make your software development (Dev) and deployment (Dev and Ops) and monitoring/management (Ops) better over time. This might not prevent human error, or even code bugs, but DevOps should mean you make fewer mistakes, less often, and learn from them to avoid repeating those issues.
The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music.
NEW SQL Clone - version 1 now available!
Create copies of production databases and SQL backups in seconds and save up to 99% of disk space using SQL Clone. Redgate’s new tool removes much of the time and resource needed to create and manage database copies, allowing teams to work on local environments to develop, test and diagnose issues faster. Try it free.
SSIS was not originally designed with automated deployment in mind. However, any database that uses SSIS projects and their packages needs a way of scripting the deployment of them if the database is to be deployed rapidly, or via a build server. Nat Sundar shows a technique that can be extended to manage the scripted deployment of SSIS projects. More »
Redgate just launched SQL Clone, a new product that can provision copies of databases in seconds. By copies, I mean... More »
Question of the Day
Today's Question (by Steve Jones):
What keyboard shortcut can be used in SSMS 2016 to hide the results pane in the query editor?
Think you know the answer? Click here, and find out if you are right.
We keep track of your score to give you bragging rights against your peers.
This question is worth
1 point in this category: Management Studio (SSMS).
We'd love to give you credit for your own question and answer.
To submit a QOTD, simply log in to the
Securing SQL Server - Written by Denny Cherry, a Microsoft MVP for the SQL Server product, a Microsoft Certified Master for SQL Server 2008, and one of the biggest names in SQL Server today, Securing SQL Server, Second Edition explores the potential attack vectors someone can use to break into your SQL Server database as well as how to protect your database from these attacks. In this book, you will learn how to properly secure your database from both internal and external threats using best practices and specific tricks the author uses in his role as an independent consultant while working on some of the largest and most complex SQL Server installations in the world. This edition includes new chapters on Analysis Services, Reporting Services, and Storage Area Network Security.
DB restore stucks after recovery step
- Hi, trying to restore my db for testing https://www.sqlservercentral.com/Forums/1862799/checkdb-Multiple-IAM-pages-for-object
I splitted the restore process into 2 steps, i restore full with...
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.