I believe in DevOps. Actually, that's a pretty horrible way to put it. It's not about belief, like keeping Tinkerbell alive. I have successfully worked within an environment that implemented a DevOps approach to development, deployment and maintenance. I also provide classes and consulting on how to approach DevOps from the Ops perspective as well as writing books on the topic. Because I've seen the DevOps approach work, and work well, despite the fact that my principal job description is in the Ops side of DevOps, I am a very strong and passionate advocate for DevOps. But! DevOps Despite the fact that I absolutely support the concepts of DevOps, moving development & deployment into the production space, and moving operations into better support of the development space, I frequently find…
The Azure Data Platform is taking off. I'm seeing more and more interest on the forums, at conferences and in my personal interactions. I've been teaching the data platform for six years. Almost as soon as it was available, I started working with it, putting up blog posts and setting up sessions. I've had stuff in production on the platform for almost that long too. I'm an advocate and, I hope, an independent voice on the topic. By independent in this case, I mean non-Microsoft. Don't get me wrong, most of the people I learn from work for Microsoft. They are excellent instructors and more knowledgeable on the topic than I'll ever be. I'm not questioning the ability of Microsoft people to deliver the very best Data Platform content. I…
I was on SQL Cruise where I was scheduled to present a session on Azure SQL Database. I recorded all my demonstrations before we went to sea, but, I planned to attempt to try live demo's. Yeah, yeah. Well, anyway, I got a unique error when I attempted to connect: Forced connection closes from remote host That's a partial message from the whole error. I don't have a good screen capture. I wasn't able to find anything on it through Ging searches, but this week I was at Microsoft for a training course on Azure. I asked the room. The rough answer is (paraphrasing): The IP address I was attempting to connect from is not is not on the approved list Interesting. I didn't realize there were blackout zones. The really…
I spend a lot of time talking about the need for automation within your databases, especially in support of development, deployment, and through process management. It's because I learned the hard way just how important this stuff is. It took a pretty strong developer (in the sense of abilities, he didn't beat me up) to convince me that I was doing database development the wrong way. However, once he made me see the light, I was like one of the Blues Brothers, on a mission. However, I think this is one of the hardest parts to get people to understand. If you have a mostly, or completely, manual deployment process, you're experiencing pain from the inefficiencies that causes. However, it's a pain that's just embedded into the organization so much, that…
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…
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…
Ever since David Moutray introduced me to the concept of cargo cult programming, it's been running round and round in my head. I'm actually coming to believe that this is a major issue in all walks of life. True or not, we're absolutely seeing it in the data professionals space. Don't believe me? OK. A few questions. Do you work for one of the organizations that absolutely requires NOLOCK on all queries (even INSERT/DELETE/UPDATE)? Why? Because it runs faster? Why don't you just use READ_UNCOMMITTED for your isolation level? What's that? Never heard of isolation levels? I'll bet you also don't know what is meant by "dirty reads" then either. READ_COMMITTED_SNAPSHOT anyone? In short, you're guilty of being in a cargo cult. You've got this form in your head of…
One of the things that can make Windows Azure SQL Databases (WASD) attractive is the fact that they run inside of a managed environment. But, that does mean that you're sharing resources with other databases. That's not necessarily a bad thing, but if people are extremely worried about performance, yet, still want to take advantage of all the cool stuff in WASD, there is a way to do this; Premium Databases. I requested access to the early access program and was able to get it. You can request it by clicking on this link and scrolling down to Premium Database. Once you get access you should see this in your list of servers: To create a Premium Database you just create a  database any way you would normally (T-SQL through…
This conference is new to me. In case it's new to you, I thought I'd take a moment to point it out. Mostly because I'll be presenting there and I love talking to anyone who has actually read any of the blather I post on my blog. If you want to get together in the land of sunshine in December (don't tell Mrs. Scary but I'm looking forward to this one, winter in New England is awful), then click here to register. If you do it now you save $500, so it's a good time to take care of it. I'll be presenting two different sessions. One is on backups and restores for the accidental DBA. I'll go over the important stuff to get you started protecting your company's data…
Buck Woody recently asked a question; how do you design a database. He outlined the process he followed and asked four questions about how each of us do our work: What process do you follow? How important are the business requirements? What tool do you use to create the design, do you need it to diagram, do you even care about diagrams? What's your biggest pain-point about designing? Funny enough, I haven't done a full on database design in over a year. My company just finished about 6 years of very hard-core engineering work, designing and building or redesigning and building, the majority of our data input and collection systems. Then, I was doing lots of design work. Now, we're either largely in maintenance mode for most of those systems, or the…