Doug Lane

SQL Server Entertainer

  • GitHub
  • LinkedIn
  • Twitter
  • YouTube
  • Blog
  • About Doug

Book Review: Getting Things Done

July 15, 2011 by Doug Lane

This review is part one of a twelve-part series of book reviews I have committed to writing over the next twelve months (read the list and the reasons for making it here: “What Gets Measured Gets Done“). As my list of responsibilities grow at work and at home, I need to improve my organizational methods in order to keep up. Plus, honestly, I’m not a highly organized person. I tend to do what is on my mind at any one moment. I remember to do pretty much everything (and certainly everything that’s important) but I don’t have much structure to support my train-of-thought methods. Getting Things Done by David Allen aimed to do two things: make me more productive, and take the stress out of the process.

I checked out the book from the public library; I rarely purchase non-technical books anymore — most are available somewhere in the Denver metro area. I also bought the unabridged audio book to listen to during my commute. The audio book is read by the author, who has an accent I can’t quite peg. I chuckle whenever I hear him stress the ending “r” in “tickler” or “labeler”. There’s enough content in the book that to fully absorb it, I had to read it twice and listen to the audio book four or five times.

At 259 pages, it is at times a tough and tedious read, if only because there are frequently new concepts, diagrams, and systems within systems being introduced. For example, in chapter nine, he introduces three levels of thinking to go through in order to decide what action is best to take:

  1. The Four-Criteria Model for Choosing Actions in the Moment
  2. The Threefold Model for Evaluating Daily Work
  3. The Six-Level Model for Reviewing Your Own Work.

These levels are hierarchical, meaning every task you undertake will pass through each of the three models before you start it. (One exception, I think, is the tasks you can hammer out in two minutes or less. Allen advocates simply doing them is simpler than trying to plan them.)

What I got out of the book

I read this book with the willingness to completely overhaul my time management habits. I can’t say I’ve done that yet, but I have made some improvements:

  • I reorganized my office folders using manila folders, and one per hanging folder. Already I have had an easier time filing and finding papers. (Note: I went against Allen’s recommendation to do away with hanging folders. I find without them the manila folders either slouch or are too tightly stuffed inside the drawer, especially when the folders are fat.)
    (True story: I once worked with someone who called them “vanilla folders”.)
  • I use the middle strata of his six-level model to evaluate tasks. I’m a very future-oriented person, and when I project out it’s usually in increments of years or even decades. I have a good idea where I want to be in ten years, but I hadn’t been connecting tasks with, say, areas of responsibility — what Allen calls “20,000 feet”.
  • I stopped making piles. My desk was only sparsely covered, but now there’s not much beyond the usual supplies and decorations. Paper doesn’t rest comfortably in processing purgatory the way it used to. By filing papers away and trusting my lists to serve as the sole reminder of actions involving those papers, I don’t feel the mental jab I used to whenever I’d see the pile.

Am I stress-free now? Of course not, but I do feel more comfortable knowing that I’ve tracked everything on a list. One of the chief aims of the book is to create a “mind like water” by storing projects and to-do’s on paper, not in your mind. I think my mind has gone from molasses to 5W-30 — a subtle improvement. Accounting for all my tasks doesn’t preclude my concern about getting them done.

Am I closer to my goal?

I read this book to improve one of my weakest links — organization. I am definitely better off for having read it, and I suspect I’ll realize more benefits as I continue implementing Allen’s methods. Some who have adopted these methods claim it has given them a new-found freedom. I don’t find the system’s effects to be so profound, but nor was I overwhelmed by e-mail and meetings. The people most likely to gain (or likely to gain the most) are those drowning in the pool where correspondence and responsibility meet.

Whether you’re in dire need of a new system of organization or merely interested in some productivity tips, give Getting Things Done a try. I suggest borrowing it from the public library; it’s a popular book and most branches will have a copy or two. You’re likely to mine a nugget or two that will make getting things done a little easier.

