What’s My Lane?

Yesterday a fellow #SQLFamily member, Brent Ozar tweeted about how someone objected to some content in his latest email he sends out to subscribers. Based on the response, I’m guessing it was this email.

Now, let me back up and in full disclosure say I’ve met Brent once or twice, sat in on a SQLSaturday session of his and one User Group meeting where he presented, but don’t know him well. We’ve never sat down and had a beer or discussed DBA topics together. And, in fairness, my blog on a good day probably gets 1/1000th the reads his blog will get on a bad day. He’s what some might call “a big name” in the industry. He’s an expert on SQL Server and well worth reading for that reason alone. I can’t guess how many people read his blog or newsletter, but I can say it has influence.

And so, someone felt that him writing about something other than how to build an index, or why not to use an update in a trigger was him straying from his lane and he should stick with data related topics. He’s already responded in some tweets and I presume elsewhere but I figured it was a good topic for me to blog about.

As long-time readers know, I don’t write just about SQL or PowerShell, but I also write about cave rescue or marshmallows or Safety (one of my more popular pages strangely). In other words I have an eclectic array of topics. But I also have some themes and I’ve written about (not) being an ally, or gender factors in giving blood. There are others, but the general point is I sometimes also write about social issues I think that are important. I think I’d be hard pressed to say what my lane is here; perhaps it’s more like a curvy mountain road?

But let’s go back to the person who told Brent he should stay in his lane. What lane did that reader refer to? I’m presuming it’s a narrow lane of “topics related to databases”. But, I think that person is wrong and I fully support Brent’s “straying from his lane.” Why? Because of power and privilege.

I’m going to go out on a limb (though I suspect it’s not a very far one) and state that I suspect Brent and I share much of the same privileges simply by being born the gender we are and skin color we have. There are other aspects we probably share.

These innate privileges give us power. And sometimes we are consciously aware of that power and other times unconsciously blind to it. Having the power and privilege itself isn’t an issue. It’s how it’s used that is important.

For example, all too often, I forget that I’m more likely to be taken seriously when I talk about a technical topic than some of my fellow DBAs, simply because of my gender and/or skin color. I can be unconscious to that power and privilege or I can work to be conscious of it. And by being conscious I can try to improve the situation for my fellow DBAs who don’t have my innate privileges.

I can be ignorant of that fact that no one questions my marriage and be oblivious to how some had to wait for the Supreme Court to recognize the validity of their love for their partners. Or, I can be aware of that and support my LGBTQI brethren in being allowed to live with who they choose and to marry them if I wish. This shapes my political opinions and who I will vote for. For example, I won’t vote for someone that I think will act to take away same sex marriage or will enact legislation that hurts such folks.

But there’s also more conscious forms of power. Simply being aware is not enough. Making room for others to be heard is a positive use of power. This is what Brent did and I fully support it. But, he didn’t simply make room, he provided the metaphorical microphone and the loudspeakers. If you didn’t look at the link above, look now. You’ll note that Brent didn’t write the email in question, but rather he gave space to a fellow DBA, Andy Mallon. This wasn’t an accident, this wasn’t Brent being lazy and not wanting to write an email, this was a conscious choice. This is using his power as a well known DBA and “big name in the industry” as well as his privileges to give a voice to others. (Please note, Andy’s a friend of mine, I’ve spoken with him at SQL Saturdays and he’s no slouch, but as far as I know he doesn’t have the audience that Brent has.)

I can support that use of power and if it’s “straying from his lane” so be it!

That said, as I wrote in my article in giving blood, as DBAs, we can NOT simply divorce ourselves from social issues. It’s not as simple as “well I just write SELECT statements and create tables.” The very data we record encodes social standards. When we make gender a bit field, we’re enshrining a very binary view of gender that does not reflect the lived lives of those around us. When we make fields that say Husband or Wife, rather than Spouse 1/Spouse 2, we are saying that only a certain form of marriage is valid (And for that matter, why stop at Spouse 2, why not make it a separate table for the day when someone walks in and claims to have more than one spouse.)

