You recognize that you need to provide a pipeline for database deployments, that you need to automate as much support for your development teams as you possibly can, that you have to have testing in place to ensure protection of the production environment, that you need to speed your processes. In short, you recognize the need for taking on a DevOps approach, an Application Lifecycle Management (ALM) approach, even, a Database Lifecycle Management (DLM) approach. Cool. Now what? Well, there are three fundamentals that you need to get under your belt. You need to get your database into source control. You need to set up a continuous integration process. You need to set up automated deployments. All tough nuts to crack. Hey, we get it. That's why Redgate Software is going…
There's an old joke that goes, "Doctor, doctor, it hurts when I do this." While the person in question swings their arm over their head. The doctor's response is, "Don't do that." Problem solved, right? Well, maybe not. Let's take a quick example from life. I do crossfit (yeah, I'm one of those, pull up a chair I'll tell you all about my clean & jerk progress... kidding). I've been experiencing pain in my shoulder. "It hurts when I do this." But, I'm not going to stop. I've been working with my coach to identify where the pain is and what stretches and warm-ups I can do to get around it (assuming it's not a real injury, and it isn't). In short, we're identifying the root cause and addressing the…
There are lots of people who talk about Application Lifecycle Management. But, the database is a major part of every application and if you do a similar search, there aren't very many people talking about Database Lifecycle Management at all. Why not? I'm positive you're deploying a database with your applications. I'm also positive, because of the unique problems that databases present, primarily around data persistence, that you need to think about how to get your database(s) deployed. Unfortunately, even for strong, capable data professionals, deployment is something thought about later. Or, you're still doing the old school method of waiting until there's a deployment script that you're going to review, line-by-line, before you run it against production. There's a better way. What you need to do is start thinking…
I'm learning how to speak German. Interestingly enough, you don't start off reading dissertations. Instead, you begin by learning the names of things, Teller for plate, Buch for book. The fundamentals. I'm a third degree black belt in Ken Ryu Kenpo. But you don't start that, or continue it, by learning complex kata. Instead, you start with how to make a fist, how to hold your hands up in a defensive stance. The fundamentals. I've been doing crossfit and Olympic weightlifting for a couple of years now. I've been working hard on my clean, standing up tall during the lift, getting my elbows around quick. The fundamentals. Situation after situation, skill set after skill set, you have to get the fundamentals right. And, if you don't get the fundamentals right,…
I no more than finished my rant from last week than I started thinking about all the reasons why a healthy chunk of the reasons that developers want to bypass relational database is not the horror of the relational database itself, although, that's there. No, a very large reason why is the DBA. We're on a blog called The Scary DBA. I earned that title, well sometimes. Sometimes I got it and I wasn't sure why. However, it's perfectly in keeping with how many people view their database administrators; grumpy, obstructionist, slow, difficult, control freak, etc.. There are even jokes about it, "What's the DBAs favorite word? No!" And for those answering "It depends" that's two words. I understand why. In large part it's that phone in your pocket (used…
We are coming into quite a busy time for my speaking schedule. I'm hitting the road. It does one thing for me that I truly love, I get to talk to people. So, if you have questions, want to chat, need to call me a pompous know-it-all to my face, I've got some opportunities for you. Next week, April 13-16, is SQL Intersection. You can register by clicking here. The following week, I've got two events. First, on Friday April 25th, Red Gate Software is hosting a free half day SQL in the City Seminar in the Chicago area. We'll be talking database deployment all day. Go here to register, but don't wait, seats absolutely are limited. And, since this is a Red Gate event, at the end of the…
Deservedly so, I got called out for a bit of attitude I displayed in a recent blog post: Time for a Quick Rant. Steve Hood took the general attitude of "Do this or I will beat you" to task in his blog post The Approachable DBA. Granted, my little rant was primarily done tongue wedged immovably in cheek. But I was reflecting an attitude that the gods know I'm guilty of and that I think way too many DBAs are guilty of. Actually, I think developers are just as guilty. And sysadmins, san admins, support desk people, QA, the report writing team, those people supporting the data warehouse certainly, the SharePoint team, and that poor lady who got stuck being the Deployment manager. That attitude? I don't think you heard…
Many years ago, I was working with a great DBA. Seriously, a very smart and capable guy. He told me, "We need to put the database into source control, just like app code." And I just laughed. Not because I disagreed with him. I knew he was right, but I had tried, several times, to do just that. See, I'm not really a DBA. I'm a developer. I knew that code (and all the T-SQL that describes databases is code) needed to be versioned, sourced, tracked and audited. But great googly moogly, it was not an easy thing to do. I first tried just exporting the entire database into a script and then occasionally checking that script into source control. Yay! Mission Accomplished... Well, I had a database in source…
I love that I get to travel around and learn from my #sqlfamily. We're still filling in the majority of the 2014 schedule, but the plans are to go to as many events as Mrs. Scary will let me. I'd like to alert you to a couple coming up in January, and then I should be able to get a fuller schedule for the first quarter posted soon (that way you can complain to me in person about Managed Backups). On Friday, January 10th, I'll be presenting a SQL in the City Seminar on Database Deployment in Cambridge, UK. Presenting in the UK is just fantastic. And this is a live event. And it's at the stately Red Gate Towers. Oh, and this is a free event, but seating is…
Some of the new functionality of 2014 is straight forward, non-controversial and easily welcomed by the community. Think, updateable column store indexes. Some of the new functionality is going to raise an eyebrow or three (most of the time, not on one person, but you know the #sqlfamily, we have some interesting mutations represented). Think... managed backups. Now, why on earth would a process that takes backups for you, including log backups, does it automatically per a schedule and/or when data has changed sufficiently, stores it offsite for protection and is easy to set up and maintain going to cause so much controversy? Hey, I'm wrong, it won't, move along... Or, maybe, I'm right, and this is going to raise more than eyebrows. We're talking about surrendering control over your…