Test your restores: he first tip in my Hard Earned Lessons of a DBA piece.
I can’t emphasize this enough. I’ve been called in as an employee and consultant to companies that never had tested a restore. Quite a few of those times there has been data loss.
It’s T-SQL Tuesday time again. This is the monthly blog party, started by Adam Machanic. If you’d like to participate, write a post on the topic and publish it on the second Tuesday of the month. If you’d like to host, contact Adam.
This month the topic is hosted by Bradley Ball and his subject is Second Chances.
We all make mistakes. I ask the question of people in some of my talks, and note that I make mistakes all the time. I do, and while most of them are fairly small and easily recovered from, some aren’t. Some are easy to brush off, and some are very, very embarrassing.
In my career, when I think about the big mistakes I’ve made, I’ve got a few choices. There have been times I’ve deleted all the data in a table.
There have been times I’ve restarted a SQL Server without telling anyone. There have been “fixes” to the system I’ve made without running through the proper channels. However there is one item that stands out for a few reasons.
I’d let patching slip. We had a large SQL Server environment (hundreds of Standard/Enterprise versions, thousands of MSDE versions) and while we’d been trying to stay patched, it was a hassle and we let some things slip in the fall of 2002.
I’d gone to the mountains for the weekend to ski with my family. We returned late on a Sunday night to find numerous voice mail messages at home and on my cell phone. I was actually called again while I was checking messages on the way home from a friend at work that said I needed to come in. After dropping off my wife and kids, I headed to the office.
Our analysis of the worm showed that it was wrecking havoc on our network. It constantly bottlenecked the network, and we had shut everything down. For a 5,000 person company, with a central network presence and hundred of software developers, this was not ideal. We were up most of the night, waiting on someone from Microsoft to fly in and help us rebuild the patch that Microsoft had released. Since we’d installed many instances of MSDE in non-standard locations, the patches wouldn’t work.
Our network was down Mon and Tues, but we learned some valuable lessons, like email and file shares weren’t so critical to the business that we couldn’t function for a day. We also learned that allowing developers to ignore patches was a bad idea as the majority of the delays after Mon afternoon were due to MSDE instances.
My lesson? Myself and the other DBA received a stern talking to from our boss about patching. We had delayed some of the patches for a few months, but there wasn’t a good excuse for getting almost six months behind. Microsoft had been sending lots of patches, but we didn’t have a good reason for not getting them installed quarterly.
I still don’t like the every other month patches that MS releases as cumulative updates, and I don’t recommend them, but I have learned the security updates are worth getting installed ASAP.
I’ve been asked by Red Gate to give my “Prepare for Disaster session on a webinar on July 23, 2013. It will be at 10:00am MST/12:00pm EST/ 5:00pm GMT. This is a session that talks about some of the disaster issues I’ve faced, and you might face. I then “rewind the clock” and look at ways that we can prepare ahead of time and either prevent, or mitigate the impact of the issues.
The registration link is here.
For once I’m doing this from the comfort of home instead of being on the road somewhere, which is good and bad. I don’t love presenting webinars, since I really like the audience feedback. Talking to the wall isn’t something I enjoy. However I don’t have the hassles of travel, the time away from home, and I get to sleep in my own bed. All in all, it’s a win.
If you’re interested in learning about how to get ready for disasters ahead of time, register and I’ll see you on the 23rd.
I was wondering what this was when I saw it at the Microsoft Technology Center in Philadelphia at SQL Saturday #200. I sat in it, and thought it was pretty cool.
Turns out it is an Emperor 1510. You can actually buy it, for between $5000 and $20000, depending on the options. I think this was the cheaper version, and it was pretty neat.
It’s not perfect, but it is neat to sit down, have the monitors then lower to meet your preferred height. There’s a flip over desk piece that has space for a keyboard. I guess you’d need to mount a keyboard on it, but it’s a neat idea. With a cup holder, it’s pretty neat. It also reclines up and down, so you can work at your preferred angle.
The downside might be that getting in and out is a little slow. The monitors take a little time to move up and down, and you might easily bang your head.
Not sure I’ve love this, or if it would be good for you. I like my standing desk, and use it a lot. Even at a sitting desk, I like getting up regularly and moving, not sitting for long periods of time.
However this is cool.