In other words, even if Brent had never strayed from writing about SQL Server, his lane would properly include social issues. Data isn’t nor should it be completely separate from social issues.

And I’ll toss out a few URLs here:

P.S. for those who read my post last week, I’m happy to say I got my slide deck and recording uploaded for presentation at PASS Virtual Summit 2020: PowerShell for DBA Beginners! So join me on Nov 11th at 2:00 PM! And use code LGDISIIK3 and save $50!

A Speaker’s Timeline

This post will be short, for reasons that are hopefully obvious by the end.

Sometime in February

Hmm, I should put together some ideas to submit to present to SQL Summit in Houston (not Dallas as Mistress SQL pointed out to me) this year.

March 16th

An update, the call for speakers has been postponed. Darn.

March 23rd

Call for speakers is finally open!

March 30th

Submit 3 possible topics.

April 1st

Approach a fellow speaker about a possible joint session, but after discussion, decide not to go ahead with the idea.

June 3rd

Get an update, Summit will be virtual this year. Thankfully I didn’t book any tickets or hotel rooms in Dallas.

July 20th 6:49 PM EDT

Woohoo! I got the email! One of my submissions got selected to present!

July 20th 6:50 PM EDT

Crap, now I actually have to write the entire thing!

July 20th 6:51 PM EDT

Wait, and it’s going to be virtual too. That’s going to make it a bit more of a challenge to present. But I’m up to it!

Sometime in August

I really should get started. Hmm, here’s one of the scripts I want to present.

But honestly, I’m preparing to teach a bunch of cavers and medical students cave rescue, I need to concentrate on that first.

September 5th

I just biked over 100 miles. I’m certainly not working on my presentation THIS weekend.

Later in September

Ok, now I’m going to sit down and really work through this. Here’s a basic outline.

October 1st

Oh wait, it’s going to be virtual AND I have to prerecord it? How is that supposed to work? I had better read up at the speaker portal!

October 2nd

Huh, ok, that sorta makes sense, upload the slides, do a recording, but I still don’t get how it’ll work with a presentation like mine with lots of demos. Well I’ll figure it out.

October 6th around 11 PM EDT

Well the PowerPoint template deck they provided looks pretty slick. I should start prepping my slides.

October 6th, approximately 5 minutes later

There, got the first slide done. Of course it’s only my name and pronouns, etc. But it’s a start.

Oh and the 2nd slide is done, but that’s simply the default PASS slide talking about chapters, SQL Saturday etc, so technically I didn’t do anything there.

I’ll start working on the closing slides.

October 7th, sometime after midnight

Ok, about 5 slides done. I’ll like to myself and say I’ve made great progress!

October 9th, approximately 10:00 PM EDT

Ok, I’ll at least start writing out the scripts I need.

October 9th, 20 minutes later

What the bloody hell? Why is this script failing? I’ve got to present this. If I can’t get this script working how is anyone going to believe that I know PowerShell, let alone actually use it.

October 9th, 5 minutes later

Well, damn, that was an embarrassing mistake, just had the , in the wrong place

October 10th around 9:00 PM EDT

Hmm, to properly demo this, I really need to run against 3-4 SQL Servers and I really don’t want to spin up a bunch of VMS and I can’t use my development one, too much proprietary data there.

I know, NOW is a perfect time to start to learn to use Docker! Why not? And besides Cathrine Wilhemsen has a great post on it. I’ll simply follow that.

2 hours and 1 reboot later

Hey, would you look at that? I’ve actually got a docker container running SQL. This is awesome!

Another minute later

But why can’t I actually connect? What network is it on? Why did I decide docker was easier? Why did I even submit this proposal? What the heck am I doing here? What is the meaning of life?

5 more minutes

That’s it, I’m going to bed.

October 11th, late night

