I was listening to Brent Ozar today and in one of his session he had mentioned that mistakes can and has cost a lot of money. I started to think about this and I am going to try to start a game of tag. So here is the way it works, for many new DBA’s they may not realize that all of us have made mistakes and that our mistakes can be… rather stupid. I challenge each of the people I tag in my blog to post as least one mistake that they recently made I will start by describing 2 mistakes that I made. One of my mistakes was as a junior DBA and one about 6 months ago. The point of this game is to in no means embarrass ourselves or discredit ourselves. But more of a learning experience from our mistakes type of a deal.
So here are my mistakes that I made…
My first full time job I was employed to be a Database Administrator, however my boss thought that I should learn more about setting up a domain. I spent two weeks in class, I learned all about Windows NT and Windows Workstations. When I took this class I paid extra attention, I would stay late I would do labs many times, I wanted to know all I could. So the first day back at work the boss man comes to me and says… Chris set this server up as the PDC and get all the workstations in the office to connect. I thought no problem. Well I swear it was two weeks of me using language that I would not dare to post. I just could not get it to work. I rebuilt servers I replaced NIC’s heck I even rebuilt the workstations. One day I though… This is not that hard I have to be missing something. So I decided that I was looking at the problem to close. I had some other work to do so I stepped away for what I intended to be a couple of days. I had some cable to clean up since I replaced all of it and left it a mess. As I was standing behind the rack, I noticed that there was a toggle on the back of the router. I thought about it and said well that is stupid why is there a toggle, there isn’t even a power wire plugged into it. Then I looked again. There was a place for a power cable, why did I not plug it in. I am telling you the second I did and turned it on the machines all connected first shot. Since that day I call that my O.N./O.F.F. dip switch project. Sometimes the problem is as hard as you make it.
Just so that you don’t think we only make mistakes when we start just a few months ago I was loading 2008 on a my machine. I connected to the server and started to browse around to see what had changed. I had a client that I connected to with my Management Studio. I clicked on a server and looked at the properties. It said there was 3 gigs of ram. I was beside myself. I know my client had 8 Gigs. I was sure of it. I even double checked my work and logged on to the server and saw that I was right there was that memory on the server. I thought wow, no one else has seen this and posted about it. I think I found a bug. I was more then happy to jump on the Microsoft site and post my findings. I was going to be the one who discovered a bug. Well I did and a SQL Server Pro that I respect a lot answered my question. We started to look at the configs. Well thank goodness before we got to deep I realized that it was not the client server I was pulling memory info from it was my local server. So now I look dumb in the news groups.
So since this was inspired by Brent I will first challenge him, and another great DBA I know. Tell us something that you did that just was not quite right.