Filed Under: Career, SQLCruise

MCTS 70-448: Failure is a Fine Option

July 1, 2011 by Doug Lane

This was the second time I failed a certification exam, and the first time I expected to fail. It’s also the first time I’ve been perfectly content with failing.

I took the MCTS 70-448 – Business Intelligence exam yesterday morning only because I had to. I signed up for the three-exam pack offered by Microsoft and Prometric on June 22, and as a requirement I had to sit for an exam before July 1. Having only eight days to study, I put my odds of passing around fifty-fifty. I knew I’d do well at Integration Services, I’d do very well at Reporting Services, and I’d need to remember everything I’d crammed in the last three days in order to salvage the Analysis Services section.

That’s pretty much how it went.

70-448 Exam Breakdown, Doug Lane, June 2011
What almost passing looks like

While the pass/fail result met my expectations, I was surprised to learn from the test that:

  • I know more than I thought I knew about deploying Integration Services.
  • I know less than I thought I knew about developing Reporting Services.
  • Apparently, I am as proficient at deploying SSAS solutions as I am developing an SSRS solution. (Riiiiiiiiiight.)

But most importantly:

  • With a score of 610, I was dangerously close to passing (700), and I will absolutely pass this exam on my second try.

I was happy about failing for two reasons. First, I didn’t crash and burn in any one category and my overall score tells me I’m on solid ground with this material. Second, I often hear that certifications (especially the lower-level Microsoft ones) are “not worth the paper they’re printed on.” Had I passed today, armed with little book knowledge and virtually no real-world experience of Analysis Services, I would have done the certification a disservice. I didn’t deserve it this time.

Fortunately, I have two things working in my favor for re-taking the exam. First, I have a free second shot (part of the exam pack offer), which I hope to take in the next 30 days, while the material is still fresh in my head. Second, I just started prototyping an Analysis Services solution — my first ever — at work. My boss is very enthused about the potential for this project, so I can allocate plenty of time to it right away. With a little hands-on experience and more study time, I’m going to do just fine on the re-take.

In my eleven-year history of certification exams, I’m now 8-for-10. That’s okay. Failing the 70-448 this time just feels right.

Filed Under: Analysis Services, Career, Certification, Integration Services, Reporting Services

What Gets Measured Gets Done

June 11, 2011 by Doug Lane

Bing bong!

In between announcements from our cruise director Julie, Buck Woody imparted some words of wisdom to our SQL Cruise group: What gets measured gets done. In other words, the things we track are the things we make sure to do. As part of his professional development talk, he issued a challenge to us all. Find twelve books that will assist in meeting a career goal, read one per month, and blog a review of each one. In doing so, we’ll not only advance closer to our goal, but also have some material handy in case we get in a rut thinking of blog content. Having identified a one-year goal, here are the twelve-ish books I’m reading to help me achieve it:

  1. ProBlogger: Secrets for Blogging Your Way to a Six-Figure Income by Darren Rowse and Chris Garrett. This one has been on my radar for a while thanks to Brent Ozar. Better to incorporate these ideas now while my blog is still small and flexible.
  2. On Writing Well, 30th Anniversary Edition: The Classic Guide to Writing Nonfiction by William Knowlton Zinsser. The last time I wrote extensively was college. Since then, my written communication skills have slowly atrophied. Time to sharpen up again.
  3. MCTS Self-Paced Training Kit (Exam 70-448): Microsoft® SQL Server® 2008 Business Intelligence Development and Maintenance (Self-Paced Training Kits) by Erik Veerman, Teo Lachev, and Dejan Sarka. Since I’m as much a BI developer as anything, I really want to pass this exam. I’ve had this book for two years. I just need to get off my can and get it done. Speaking of getting things done…
  4. Getting Things Done: The Art of Stress-Free Productivity by David Allen. One of my not-strengths is organizing a large quantity of tasks. I can do it, but not very efficiently. I’m hoping to adopt some ideas, if not the whole system, to make life less chaotic.
  5. The Exceptional Presenter: A Proven Formula to Open Up and Own the Room by Timothy J. Koegel. At the end of Kendal Van Dyke’s 2010 PASS Summit session, he gave away two books about presenting. This was one of them. I love presenting and I crave getting better at it. This seems as good a place to start as any.
  6. Confessions of a Public Speaker by Scott Berkun. The other book Kendal gave away at the PASS Summit. Between this and Koegel’s book, I should have plenty to work on.
  7. StrengthsFinder 2.0 by Tom Rath. I’ve already taken the StrengthsFinder test. I’d like to know more about what my results mean and how I can best put them to use. I expect this book will give me the answers.
  8. Microsoft SQL Server 2008 Integration Services: Problem, Design, Solution by Erik Veerman, Jessica M. Moss, Brian Knight and Jay Hackney. At last, a technical book on the list! I work with SSIS a lot, and I like hearing how other people design their ETL solutions. I’m eager to read how they solve problems with SSIS, and learn how I might design things better.

