I’m very happy to be making the trek up to Appleton, Wisconsin to speak at FoxPASS next week!
I’ll be delivering my presentation entitled “Whatcha Doin’? Passive Security for Hostile Environments”, which I presented to a packed room at this year’s PASS Summit. Here’s the abstract:
Ideal database security settings usually exist in books, but rarely in reality. Is your CIO a member of the sysadmin role because they demanded it? Or maybe some users have rights for purely political reasons? Just because you can’t enforce security through typical means doesn’t mean you’re powerless. Attend this session to learn about the features SQL Server provides that will allow you to keep track of what your users are up to at all times and sleep a little easier. Through various scenarios and demos, see how technologies such as event notifications, auditing, and extended events can help ensure nothing happens on your system without you knowing about it. Even in optimally secured environments these techniques can still come in handy. The best security is often that which cannot be seen.
When: Wednesday, December 4, 2013 5:30pm
Where: 2201 E. Enterprise Ave., Suite 201, Appleton, Wisconsin
If you’re a FoxPASS member, I’m looking forward to meeting you next week!
There was an interesting debate on Twitter the other day over whether or not it’s important for an interviewee to know what a company does, or if they should just know whatever technology the job description calls for and nothing else. Jen McCown blogged about it in detail and included a lot of comments.
There are definitely valid points on both sides, but in general I think it’s always a good idea to know what you’re potentially getting yourself into before you head to an interview. This way, should you find there’s something about the position you object to beforehand, you can save both yourself and the interviewer a lot of time by canceling.
Even more importantly, taking the time to learn a little about the company and what they do shows your interviewer(s) that you are really interested in the position, and may separate you from the other candidates. If someone is faced with two similarly-qualified applicants and one of them put forth the extra effort to do some research about the company in advance, which candidate looks better?
True story: back when my brother was a senior in high school he was applying for all the local scholarships he could find, one of which was offered by the local Masonic Lodge. They decided to bring him in, and I can remember him mentioning to my father one morning that the interview was later that afternoon. My dad asked if he knew anything at all about the masons, and if not, maybe he should look up some facts about them. Adam heeded my father’s advice before heading off to be interviewed.
A few days later, the Worshipful Master (awesome title!) called my brother to say they decided to award him the scholarship. This of course was awesome and we were all very happy, but even more entertaining was why they decided to award it to him.
It turns out they only invited 2 people in for interviews, and one of the questions they asked was “What do you know about the Masons?” Adam came prepared, and said he knew they were one of the oldest fraternal organizations in the world, and that several U.S. Presidents, including George Washington, were all Masons as well.
They said the other candidate, when asked the same question, replied something along the lines of “You guys are a cult, right?”
So if you want the job, or the scholarship, or for whatever reason find yourself needing to impress someone, do your homework ahead of time.
I’m very proud to have contributed a chapter to Tribal SQL, which is now available for purchase at Amazon and finer bookstores everywhere. This is the first book I’ve had any part in writing, something I never thought I would do. I always hated English and literature classes in school – if it wasn’t math, hard science, or architectural history, I wanted no part of it. I credit the SQL community and blogging for slowly getting me excited about the written word.
Getting this book from idea to print was not a sprint but a marathon. While I’m sure there was plenty going on behind the scenes that I wasn’t aware of, here’s how everything came together from my point of view.
How I got Involved
The first I heard about “SQL Tribal Knowledge” was from Matt Velic’s (@mvelic) blog post almost two years ago. Despite being fans of MidnightDBAs (@MidnightDBA) Jen and Sean McCown, I missed their blog post announcing the project. Basically they wanted to get a whole bunch of unpublished people together, have everyone write a chapter, and then assemble them into a book. Seemed like a great idea to me, so I submitted a few topic ideas, and ended up writing about data compression – a feature I’ve done lots of work with and know rather well.
Actually writing the chapter was both the hardest and easiest parts for me. Getting started was difficult because I wasn’t sure about what style of writing to use. I ended up reading through about a dozen other books not for content, but to see what tone the authors took when putting their words to paper. I ended up going with something not much different from a blog post – perhaps slightly more formal. With a style established, everything flowed easily. After about 2 months, my initial draft was complete and to my liking.
After the first drafts came peer editing. All the authors picked two other chapters to read and comment on. It was a great gut-check on things like grammar, effectiveness of explanations, etc. With both reviews in-hand it was back to the drawingkeyboard for revisions.
After peer editing there was a second round of reviews, this time from outside the author pool. Over 20 bloggers and speakers from the SQL Server community volunteered their time to read and comment on our work. Afterwards, this was followed by another round of revisions.
Throughout the process, Jen and Sean were trying to find a publisher. There was some brief talk about self-publishing, but then Red Gate got involved and agreed to publish the book, now named “Tribal SQL”. This involved – you guessed it – another round of editing, this time by Red Gate’s Tony Davis (@TonyTheEditor). Tony was delightful to work with and I have tremendous respect for what he does. After a few rounds of back-and-forth with him, my chapter was done.
From this point on I’m sure there were a lot of things taking place that I didn’t know about, but the end result is that the book was published, and Red Gate was kind enough to hold a launch event at the PASS Summit and distribute copies. They also held a book signing for all the authors that were in attendance.
Would I do it again?
I would. Writing a chapter is a lot of work – writing an entire book is obviously much more, but I found it enjoyable and rewarding. Given the right topic and/or group of co-authors, I’m sure I could have just as much fun working on another one.
Write Book, Get Published, ?????, Profit?
HA! I should mention that all royalties from the sale of this book are being donated toComputers4Africa. Even if that weren’t the case, any money we might get would work out to a paltry rate when divided by the number of hours spent working on this project. If you ever decide to write a book, make sure you’re doing it for the right reasons. Money is not one of them.
Finally, some thanks are in order. Thanks to Jen and Sean McCown for putting this all together, and to Matt Velic for blogging and making me aware! Thanks to all the other co-authors and editors for their time and hard work. Finally, thanks to the wonderful people at Red Gate, not only for publishing this book, but for the tremendous support they give to the SQL Server community as a whole.