Oh, I get it it now, I didn’t setup a full separate network, it’s bridged and that’s why it’s showing 0.0.0.0. I just need to change the port and I’m good to go!

A minute later

This is pretty awesome. Not what I’d do for a production setup, but definitely works for my demos. Now if I were really smart, I’d also setup persistent storage and the like, but this is good enough. And honestly now, setup a loop, increment a variable and bam, I’ve got 4 instances of SQL running in docker, 2 are 2017 and 2 are 2019. This is really incredible. I’m proud of myself.

Oh and even better, I’m doing all this in a PowerShell script, so I can actually make it PART of my presentation!

October 12th 2:26 PM EDT

Send off an email to the Program folks at PASS asking about how the recording stuff works with demos. Eagerly awaiting a reply.

October 15th, another late night

Yes, there’s a theme here, much of my work is being done late at night. It seems to work for me. But dang that deadline is getting closer!

October 16th, late night, again

Watched some Schitt$ Creek with the family. “Why didn’t we start watching this sooner? It’s hilarious! But I need to work on my presentation some more.”

Get all the PowerShell scripts basically done. I’m happy with it, need to work on my speaking script some.

October 19th 3:00 PM EDT

Get off the phone with a fellow Cave Rescue expert. Just before I get off, I mention my upcoming virtual, prerecorded session I have to finish. He says, “Oh, you know I just did 2-3 of those for a rescue conference, exact same format. It worked out really well. I can send you some details and feedback.”

I find that reassuring.

Also recheck email, still no answer from the folks at PASS on my questions about demos, etc.

October 19th, guess what time

I’ve finished everything, even updated the slides and scripts a bit more. I’m a bit worried I’m going to run too long, but decide to do my first of several practice run throughs.

Do my first full run through. Stop and correct a few mistakes or rough edges here and there. I’m not too worried if I run over now since I know I’ve artificially added some time.

October 19th, 42 minutes later

I get done, look at the PowerPoint timer: 42 minutes. “CRAP! I need this to be 60 minutes!” I’m not too worried, I can add more, but I’m not sure where and I don’t want to simply add fluff for the sake of fluff. I need to give this some thought.

Later on October 19th

Talking to a friend of mine who among other things has a background in adult education. She doesn’t know SQL or PowerShell, but she’s a good sounding board and she’s going to sit through my next run-through, not so much for the technical details but to give feedback on the flow and perhaps suggestions on where I may be making too many assumptions on what my listeners will know.

October 20th Early Morning

It’s a Tuesday, time to blog. As always I face that question, what should I blog about?

“I know, I’ll blog about how I’m getting my presentation together and the deadline is fast approaching. I can’t be the only speaker that often finds themselves up against the deadline and panicking.”

Next 36 hours

Add a bit more content and run through it 2-3 more time and then… RECORD! (technically it looks like I have until the 26th to upload my recording, but I want to get done early).

Conclusion

The above may or may not be a wholly accurate timeline or description of the process I’ve gone through trying to get my presentation ready for Pass Virtual Summit. I may have elided a few details and over-hyped a few others, but in general it’s close to true and accurate. Despite my always best intentions, I find myself often working up close to the deadline for submissions. Since for Summit they want NEW presentations, I can’t simply dust-off one of my previous presentations and use that, so there’s definitely more work involved here.

And honestly up until I learned it was going to be prerecorded, I thought I’d have most of October to work on it. The deadline to get the slides and recordings submitted sort of threw my original timeline for working on it in the dumpster so I’m actually a bit further behind than I expected to be.

On the other hand, I really did learn to use Docker and I think that’s valuable and I am making that part of my presentation. And, when all is said and done, I think I’ll be happy with it. I think though like any good speaker, I’ll look back and think “well next time, I’ll have to improve this or that.” There’s always room for improvement. I’m not keen on giving it prerecorded. I value the instantaneous feedback I get from the audience. So that will be different. But I at least can elicit questions during the presentation and there’s a life Q&A afterwards. But, I’ll still be nervous.