And then there were five. Five books that, for reasons I won’t go into now, are supportive of my one-year goal. As much as I love reading about giving a professional presentation, writing well, or blogging effectively, I expect this will be the part of the list I devour. I can’t wait to get through these five books, and I can’t wait to show you why I’m reading them.

  1. The Murder of Roger Ackroyd: A Hercule Poirot Mystery (Hercule Poirot Mysteries) by Agatha Christie.
  2. Don’t Murder Your Mystery by Chris Roerden
  3. The Weekend Novelist Writes a Mystery by Robert J. Ray and Jack Remick
  4. How to Write a Damn Good Mystery: A Practical Step-by-Step Guide from Inspiration to Finished Manuscript, by James N. Frey
  5. How to Write Killer Fiction: The Funhouse of Mystery & the Roller Coaster of Suspense by Carolyn Wheat

Until then, enjoy the soothing sounds of the Norwegian Pearl, courtesy of a forum user with the handle “groo”.

Filed Under: Career, SQLCruise Tagged With: #sqlcruise, #sqlcruiseak, career

My PASS Summit Abstracts: Why You Should Care

May 19, 2011 by Doug Lane

As you may already know, I’ve gone crazy for speaking at SQL events.  I can’t get enough of it. If I had the means, I would be hitting SQL Saturdays all over the country.  It’s only logical, therefore, that I submitted the maximum of four abstracts to the PASS Summit. I have no idea what my odds are of getting chosen; I dare not even guess.  For a very short time, you can up those odds by “preferring” (voting) for my sessions here.

To give you a better idea of what I’m hoping to speak about, I’ve listed the abstracts below, along with a little blurb about why you should vote for it, and ultimately, and hopefully, attend.

“Ben, why didn’t you tell me?”: Reporting Services Lessons Learned the Hard Way

Level: 100

What is it about? 

Like Luke Skywalker, sometimes we wish we had received certain information a little earlier. In this session, we’ll cover ten tips — gleaned from real world lessons — about Reporting Services that will help you skip ahead on the learning curve. Attendees will learn simple tricks to quickly test report subscriptions, keep the Reporting Service from falling asleep, jump-start new report creation, and more.

Why should I care?

If you’ve ever wished for the SSRS equivalent of an “Accidental DBA” or “Top 10 Mistakes DBA’s Make” session, your wish is granted. Imagine you were taking over your first Reporting Services instance from me and I had one hour to give you tricks to make life with RS easier.  That’s what you’ll get in this session.

Bump, Zoom, Flip: Precision Report Design

Level: 200

What is it about?

Do you feel stuck with the default appearances of your report objects? If you’re ready to take complete control of your report visuals, this session is for you.

Valeris and her mismatched uniform
"This doesn't bother you? Not even a little?"

