The Song is Over

So the past few weeks I’ve been writing about PASS in general and about Summit. And now like several of my fellow #SQLFamily members who have already blogged, such as Deb Melkin and Andy Levy, I’ve decided to post a post-Summit post.

First Impressions

Virtual Summit was better than I expected it to be. Let me actually correct that a bit, it was much better than I expected. Now, it was not as great as in person, but my fear was virtually it would completely lack any semblance of the social interaction that makes Summit such a great experience. And while the social interaction was greatly diminished, it was still there and that made it a great experience. I will add that Twitter really helped here, both with the #SQLFamily and #PASSSummit hashtags.

My Sessions

I was honored to have the opportunity to speak at two sessions this year. This is a grand total of two more than I’ve ever had given before. Initially I had been selected to give a session on PowerShell for DBA Beginners. I was a bit disappointed to learn it would be a prerecorded session, but took that in stride. I was very curious how it would work. More on that in a bit. A few weeks before Summit I was asked to take part in another session, this time a live panel session All About PowerShell Panel Discussion. I immediately said yes. And then was later reminded by my wife I’d be out of the house taking her to an appointment and back. This was going to complicate things. But I didn’t want to say no, in part because I felt honored to be among such great luminaries: Hamish WatsonBrandon LeachRob SewellBen Miller. So, I decided I’d do it from my car in the parking lot. And since this would be live I was really excited for that, since I had been looking forward to the real-time interactions. The only other drawback was the timing. It was an 8:00 AM EST session on Wednesday, which meant it was one of the first sessions of Summit, and it would be live, so if there were opportunities for things to go wrong, this would be it. Other than Hamish being up at I think about 1:00 AM his time and a wee bit sleep deprived (or as he put it, the entire world now was on Hamish Standard Time) it went really well. He did a great job of moderating and we had a very good turnout and a number of good questions from the audience. I’ve written about PowerShell quite a bit in my blog and for Redgate and feel very strongly that every DBA needs to have some experience with it, so this was a great opportunity for all of us to evangelize a bit. I was really happy with the this session and can’t wait for the recording to be available. It left me in a very energized state for my session at 2:00 PM the same day.

I had realized several days before my 2:00 PM session that there was a benefit of having it prerecorded. I didn’t have the normal butterflies I have before presenting. It was done. I couldn’t change it. I went into it very relaxed. That said, I did make one change to my normal desktop setup. I added a monitor.

Multitasking at Summit for the win!

The upper monitor is generally my TV but has a HDMI input so I added that to my usual setup. This allowed me to have the ARS window up there so I could see questions and comments and answer them or moderate as needed. The lower left is the video chat window. Though in theory this was only needed during the live Q&A session at the end of my session, I opened it right at the beginning and was able to chat and share with others. You can see my accidental selfie in it. The rightmost monitor showed my presentation as attendees would see it.

After chatting with some other presenters I realized most did not go full-bore like I did and just did one window, generally the ARS window, or maybe the ARS window and their presentation muted in another. For me, the setup above worked well and I’d use it again. I’m used to multi-tasking like this and it worked really well. While I couldn’t modify the presentation itself on the fly in response to audience input, I could interact with the audience in a way I hadn’t previously.

One drawback of the system was while my presentation was on, I had no idea how many were actually “attending” it. Before it started the window with the link to it showed 143 people as “attendees” but I have no idea how many actually ended up viewing, but I’ve got to say even a 1/3rd of that number would have been a win for me. I was VERY happy with those numbers. Also the questions I got during the session and during the video chat Q&A after and then via email really pleased me. It seems like I met my goal of generating interest among people was a success.

Another drawback I realized half-way through (due to a mistake on my part of trying something) was that if you came into the session late, you started at the beginning, not at the same point in time as everyone who had started at the start of the session. While later on I think this is ok, I think during the session presentation times, folks should come into “where the session is at that time”. For me, it meant I had to figure out where most of my attendees were at that point in the session.

