I’ve been giving an encryption talk over the last year, focusing on educating DBAs on the various features and capabilities available in SQL Server. One of the things I note in the talk is that SHA1 is not considered secure. You should avoid SHA or SHA1 if you are using SQL Server 2012. If you’re on an earlier version, you don’t have a choice.
Hopefully we’ll have more choices in the future. NIST has selected an SHA-3 algorithm as a new standard. This should provide more security, though there will be some time before we find out if there are any problems or potential attacks against this algorithm.
Orca was a high profile software failure this year.
I really wish that we would see detailed analysis of failed systems, if for no other reasons than to avoid repeating the same mistakes in the future. I’d hope that technical people that were engaged in building systems that didn’t work well would share their experiences, whether from development, deployment, administration, or even operations. I ran across a piece on the lessons of Orca, the web application that Mitt Romney’s campaign used, or tried to use, to manage their operations.
It seems that there were a number of problems with this system, which is almost stunning. I’d think this is a well known process that includes a number of pieces of technology that are built into so many systems these days. Integration is never smooth, and the short time frame of an election campaigns doesn’t leave a lot of time for testing, much of which apparently didn’t get completed. The article talks about many of the same things that I’ve seen mentioned in the past when applications don’t work as expected. A lack of training, a dearth of hardware, tooling that doesn’t work, all of these have been reported for years in many software engineering journals and articles.
Perhaps more analysis won’t help. I doubt that even a high profile failure would convince the manager of any internal software development project to spend more resources or lengthen their time line to prevent a problem with an application. Like most developers, managers are eternal optimists when it comes to software being completed, regardless of their past experience. They never seem to learn that pushing for faster releases, cutting features, and limiting testing will showcase the end product poorly for the customer.
Steve Jones
The Voice of the DBA Podcasts
We publish three versions of the podcast each day for you to enjoy.
At SQL Saturday #169 in Denver I sat in on a panel that talked about cloud computing. There was a consultant, a customer, and a Microsoft representative that give different perspectives on what their experiences were with Windows Azure. It was an interesting talk and the more I learn about the cloud, the more potential situations where I think it applies. It’s not for everyone, but there are a lot of places where it can work, and I would encourage you to learn more about cloud services and cloud computing.
One really interesting question was asked. Do you know the skills needed for modern Microsoft data centers? Truck driver. A truck driver can drop off a shipping container with servers pre-configured inside and just plug it in to power and network, often with no cooling needed. A fenced in parking lot, open to the atmosphere, makes a nice, inexpensive, low maintenance data center.
That’s simplified, but it has interesting implications for networking, hardware, and system administrators, but what does that mean for DBAs? How will our jobs change if these shipping containers run SQL Server services on Azure or AWS? It’s a good question, and one that I know worries many people that manage SQL Servers.
On one hand our jobs don’t change. We still need to manage the data, enforce quality, design tables and manage indexes. We must ensure the data is available, intact, accessible by clients. We import, export, and even recover it at times. These are all the core skills of a DBA. On the other hand, we have new challenges to manage. Our recovery process will change. We will need to learn how to scale out our data and applications. We will need to better set expectations for performance, and perhaps more closely expand and contract the resources we use to match the demand we receive. In order to do that, we’ll also have to better understand the financial costing models that vendors provide, along with gathering more knowledge on the actual value our organization receives from more, or fewer, resources.
The idea of remote computing, whether as hosted VMs or a platform that provides database services, is going to be a part of many of our careers. We might as well embrace it, understand it, and find a way to fit in.
Steve Jones
The Voice of the DBA Podcasts
We publish three versions of the podcast each day for you to enjoy.
Voice of the DBA 