Attendees will learn to control the finer points of Reporting Services report objects through the manipulation of properties like PointWidth, CustomInnerPlotPosition, WritingMode, StripLines, and more. We’ll also go off the beaten path into the strange and seldom-visited underworld of the Grouping Pane known as Advanced Mode.

Why should I care?

Because you care about the little things. Because to you, reports should look like your resume: impeccable. Because there’s too much white space around these charts.  Because you want complete command over how your reports look.

Data-Driven Subscriptions with SSIS

Level: 200

What is it about?

Do you have the need for data-driven subscriptions, but no room in the budget to buy Enterprise Edition? If so, this session is for you. We’ll cover how you can deliver reports, by both file share and e-mail, on a limitless number of schedules, all using one simple package.

Why should I care?

Because you don’t have Enterprise Edition, but you have more reports than you can easily administer using Report Manager.  Although I’ve taken out proprietary stuff, this setup is nearly identical to one I’ve run in production for over a year.  Plus, I’ve added some enhancements that weren’t part of the package the last time I presented it. If you’ve been thinking about creating your own data-driven subscription framework, you’ll want to see this first.

Developers are from Mars, Report Servers are from Venus  

Level: 100

What is it about?

Do you remember what it was like to fall in love? Wasn’t it wonderful?

Lately it just hasn’t been the same. There’s just no spark anymore. You’ve been stuck in the same old routine, doing the same old charts and tables. Maybe Reporting Services won’t tell you what’s wrong. Maybe you’re even thinking about seeing other reporting products.

In this session, Doug will re-ignite your passion for RS by reminding you how reports perform best, what RS has been trying to tell you (but you haven’t been listening), and show you some new — and easy — tricks you may not have known RS can do. You’ll leave knowing more about troubleshooting with the execution log views, understanding how to better design reports for performance, having a plan to deal with unwanted blank pages, and more. After this session, you’ll want to spend some time alone with your new old flame.

Even though this is a 100-level session, it’s still useful for people in the 200-300 range.

Why should I care?

Business Intelligence should be fun, but it’s hard to have fun when you get frustrated.  Think of this session as couples therapy for you and Reporting Services.  This is an upbeat session that’s meant to help you understand why Reporting Services doesn’t always behave the way you expect it to, and how you can develop a great working relationship with it.

Of the four sessions I’ve submitted, this is my favorite because I get to tap into some of the reasons people hate SSRS and not so much convince, but remind them it really is a great product.

“Tick tock, Clarice.”

Time’s running out.  Head over to the PASS Summit site and give these and other sessions you like the thumb’s up.  Thanks for your consideration!

Filed Under: Presenting

Feedback Matters

May 17, 2011 by Doug Lane

I readily admit when I see a comment card, there’s a 99.9999% chance I’m not filling it out.  When I buy a product on Amazon.com or another site, I don’t go back and post a review unless I feel a very compelling reason to do so (read: never).  And it’s rare that I will give feedback to a restaurant other than telling the server I enjoyed my food.

Perhaps it’s paradoxical, but I feel a strong obligation to provide feedback to speakers at SQL events.  Here’s why.

In most areas of life, we vote with purchasing power.  If a restaurant has good food and service, I buy again.  If I really like my Panasonic TV, I’ll strongly consider another Panasonic TV when it needs to be replaced.  SQL presentations are different because:

  1. In many cases, I paid nothing to attend except the cost of getting there.  If I’m lucky, the conferences with fees were paid by my employer.
  2. Even if one or two speakers don’t meet my expectations, I’m probably going to attend the event again.
  3. My decision to skip an event by a particular speaker is only loosely correlated to my opinion of their session.  For example, I have seen Steve Jones’ Modern Resume session and I thought I was great.  Would I attend it again?  Probably not anytime soon, but only because I want to hear something new or different.  It’s the same reason I won’t see Brian Regan (my favorite comedian) more than once every few years.  The jokes are still funny, but I’ve heard them already.  I’ll go see him again when he’s doing new material.