I’m in awe of speakers who get their presentations all prepped and prepared months in advance, but I suspect there’s a number out there like me, that don’t operate that way. And I suspect there’s a few who are even more nervous than I thinking, “OMG, am I the only one in this spot?” Nope, you’re not. Or rather, “Please let me know I’m not the only one!”

See you all at Summit, at least virtually!

And in the meantime there’s another possible deadline coming up I need to think about…

Privilege is a Tailwind

I’ve written about how much I enjoy bicycling previously. Besides being good exercise and a decent way getting from point A to point B, it gives me a chance to think about things. Sometimes it’s deep thoughts, sometimes it’s simply prosaic, as in “hmm, how fast do I need to do this section to keep my average speed up.”

One thought that has run through my head often is the impact of a tailwind or headwind on my average speed. There’s certain truth that I think many bicyclists will agree with and that’s a headwind somehow always finds you. Seriously I’ve done in/out loops (i.e. out X miles and make on the same route) and it seems the wind will reverse directions about half-way through.

In any impact, air resistance is one of the banes of speed. What makes it worse, is the impact is really a square factor, i.e. if you go twice as fast, the impact of air resistance is 4 times as much. This is why it’s fairly easy to bike at say 5 mph, not to bad at 10 mph and much harder at 20 mph and unless you’re a star athlete, to go 40 mph for any real distance on a flat path.

Now, if you’re trying to bike into a headwind, that just multiplies the impact of air resistance. Even a slight headwind can really slow you down.

Fortunately, a tailwind has the opposite impact and can help.

Saturday it was in the 70s here so I decided to get in a longer ride (a bit over 20 miles). It was a fairly blustery day and I didn’t expect to have a great average speed. And I was right. For most of the ride I was actually heading into a headwind and on the sections where I did have a decent tailwind I was climbing hills and already moving slowly so the impact wasn’t very much.

But enough about aerodynamics and back to thinking while biking. While I’ve often thought about the impacts of a headwind vs. tailwind a new analogy dawned on me: tailwind as privilege.

Privilege in this case refers to the systemic advantages one has because simply because of the circumstances of their birth. It doesn’t necessarily mean you had it easy, for example you may have been born into a low-income household, but it does mean you didn’t have artificial constructs placed in front of you as you tried to navigate life. In addition it doesn’t necessarily mean you didn’t have certain advantages, you may be a person of color born into a high-income household.

Let me continue with the analogy.

While biking, if I’ve got a nice tailwind, it feels great. In fact I’m pedaling along effortlessly and don’t have to give much thought to my ride. If I’ve got a headwind, I may be pedaling with all my effort but not moving very fast. And I definitely notice the extra effort.

Privilege is not the quality of my bike. Privilege is not the hills I have to climb or go down.

Privilege is not being born into a neighborhood that suffered with redlining, which means even decades layer home values are depressed which makes it harder to get loans and harder to improve the neighborhood in general.

Privilege is being able to wear what clothing you like without people immediately thinking you’re a criminal.

Privilege is being able to put a photo of your family on your desk without worrying about if your homophobic coworkers will make comments or your boss will consciously or subconsciously take it into consideration at your next review.

Privilege is being able to walk out of a bar holding hands with your sweetie and not worrying if someone is laying in wait to beat you up solely because of who you love.

Privilege is being able to walk into a car dealership and not worrying about if the dealer will take you seriously because of the gender you present.

Privilege is going into a meeting and not having someone ask you to take notes simply because they think women have neater handwriting.

Privilege is being given a 3-speed bike, but being on a course that automatically has a tailwind. When it’s level, you might struggle a bit, but you don’t really notice the air resistance. Hills are an issue, but everyone has trouble with those.

