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.
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.
Watch your systems like a hawk. You’ll be glad you did.
An old phrase used in business is that knowledge is power. When you understand more about a particular situation, you can develop solutions and better understand which ones would both suit your environment better and solve any issues faster.
As someone that has worked in a variety of production environments managing all different types of platforms, I have found it extremely career-enhancing to have knowledge about the entire environment. Knowing what is happening at any point in time has allowed me to answer pointed questions about the applications. With comprehensive monitoring set up in database servers, I have often found myself in a position to proactively prevent issues, or make preparations for a quick response when I do find problems.
Over the years I developed a variety of techniques to monitor my own servers, often using third party solutions, enhanced with my own queries. I have learned that each system has its own idiosyncrasies, which often require custom queries to keep an eye on the pulse of the system. I’ve also learned that a regular exception report is the most valuable tool for me as a DBA. I assume most of my applications and scheduled tasks are working well; I just want a list of those things that have broken, or are not performing as expected sent to me every day, using the data from my various monitoring tools.
I have found that tracking metrics and analyzing the data is a valuable tool in my DBA tool belt. I would go so far as to say that monitoring the systems that you work with is not only a best practice, it’s essential if you want to be an exceptional DBA.
Steve Jones
The Voice of the DBA Podcasts
We publish three versions of the podcast each day for you to enjoy.
There’s always more than one way to get things done.
This editorial was originally published on Feb 13, 2008. It is being re-run as Steve is returning from the PASS Summit.
I have come competition here with my daily editorial. If any of you get the SQL Server Performance newsletter, you might have noticed that Peter Ward is now writing daily over there. He’s a nice bloke from down under, a fellow MVP, and he has some interesting things to say. He’s a bit more focused than I am and if you have the chance to hear him speak, it’s worth it. He gives some nice presentations.
I noticed the other day that he was talking about how he uses ALT-X to execute SQL queries, while most other people click “Execute” or click CTRL-E. I can’t help but think even more highly of Peter since I’ve used ALT-X for over a decade and know it’s the best way to do this. 🙂
His discusion wasn’t on executing queries, but on the fact that there are many ways to accomplish tasks in SQL Server. For example, you could audit by placing triggers on every table, capturing the inserted/deleted information, and storing it in a table. Or you could run Profiler forever and ever, making sure you have a system in place to manage those files. Or you could rewrite your code to use the OUTPUT clause. Or wait for Change Data Capture in SQL Server 2008.
All of these are valid, and there might be good reasons why you’d pick one over the others in your environment, but which one should you look to? What about many of the other possible ways of doing things in SQL Server? Should you look to rebuild or reorganize indexes by default? There are any number of tasks you need to accomplish and, often for people less experienced in one area, it seems either of a few ways is acceptable.
I certainly wouldn’t want to remove options and limit a DBA to developer to one way to do things in most cases. I think the richness of SQL Server, which is always growing, allows it to scale and handle a wider variety of tasks than ever before.
However I think that often the overwhelming number of choices can lead to a paralysis of choice for some people. Or confusion about what to do or what makes sense. Present my daughter with 2 candy machines and she can pick the one she wants in an instance. Take her into a 7-11 with an aisle of candy and I’m still standing there 15 minutes later waiting on a decision if I haven’t forced the issue.
I think that one area of improvement that could really help with many of the possible choices for completing a task is to have some strong guidance from Microsoft (based on customer pilot testing and the reasons for implementing a feature) that would explain what the defaults should be. And would have those defaults set up as the default choices or actions for the product.
Those of us with reasons to make changes can, and will do so. But those that don’t know what to do would have more guidance right out of the box.
Steve Jones
BTW – No offense intended to the cat-people out there.
The Voice of the DBA Podcasts
The podcast feeds are now available at sqlservercentral.podshow.com to get better bandwidth and maybe a little more exposure :). Comments are definitely appreciated and wanted, and you can get feeds from there.
Today’s podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.
Voice of the DBA 