Therefore, the feedback we’re used to giving automatically — keep buying or quit buying — doesn’t apply well, if at all.  As attendees, what are our alternatives for giving feedback?  We could instead choose to share our thoughts face-to-face (tell the speaker we liked their talk), praise or flame the speaker/event on Twitter either in real-time or afterward, or we can blog about it.  Finally, we can give ratings and comments on feedback forms.  Feedback forms are the most common way for event organizers and speakers to gather feedback on their performance.

How Helpful Is Feedback?  It Depends.

The typical SQL user group and SQL Saturday feedback forms have a series of “rate from 1-5” questions, along with some open-ended questions intended to solicit comments. Switching perspectives to that of the speaker, here’s how I value feedback on these forms (ranked from most to least valuable):

  1. Useful comments, positive or negative.
    Example: “You lost me when you talked about the execution log.  Too high-level compared to the rest of the talk.”
    Delightful.  The kind of comment I can use to improve my presentation.
  2. Feel-good comments.
    Example: “Really enjoyed it!” 
    It makes me happy to read these even if there’s nothing in them to help me get better.
  3. Feel-bad comments.
    Example: “Didn’t cover what I expected.” 
    While this is not explicit, at least it makes me look back at my abstract to make sure I kept my promise about what I would say and what I wouldn’t.
  4. Good numeric feedback but no comments. Even though I know it’s nearly meaningless, it makes me smile to see 4/5 and 5/5. At least I know I didn’t disappoint these people.
  5. No feedback submitted. I put in 40-60 hours’ off-work time — time I could be playing with my kids, sleeping, watching my PASS Summit DVD’s, gardening, learning to play piano, anything — to build, rehearse, and refine this presentation. You come and absorb it at no cost.  I ask for 1/1800th of that time back for your thoughts and some light stenography so I can make my next presentation to you better. You decline. Then you leave. Yes, that seems fair.
  6. Bad numeric feedback but no comments. This is in no way helpful and it makes me look bad to those who would use these ratings to quantify the value of my session.  If you’re going to jab my overall score without telling me why, do us both a favor: Don’t fill out the evaluation at all.
  7. Kick to the crotch but no comments.  I have yet to offend someone so gravely that they assault me, but I’ll throw it out there anyway: if you’re going to kick my bag in, TELL ME WHY! (That way, my restraining order against you is much more likely to be granted.)

When I deliver a presentation, I’m dying to get feedback that falls under items 1 and 2.  Feedback for items 3-4 are okay.  Anything else is not going to help either party.

Why I’m Ranting About Feedback

It wasn’t the blog posts by Aaron Bertrand, Allan Hirt, or Mike Walsh that got me stewing about poor feedback.  It was Scot Reagin’s presentation to the Denver SQL Users Group last month that got me fired up.  All I will say on this is that there were at least thirty people in attendance that night, and Scot presented on MDX – a subject that is not easily grasped by beginners.  Here is what little feedback Scot received in return for a first-class session.

“You can go about your business.  Move along.”

Having met enough other presenters, I can say with confidence that we speak because we love to.  We love sharing what we know and helping other DBA’s, developers, and architects do their jobs better.  We’re passionate about SQL Server and the SQL community.  And in case I haven’t made it obvious, we’re passionate about improving what we deliver to you. 

Whether or not we get good feedback in return, we’ll keep on teaching.  Hopefully, you’ll take a few minutes to teach us a little something too.

Filed Under: Presenting

  • « Previous Page
  • 1
  • …
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • Next Page »

Subscribe now!

Don't miss new posts as they publish. Enter your e-mail address to subscribe!

Your e-mail address will stay quietly between us, like that time I set the carpet on fire by accident.

Copyright © 2025 · Outreach Pro on Genesis Framework · WordPress · Log in