Author: way0utwest

  • Speaking at SQL Saturday #304–Indianapolis

    indy304Next weekend is SQL Saturday #304 in Indianapolis, a milestone for me. It’s the first Indy SQL Saturday I’m speaking at, though not the first one they’ve held. I’ve been to the Indy Tech Fest, but that was years ago and I’m looking forward to going back.

    It’s also the first 300-ish event for me. I’ll be at #300 in Kansas City in September, but as it sometimes goes, #304 is happening before that milestone.

    This looks like another great event, with speakers coming from all over. The schedule has Allen White, Brian Davis, and Erin Stellato coming from Cleveland. Joey D’Antoni from Philadelphia, Kevin Boles from Alabama, Rob Volk from Atlanta, Tamera Clark from Tennessee, and more. I see amazing sessions on Azure, T-SQL, execution plans, extended events, XML, Hekaton, and more. The biggest challenge will be choosing between sessions.

    I’ll be delivering my branding session, at 9:15, so hopefully I can convince a few of you to network and brand during the day.

    If you are anywhere near Indianapolis, which means Louisville, Cincinnati, Dayton, even Chicago or St Louis, I hope you make the drive and come attend.

    And please be sure to stop and say hi and shake my hand. It’s always a pleasure.

  • Smiles

    seheap

    From the Stack Exchange chat.

  • A late night–sabbatical catch up

    My company, Red Gate software, has given me a 6 week sabbatical. I’m documenting the time with all the posts under a tag if you want to follow along. The sabbatical is over, but I’m still catching up on things.

    I took an extra day in the wood lab last night. The instructor offered to show up Wed night, with all projects and work due Thur, and I wasn’t the only one that needed the time. Almost the entire class was there, and it was fairly quiet with no other students or instructors working.

    With my piles of parts close, the first thing I needed to do was cut tenons. I’ve done this before, by hand, with limited success. However since time is short this semester, we were given permission to use the bandsaw (and a little instruction).

    I first marked things up.

    Photo Jul 29, 5 47 21 PM

    As with the mortises, I was thinking I could mark one board and use the setup for others. However when I showed the TA, he saw some problems. First, I needed to center the tenon. That messed up my reveal, but I could always plane the board to fix that. Then he noticed that when I’d cut left and right hand mortises, my setup was slightly off, so that they are slightly (1/64”) low on one side. Not a huge deal, but it means I need to account for R and L tenons differently.

    So back to marking, spending the better part of an hour marking all 8 sides of the 4 boards, in stages to separate right from left. With that done, I turned to the bandsaw to cut the tenons.

    Photo Jul 30, 8 14 15 PM

    I went a little fat, having had experience with too thin. I ended up too fat, and spent most of the night fussing to get thickness, and then height, to the correct settings. Once they were cut, I felt like I was making progress, but little did I know.

    Photo Jul 30, 7 53 50 PM

    I went very slow on the router plane, making some passes that didn’t cut anything or generated dust. However I wanted a tight fit. Things were tight on the right tenons, but later I had to come back to this to thin a couple left ones. However I had tight fits all around.

    Photo Jul 30, 7 53 44 PM

    Once those were done, I re-marked, and shaved off the upper part of the tenon. Things still seemed to fit well, and I had a decision to make. The bottom shoulder was about 1/16”-3/32”, depending on left or right. I could lengthen the mortises and have no shoulder (tempting) or cut a small one. I opted to cut a small one. As much as I like the mortiser, it takes time to setup and at this point, I’d blown 2 of my 3 hours and wasn’t terribly close to having a single joint. I still knew I’d have shoulder work.

    I lightly trimmed the bottoms, and as I worked on squaring the shoulders to the joint, I went back to the bandsaw a few times for small trims. I was trying to be careful, but also feeling pressure. Never a good combination.

    Once things were cut, and thinned, I test fitted them together. The right hand ones seemed to do OK.

    Photo Jul 30, 8 26 05 PM

    You can’t see it well, but the shoulders on most were slightly off to way off. I spent about 15 minutes trying to get one to fit, before I got too frustrated and decided to work on them in the order of the closest to fitting to least.

    Photo Jul 30, 8 26 00 PM

    Back and forth to the vise, using a chisel to square, and then fit again. I’d hit the bandsaw for the ones that were way off to save time. Chiseling is satisfying, but slloooooowwwww and things are due Thursday.

    When I had a good fit, with almost no gap, I’d mark the back of the board. I got the short aprons (sides) done first and I could put two legs on an apron and felt good. The long sides were harder, and 3:15 into extra lab time, people were cleaning up. I decided to try a test fit and see where I was.

    Photo Jul 30, 9 42 06 PM

    Things went together. I was amazed, and also somewhat proud. After all, I’d started with a pile of rough lumber board. I dropped the top on, just to see.

    Photo Jul 30, 9 42 21 PM

    It looks good. I actually built a piece of furniture that doesn’t need glue or screws, and looks decent.

    Photo Jul 30, 9 42 27 PM

    There are three bad gaps on the long aprons (front/back) that I need to fix tonight. I also need to run the bottom of the top (if that makes sense) through the planer to thin it and shorten my bevel. A little long for the side of the bottom.

    I’ve also got the dimensions slightly smaller than I’d like, so I have to decide if it’s worth trying to shorten aprons slightly from a design aspect. Probably won’t do that, but it’s something I’ll think about.

    Hoping to get to pin it with dowels tonight, but if I don’t, I’ll drill and add faux pins for decoration.

  • Monitoring for Non Existent Events

    I was catching up on work recently, reading the third installment of The 5 Worst Days in a DBA’s life, starring The DBA Team. Someone had asked me if I enjoyed having Paul Randal (b | t) of SQLskills join them team. The piece had been edited and published while I was gone, and I hadn’t had a chance to immerse myself in the adventure. I was anxious too read how Paul helped save the day.

    It was a fun read, but one quote in the piece struck me. “A job that runs long or doesn’t run at all can sting just as bad as one that fails.” That’s a quote from my character showcasing a situation that few people actually think about. However jobs that don’t run or don’t finish are situations that DBAs should be monitoring for.

    So many of us adopt a set-it-and-forget-it mentality with our jobs. We assume that things will work, or fail, as we set them up. However it’s easy to forget that there are other states we might find ourselves or our systems in that can cause issues.

    Monitoring is critical to any well run system, but monitoring needs to be set up well. If we require that certain jobs run, we need to not only check for success or failure, but if the job has actually run and completed. It’s easy to accidentally disable the wrong job and not notice. It’s also entirely possible that a job gets stuck and doesn’t complete.

    If you’re not watching for those other states, you might find yourself in a situation where you don’t have backups and your job is on the line. However you probably won’t have The DBA Team to call on.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.2MB) podcast or subscribe to the feed at iTunes and LibSyn. feed

    The Voice of the DBA 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.