After I was done I realized, “that was it. My work is done, the rest is just fun now.”

Other Sessions and Events

I found myself, despite work interfering attending probably as many sessions as I might have at an in person Summit. These included Rob Sewell‘s session on Notebooks, PowerShell, and Excel Automation and LGBTQ+ and Pass Local Groups Birds of Feather sessions on Wednesday.

On Thursday I started with Bob Ward‘s Inside Waits, Latches, and Spinlocks Returns (which is so information rich, but at 8:00 AM EST? Really? And what’s worse, is he makes it seem just so natural), part of Erin Stellato‘s Query Store Best Practices and part of the Diversity in Data Panel Discussion: For the Professional Woman, Itzik Ben-Gan’s Workarounds for T-SQL Restrictions and Limitations which again blew me away with how powerful SQL can be in the right hands.

On Friday I moved on to Brand Leach’s SQL Server Configuration And Deployment With Powershell DSC which gave me some great ideas I hope to implement someday. After lunch I caught Ben Miller’s Getting Started with PowerShell as a DBA (I always like to see how others present on similar topics, gives me ideas to compare and contrast and while we had similar topics, very different approaches and I’d recommend people view both). I finished the day and basically the Summit with Panel Discussion: Consulting 101 – Help Us to Help You. Despite being a consultant for many years, I’m always looking for new tips (and new clients, hint hint)

I also attended several of the keynotes and was especially blown away by the Diversity, Equity & Inclusion Keynote by Bärí A. Williams. I would HIGHLY recommend watching that when you get a chance if you didn’t watch it before.

So That Was Summit

So technically that was Summit. I learned a lot and had a great time. But, I have to talk about some of the drawbacks and disappointments.

For the vendors, I think Summit was a bust. This is unfortunate. I think it’s just harder to do it this way. One thing I noticed is that some vendors advertised “one on one” video chats. I avoided them because I didn’t want to tie up precious resources just being sociable (I don’t have much vendor needs these days). But it turns out in at least one case it was really a 1:Many relationship and the vendor would have welcomed more folks just stopping by. I think that’s on the vendors for not being clear enough in their own descriptions. But that said, even with that change, I think an issue with “stopping by a booth” is there’s more pressure to make it solely productive and not about being social. I don’t know how to change that. I’ll also admit I quickly gave up on trying to collect my points or whatever it was like I would stamps at the in person event. I was told this was more straightforward on the mobile app, but I had no desire to download that, especially since I was attending from my desktop. That said, I think in general vendors struggle with making virtual events worth their time and money. That last one is important because it’s what makes PASS possible. So, perhaps it’s still worth showing a vendor some love and mention you saw their name at Summit.

Overall, I’d say I think the prerecorded sessions and the ARS/Video chat stuff went better than I had hoped for. I’d probably do it again if I had to. I really only had two issues. For the prerecorded sessions there was no way to “pop” it out or expand the presentation screen. You were forced to have he Chat/Comment sidebar at all times. This took up precious screen space. For some reason on the live sessions you had this ability. This should have been made available on the prerecorded sessions. Also, it appeared the session window did not scale. i.e. if you had a monitor with higher resolution, it simply kept a certain mount of space around the presentation itself. Overall, the session window did NOT take good use of screen real-estate. This was compounded by the fact that some presenters (me included) did not make their fonts large enough. On my screen when I was recording, the size was great, but once in the presentation window, for many nearly unreadable. I know at least one person left my session because of that. I’ll own up to the fact I should have better headed the recommendations and probably gone overboard on font size, but the fact that screen real estate was so poorly used only exacerbated the situation.

I was disappointed in the turn-out for the two Birds of a Feather sessions I attended. I think the timing was rough, especially for folks on the East coast and perhaps Central timezones. Honestly, I think the Birds of a Feather and some of the other social times should have had FAR wider windows of time, perhaps from lunch until dinner or past. Take advantage of the fact that folks are in different timezones to get more moderators. I know I’d have attended more Birds of a Feather sessions had they been available at times other than when I was making dinner (or eating my salad).