Lack of privilege may be being given a beautiful 21 speed graphite frame bike that weighs practically nothing, but being put on a course with a headwind. For practically the entire ride, you notice the headwind. On level ground, you’re pedaling as hard as you can, but you realize you’re not having it as easy as the bicyclist with the tailwind, regardless of your respective bicycles. On downhills, yeah, gravity helps, but again, you notice the headwind and can’t even coast as easily as the person on the other bike. Sure, both of you may struggle on the uphills, but you realize that once you’re both at the top, again they’re going to have an easier time.

And what’s worse, is the person on the 3-speed will complain about the horrible bike they’ve been given, how lucky you are to have been given the 21 speed and then have the audacity to suggest that you just need to bike harder to keep up, after all, they’re doing just fine on a 3-speed and the tailwind they have has nothing to do with their advantages.

I also noticed something else my ride. The headwind was from the south, and the flattest portion I was biking was southbound. For much of it I had some shelter from the headwind because of trees and the like so it was less noticeable, but the minute I was in an open area without trees, the headwind was definitely noticeable and definitely slowed me down.

Now if the person with the tailwind can upgrade to the same 21 speed graphite frame bike, they will be able to go even faster, but that tailwind will always be there, assisting them. The person with the headwind, no mater how much better their bike is will always have a built-in disadvantage until the wind changes.

In reality, I really only encounter tailwinds while biking. For the other areas of my life, I’ve had a tailwind. I’m not aware of it unless I think about it but it’s there. Don’t mistake for the bicycle you ride for privilege or the lack of privilege. It’s the tailwind that’s the privilege.

I wish everyone, bicycling or not, a strong tailwind.

Projects You’re Proud Of?

When I present, I start my presentations with a brief bio of myself and one item on there I generally have is a comment that I like to solve problems. This may sound obvious, but it’s true and I think describes my goal well. Yesterday, while on a 3 hour zoom call with a client, we got talking about various projects and it made me think about some of the problems I’ve solved over the years.

There are several I could talk about, but one came up yesterday. Several years ago at a previous client, the head of their call center came to me with an issue. They had a process where they’d export their call center logs and input them into SQL Server. Except to call it a process was a bit of an overstatement. It was a series of about 4-5 steps, all except the initial export were done manually. This meant that every morning one of their IT people would take a file from a Linux server, copy it locally, and then import it into Access where several macros were run on it to transform it and then the person would import it into the SQL Server where they could then run reports. There were several possible areas for mistakes to happen and while mistakes weren’t routine, they tended to happen about once or twice a month. On a good day, it would take about 1/2 an hour to do the manual import, on a bad day, over an hour. So in a month, one of their IT people could easily spend 15 or more hours on it, or over 180 hours a year.

In addition, adding new meta-data into the process was error-prone and he couldn’t do as often as he liked. He asked if I could take a look at it and automate it. While SSIS is not an area of expertise, I was familiar enough with it to know it was a good fit and said I’d work on a solution. It took some effort, but eventually I had a solution in place. The entire process now runs automatically in about 5 minutes and he can add or remove the meta-data he needs to by updating a single SQL table. He was quite pleased.

I’m also proud to say the only real time there’s been an issue with the process is when they had to for business reasons IP their entire internal network. They unfortunately scheduled this for a week when I was not only on vacation, but spending that week at some National Parks and Forests in the South Dakota area. The remoteness of these locations meant that my connectivity was very limited. I let their IP team know what changes had to be made to a config file to make things work, but in the aftermath of other issues they had to deal with this was missed. Fortunately, once I found the right place to sit in the National Forest we were camped in and get enough of a cell signal to log into their network, I was able to make the update and fix things. Since then, things have worked without a hitch.

I like this particular project, not just because it’s been so problem free, but because I think I can clearly point to a problem a client had and that I helped solve. Now that IT person can spend their time on more important issues.

It also is an example of a mantra I think is generally true:

Anything that can be automated should be automated.

There’s other projects I may write about at other times (including a few involving PowerShell) but that’s it for today.

What projects are YOU proud of? I’d love to hear from you.