That aside, the one issue that quite honestly angered me and I felt there was no excuse for was the horrible closed-captioning. When I first heard about it I was excited because I’m a firm believer in accessibility. All speakers were told we had to have our sessions recorded early enough so that closed-captioning could be applied. Given the time frame I had wrongly assumed this included time for a Mark I human brain review. It was VERY apparent that the closed captioning was purely automated and had not been reviewed. Some of the errors were comical, apparently at one point I was talking about T-CPU and not T-SQL, and another presenter was creepily talking about skin. Other errors made the presentation at times seem senseless. I had more than one person comment that the real-time capabilities of PowerPoint did a better job in their experience. Pretty much every speaker I spoke with had similar complaints. So, in conclusion I’ll say, I’m not sure the point of having stuff in so early when current realtime tools from other vendors can already do a better job. If you have two weeks to review the closed-captioning, I highly recommend outsourcing it to a human to review. Or somehow give speakers the ability to touch it up (if that was a possibility neither I nor any other speaker I spoke to was aware of it, and it was not on our speaker checklist on the dashboard). Honestly, not only do I think there was no excuse for the poor quality, I think it did an actual disservice to any hearing impaired people trying to attend.


By the time you read this, it’s probably too late, but if you haven’t VOTE OR YOUR PASS BOARD if you’re eligible. I’ll be blunt, we’re at a crossroads with PASS and we may not have it a year from now. But no matter what happens, if you’re eligible to vote and failed to do so, I really don’t want to hear you kvetching about the future of PASS.

And while it’s too late to register for Summit, if you have already, remember, you get access to ALL the sessions for the next 12 months. Take advantage of that!

Caving and SQL

Longtime readers know that I spend a lot of my time talking about and teaching caving, more specifically cave rescue, and SQL Server, more specifically the operations side. While in some ways they are very different, there are areas where they overlap. In fact I wrote a book taking lessons from both, and airplane crashes to talk about IT Disaster Management.

Last week is a week where both had an overlap. One of the grottoes in the NSS (think like a SQL User Group) sponsored a talk on Diversity and Inclusion in the caving community. The next day, SQL Pass had a virtual panel on the exact same subject.


Let me start with saying that one thing I appreciate about both communities is that they will welcome pretty much anyone. You show up and ask to be involved and someone will generally point you in the right direction.  In fact several years ago, I heard an Oracle DBA mention how different the SQL community was from his Oracle experience, and how welcoming and sharing we could be.

This is true in the caving community. I recall an incident decades ago where someone from out of town called up a caving friend he found in the NSS memberhsip manual and said, “hey, I hear you go caving every Friday, can I join you?” The answer was of course yes.  I know I can go many places in this country, look up a caver and instantly be pointed to a great restaurant, some great caves and even possibly some crash space to sleep.

So let’s be clear, BOTH communities are very welcoming.

And I hear that a lot when the topic of diversity and inclusion comes along. “Oh we welcome anyone. They just have to ask.”


Well, there’s two issues there and they’re similar in both communities. The less obvious one is that often anyone is welcome, but after that, there’s barriers, some obvious, some less so. Newcomers start to hear the subtle comments, the subtle behaviors. For example, in caving, modesty is often not a big deal. After crawling out of a wet muddy hole, you may think nothing of tearing off your clothes in the parking lot and changing. Perhaps you’re standing behind a car door but that’s about it. It’s second nature, it’s not big deal. But imagine now that you’re the only woman in that group. Sure, you were welcomed into the fold and had a blast caving, how comfortable are you with this sudden lack of modesty? Or you’re a man, but come from a cultural or religious background where modesty is a high premium?

In the SQL world, no one is getting naked in the datacenters (I hope). But, it can be subtle things there too. “Hey dudes, you all want to go out for drinks?” Now many folks will argue, “dudes is gender neutral”. And I think in most cases it’s INTENDED to be. But, turn around and ask them, “are you attracted to dudes?” and suddenly you see there is still a gender attached.  There’s other behaviors to. There’s the classic case of when a manager switched email signatures with one of his reports and how the attitudes of the customers changed, simply based on whose signature was on the email.

So yes, both groups definitely can WELCOME new folks and folks outside of the majority, but do the folks they welcome remain welcomed? From talking to people who aren’t in the majority, the answer I often get is “not much.”

An Interlude

“But Greg, I know….” insert BIPOC or woman or other member of a minority.  “They’re a great DBA” or “They’re a great caver! Really active in the community.”  And you’re right. But you’re also seeing the survivorship bias. In some cases, they did find themselves in a more welcoming space that continued to be welcoming. In some cases you’re seeing the ones who forged on anyway. But think about it, half our population is made up of women. Why aren’t 1/2 our DBAs?  In fact, the number of women in IT is declining! And if you consider the number of women in high school or college who express an interest in IT and compare it to those in in their 30s, you’ll find the number drops. Women are welcome, until they’re not.

In the caving community during an on-line discussion where people of color were speaking up about the barriers they faced, one person, a white male basically said, “there’s no racism in caving, we’ll welcome anyone.”  A POC pointed out that “as a black man in the South, trust me, I do NOT feel safe walking through a field to a cave.”  The white man continued to say, “sure, but there’s no racism in caving” completely dismissing the other responder’s concerns.

There’s Still More…

The final point I want to make however is that “we welcome people” is a necessary, but not sufficient step. Yes, I will say pretty much every caver I know will welcome anyone who shows an interest. But that’s not enough. For one thing, for many communities, simply enjoying the outdoors is something that’s not a large part of their cultural.  This may mean that they’re not even aware that caving is a possibility. Or that even if it is, they may not know how to reach out and find someone to take them caving.

Even if they overcome that hurdle, while caving can be done on the cheap, there is still the matter of getting some clothing, a helmet, some lights. There’s the matter of getting TO the cave.

In the SQL world, yes anyone is welcome to a SQL Saturday, but what if they don’t have a car? Is mass transit an option? What if they are hearing impaired? (I’ve tried unsuccessfully 2 years in a row to try to provide an ASL interpreter for our local SQL Saturday. I’m going to keep trying). What if they’re a single parent? During the work week they may have school and daycare options, but that may not be possible for a SQL Saturday or even an afterhours event. I even had something pointed out to me, during my talk on how to present, that someone in the audience had not realized up until I mentioned it, that I was using a laser pointer. Why? Because they were colorblind and never saw the red dot. It was something that I, a non-colorblind person had never even considered. And now I wonder, how many other colorblind folks had the same issue, but never said anything?

In Conclusion

It’s easy and honestly tempting to say, “hey, we welcome anyone” and think that’s all there is to it. The truth is, it takes a LOT more than that. If nothing else, if you’re like me, an older, cis-het white male, take the time to sit in on various diversity panels and LISTEN. If you’re invited to ask questions or participate, do so, but in a way that acknowledges your position. Try not to project your experiences on to another. Only once have I avoided a field to get to a cave, because the farmer kept his bull there. But I should not project MY lack of fear about crossing a field onto members of the community who HAVE experienced that.

Listen for barriers and work to remove them. Believe others when they mention a barrier. They may not be barriers for you, but they are for others. When you can, try to remove them BEFORE others bring them up. Don’t assume a barrier doesn’t exist because no one mentions it. Don’t say, “is it ok if I use a red laser pointer?” because you’re now putting a colorblind person on the spot and singling them out. That will discourage them. For example find a “software” pointer (on my list of things to do) that will highlight items directly on the screen. This also works great for large rooms where there may be multiple projection screens in use.

If caving, don’t just assume, “oh folks know how to find us” reach out to community groups and ask them if they’re interested and offer to help. (note I did try this this year, but never heard back and because of the impact of Covid, am waiting until next year to try again.)

Don’t take offense. Unless someone says, “hey, Greg, you know you do…” they’re not talking about you specifically, but about an entire system. And no one is expecting you to personally fix the entire system, but simply to work to improve it where you can. It’s a team effort. That said, maybe you do get called out. I had a friend call me out on a tweet I made. She did so privately. And she did so because, she knew I’d listen. I appreciated that. She recognized I was human and I make mistakes and that given the chance, I’ll listen and learn. How can one take offense at that? I saw it has a sign of caring.

Finally realize, none of us are perfect, but we can always strive to do better.

So, today give some thought about how you can not only claim your community, whatever it may be, is welcoming, but what efforts you can make to ensure it is.


On a separate note, check out my latest writing for Red-Gate, part II on Parameters in PowerShell.


Years ago, I had my team building out our racks at our new datacenter. I was quite proud of it. It was going to be our first planned from the start build-out of 6 racks, as opposed to the hodge-podge build-out we had done of 5 cabinets we had previously rented. Instead of just cramming in equipment where it would fit, we could plan where every piece would go and where we’d leave room for future expansion. This was in 2001, so it was still during a big Internet boom.

One of the things I had decided on doing early on was color coding cables. Red was for anything in front of the firewall for example.  On the backside, every server had two network cards, one for outgoing traffic (the “front-net”) and the second for traffic between the servers (the “back-net”).  To help distinguish between the two, I had ordered a bunch of green cables for the front-net, since that data was “safe” and green is “safe”, and blue cables for the back-net, both start with “b”. Sure, somewhat silly mnemonics, but they worked.

Until, about a week after we finally completed our datacenter move, not one, but two members of my five person team commented, “oh, they were different colors? I couldn’t tell, I’m colorblind.”

“Doh!”  So much for my nice color-coded system.  It can be fairly easy to overlook barriers when you don’t see them. Sometimes it takes more thought and action on your part. Sometimes it takes asking questions, or observation.

Lately I’ve been trying to look for more barriers that I might not have seen before and looking into what I can do to remove them. I’ll be the first to admit, I’m not always successful and I’m still learning. But hopefully we call can.

One area I’ve been focusing on this is in my work for the Capital Area SQL Server User Group. Right now I’m looking at two possible barriers. I say possible because I honestly don’t know if they’re issues or not:

First, I’m trying to find someone who can provide ASL interpretation.  Here’s the thing: we have never had, as far as I know, a deaf person attend one of our events, or even express an interest. Is that because there are no deaf DBAs in the area or because they know if they do attend, they probably will face barriers an person with hearing won’t face?

But, that actually begs the question: if there are no deaf DBAs in the area, why? Perhaps there are deaf people who WANT to become a DBA, but can’t because the barriers that exist well before they even attempt to attend one of our events.  I don’t know, but I hope to explore this issue a bit more.

Another item I’ve started to look into, is whether some sort of child-care services at our SQL Saturday event would help encourage more people to attend. My initial thought is, “it’s Saturday, so ideally a spouse can watch kids” or a similar solution. But, that’s assuming every attendee has a spouse or the extra money to hire a babysitter for an entire day. In other words, it’s making a lot of assumptions.  There’s definitely some major logistical concerns that I have to continue to explore before we can even think about offering it. But I’m also simply trying to figure out if it would make a difference.  Unfortunately, currently for our user group meetings itself, it would not be practical. But even then it may be worth looking into.

On a personal note, I have a friend who had a service dog. She was interested in joining me on a caving trip.  So we actually discussed the logistics of it and determined that it was in fact possible to take her caving with her service dog.  There was some logistics we had to work out and I did have to get permission from the cave owner.  Unfortunately, our scheduling never quite synched up and we had to forego the trip. But the point is, barriers CAN be overcome if one works at them and is willing to be a bit flexible.

Today’s takeaway: What barriers have you looked for and tried to remove? They’re out there, even if you can’t see them.