February CASSUG Monthly Meeting

Our February meeting will again be online. NOTE: you MUST RSVP to this Meetup at https://www.meetup.com/Capital-Area-SQL-Server-User-Group/events/275968506/ to view the Zoom URL!

Our February guest speaker is Elizabeth Noble!

Topic: Streamline Database Deployments

Our online meeting schedule is as follows:
6:00: General chat, discussion, and announcements
6:30: Presentation
We usually wrap up between 7:30 PM and 8:00 PM.

Please RSVP to this Meetup, then use the online event URL to join (note: you MUST RSVP for the URL to be visible). We will send out a meeting password as we get closer to the event.

Thanks to our sponsor, Datto, for making this event possible!

Setting up my #Sessionize profile, and speaking opportunities — #DataSaturday

The other day, I wrote about how Data Saturday — the successor to SQL Saturday — was making use of Sessionize for event applications and scheduling. In order to take advantage of the technology, not to mention future opportunities to speak, I took the time to work on my Sessionize profile.

It turned out to be a lot of work — much more than I expected. I already had my bio and my presentation descriptions within the application, but I discovered a number of other features that, I believe, will present me with additional opportunities to speak.

First, while Sessionize keeps track of events to which you apply through its application, I discovered that it also has the ability to enter external events not scheduled through Sessionize. Even the header on the external events page says, “Organizers love to see your talk history” (and I agree). So, I went through my presentations page to enter all my previous speaking engagements that I did not schedule through Sessionize.

Did I mention that it was a lot of work? I started speaking regularly in 2015. In that time (until now), I’ve spoken at 26 SQL Saturdays, two PASS Summits, seven in-person user group meetings, three professional development virtual meetings, and a podcast. Granted, I know people who’ve spoken at more events than I have, but still, that’s a lot of speaking engagements. I added them to my external events, including descriptions and web links (where applicable — since PASS.org is no longer active, I linked the SQL Saturday pages to the schedule PDFs that I downloaded several weeks ago, and a few other links to any YouTube presentation links I had available).

I also discovered that Sessionize has an option called “discover events” — a feature that allows you to discover potential speaking opportunities. I had gone through the Data Saturdays site to apply to speak at (virtual) events in Redmond and LA, but when I saw the “discover events” option, I got curious.

As it turned out, in order to use this option, I had to fill out sections for areas of expertise and topics, so I filled them out as best I could. Once I did so, I was able to view (and apply to) potential events. In addition to the two Data Saturday events, I also applied to the VTTA Tech Conference and Techorama 2021. (And Sessionize says that I still have an active application to speak at Albany Code Camp, where I’d applied last year, but the event was wiped out by the pandemic.) I think I have a decent shot at the Vermont tech conference, and I have my doubts about being accepted to Techorama, but I figure, you never know until you try.

So far, I do like the Sessionize application. It does a good job of keeping track of my profile and my speaking engagements, and it could potentially open up more speaking opportunities. I’ll admit that I felt some trepidation after PASS (and SQL Saturday) ceased to exist. I wanted to continue speaking at events, and I wasn’t sure how to approach it once the SQL Saturday window closed. We’ll see what speaking opportunities open up with this application.

#DataSaturday

After the demise of PASS, a common question among data enthusiasts and PASS members was, “what happens with SQL Saturday?” SQL Saturday was backed by PASS, and as such, when PASS disappeared, so did SQL Saturday.

Enter Data Saturdays, the successor to SQL Saturday. As I write this, the first Data Saturday is in progress, in Guatemala (virtually, of course).

I’ve applied to speak at the first Data Saturday in the US (so far), event #5 in Redmond, WA on April 17. I submitted three sessions: my presentations on ‘blogging, job hunting, and networking.

When I submitted my sessions, I was a little surprised to see my information come up in the speaker’s profile. My initial thought was that they had exported and imported my profile and presentation info from the PASS.org site, but I don’t think this is the case. Data Saturday uses Sessionize to coordinate events, and as it turned out, I already had a Sessionize profile; I had created it last year for Albany Code Camp, where I had applied to speak last year; of course, the event was wiped out due to COVID. I did notice, on my Sessionize profile, that my submissions are in evaluation for Albany Code Camp on September 25, so I’m assuming that that event is rescheduled for that date.

We’ll see if I’m picked to speak for the Redmond event. There are a number of additional Data Saturday events listed as well; I haven’t yet decided what other events I’ll apply to speak. Even though the events are virtual (for now), they still require some work, and I’m wary of spreading myself too thin, despite my desire to speak at more events.

In any case, I’m looking forward to participating in this next endeavor. I’m looking forward to contributing toward these conferences, and, as always, I’m also looking forward to reconnecting with my #SQLFamily friends.

January CASSUG Monthly Meeting

Our January meeting will again be online. NOTE: you MUST RSVP to this Meetup (https://www.meetup.com/Capital-Area-SQL…/events/275432320/) to view the Zoom URL!

Our January guest speaker is Bob Ward!

Topic: SQL Server Edge to Cloud

SQL Server is everywhere you need it from the IOT Edge to your cloud to public clouds. With all of these options it can be difficult to know which to choose and why each options may be right for your data needs. In this presentation, I’ll review with you all the current released and preview versions of SQL Server from the edge to the cloud. I’ll compare each of them and discuss why you want to get ahead of the curve by understand what is possible with the modern SQL Server. I’ll discuss technical details of some of these options so you can understand what SQL Server flavor fits your company needs. This session will include some demos to highlight key innovations with SQL Server.

About Bob:

Bob Ward is a Principal Architect for the Microsoft Azure Data SQL Server team, which owns the development for all SQL Server versions. Bob has worked for Microsoft for 26+ years on every version of SQL Server shipped from OS/2 1.1 to SQL Server 2019 including Azure SQL. Bob is a well-known speaker on SQL Server, often presenting talks on new releases, internals, and performance at events such as PASS Summit, Red Hat Summit, Microsoft Ready, SQLBits, SQLIntersection, Microsoft Inspire, and Microsoft Ignite. You can follow him at @bobwardms or linkedin.com/in/bobwardms. Bob is the author of the books Pro SQL Server on Linux and SQL Server 2019 Revealed available from Apress Media.

Our online meeting schedule is as follows:
6:00: General chat, discussion, and announcements
6:30: Presentation
We usually wrap up between 7:30 PM and 8:00 PM.

Please RSVP to this Meetup (use the link above), then use the online event URL to join (note: you MUST RSVP for the URL to be visible). We will send out a meeting password as we get closer to the event.

Thanks to our sponsor, Datto, for making this event possible!

Requiem for #PASS — #SQLFamily

Many data professionals, myself included, are shocked and saddened by the announcement that PASS will cease operation on January 15, 2021. I’m sure that a large number of data ‘bloggers will be posting their thoughts regarding PASS’s announcement; this is only one of many such articles, I’m sure.

I know that PASS has been under a great deal of scrutiny by its members, and even I, myself, have been critical of PASS in the past. Three members of the board of directors resigned within the past few weeks, and the organization had been consulting with legal experts regarding its future.

I’ve always taken great pains to be apolitical (it’s one of my most, if not the most, hated topics to discuss). I don’t know much about any of PASS’s inner workings or governance, and quite frankly, I don’t want to know. I’m sure there’s a lot they could’ve done better, but I’ve never been privy to it. (Indeed, one frequent criticism I’ve heard has been their transparency — or lack of.)

As someone who has been a member of PASS for some time (since attending my very first SQL Saturday in New York City in 2010), I would prefer to talk about everything that PASS has given me. So I wanted to take some time to reflect on the things that PASS has done to enhance my professional career.

When I attended my first SQL Saturday (#39 in New York City back in 2010), I knew right away that I wanted to be involved and contribute to the community. The question was, how? I remember looking around at other attendees at the Microsoft office (back then, it was held next to Radio City, not at the Times Square location like it is now) and saying to myself, “these people probably know more about SQL Server than I do. What can I contribute to this organization?”

On that same trip, I met Dan Bowlin on the train heading down to the City. Along with Joe Barth, the three of us founded the Albany SQL user group. Through my association with that group, I also met Greg Moore and Ed Pollack; the three of us currently maintain the group’s leadership team. Since those humble beginnings, our user group has remained strong. We hold our own when compared to user groups in larger cities; indeed, we frequently say that we “punch above our weight.” And although Dan and Joe moved out of the area several years ago, I still remain friends with them to this day.

One evening, during one of our user group meetings, I had a thought: I’ve been adept at talking the language of technology to people who don’t understand it. Would that make for a good presentation? As that meeting progressed, I jotted some notes down; by the end of the meeting, I had enough fodder for an entire presentation. I ran my idea past a few people, including Greg and Ed. They all told me, that was a great idea! Run with it!

That idea became my very first presentation, which I first presented in 2015. Since then, I’ve presented that session at several SQL Saturdays and at PASS Summit.

I wrote previously about what happened after that first presentation. I discovered that I enjoyed presenting and attending events such as SQL Saturday. Additionally, I also noticed some subtle changes to my professional development. I found that I was passively getting better at what I did. I gained more confidence in my abilities, I became more assertive, and I was increasingly being recognized for the things I did. I even remember one manager telling me, “we recognize what you’re doing with all these conferences where you’re speaking; keep up the good work!”

I now have several presentations that I do. I have presented at numerous SQL Saturdays, PASS Summit, and a number of user groups, both in-person and virtual. I even did a podcast!

It wasn’t all about professional development. I made a number of friends through my involvement with PASS and SQL Saturday — people I likely wouldn’t have otherwise met, and whom I love dearly. In addition to my association with PASS, I’ve connected with these people through Twitter, LinkedIn, and Facebook. These people have become a part of my life, and I am as close to these people as I am to any of my family or circles of friends. And because of this, my professional network is stronger than ever.

I love to travel. I wish I could do more of it (usually, lack of time or money — and these days, the pandemic — keeps me from doing more of it). I’ve written before about my SQL Saturday (and other PASS) travels. These speaking opportunities gave me chances to visit places I don’t normally get to see, not to mention that they got me out of Dodge for a little while.

I attribute all of this as things that PASS has given me.

I’ve been thinking about whether or not it would be feasible to resurrect PASS. In addition to PASS, I am also a member of STC. Unlike PASS, STC charges dues to its members (using a tiered structure — the amount of dues you pay depends on your tier). Conceptually, STC is very similar to PASS; they are a professional organization that represents a specific profession (PASS represents data professionals; STC represents technical communicators). STC also does a number of things that PASS did not do; they have publications that they publish regularly, for example. If PASS is able to reorganize, I’m wondering if they’d be open to restructuring using a model such as STC. Of course, I suspect one of the reasons why PASS was popular was that they didn’t charge dues. If PASS is to be solvent, that might be something to consider.

I think it’s important for professionals in any field to have an organization such as PASS. They provide opportunities for networking, guidance, reference, and development that wouldn’t otherwise exist anywhere else. What PASS has done for my career and professional development is incalculable. The demise of PASS represents a big, big loss. I sincerely hope that PASS is able to come back in some way, shape, or form, and be stronger than ever in doing so.

#SQLSaturday Minnesota — the debrief #SQLSat1017 #SQLSatMN

I don’t think I have to tell anyone what a crazy year 2020 has been (and I won’t belabor the point). As such, many of us have had their fill of Zoom meetings and virtual conferences. I’ve heard a lot from people, myself included, about their dealings with pandemic fatigue and how burned out they are by virtual conferences.

And then, along came Minnesota SQL Saturday.

Before today, I’d spoken at or attended four virtual PASS events: SQL Saturdays in Albany, Memphis, and Montreal, and PASS Summit. In spite of the challenges faced with putting on virtual events — uncharted territory for all of us — the events went about as well as they could. There were glitches and lessons learned, but for the most part, they went about as well as virtual conferences — being put on for the first time — could go.

Minnesota, however, raised the bar. The event went through a great deal of thought and planning, and it showed. This is not a slight against other events, as we were all breaking new ground in putting together virtual events; rather, Minnesota demonstrated a better way to do it.

I’ll start with Friday night. At many of the in-person SQL Saturday events where I’ve spoken, organizers put together a speaker’s dinner on Friday night. In lieu of that, Minnesota organized a Zoom session allowing speakers to get to know the organizers and other speakers (Memphis did the same thing). In addition, however, Minnesota also organized a test run using GoToMeeting sessions (the virtual meeting application of choice by PASS) to make sure that speakers could test their sessions and get comfortable with presenting online. Although I’d previously presented via GoToMeeting before, I found that this went a long way with helping me to get comfortable with the technology, the session, and knowing what to expect.

Additionally, throughout the day for SQL Saturday, the Minnesota crew set up a separate chat application using Discord (an application that I understand is popular with gamers). Through this application, speakers and attendees had an avenue through which they could mingle and chat using different channels. They had channels set up for each meeting room, as well as a “lunch room” (where people could converse during lunch) and a speaker’s channel (roughly the equivalent of a speaker room). I don’t remember all the channels they had set up — I do remember channels called #jobs and #hallway — but I thought using this application was a great move.

One of the things that is sorely missing from virtual SQL Saturdays is the ability to randomly converse and chat. At in-person events, one of the best parts is to randomly bump into #SQLFamily and chat about a variety of subjects, or randomly start chatting about session topics in the hallway, or whatever. Networking is a huge part of SQL Saturday. By nature, that dynamic is nearly impossible to duplicate at a virtual event. Of course, no virtual event can ever duplicate the things you’d experience at an in-person event. But by employing a technology such as Discord, they managed to fill that gap quite nicely.

I also liked that room moderators introduced speakers and topics. They all included slides to start each session, which also included reminders to solicit the sponsors, their local user group, and various other standard announcements. The format was similar to PASS virtual groups, where the group moderator would start with the intro before the speaker went into his or her presentation.

Overall, Minnesota did a great job with their virtual SQL Saturday. Bravo! They demonstrated that a virtual event could still be exciting and fun, and not the same old virtual event that everyone else does. Granted, I’m looking forward to when we can start attending in-person events again. But by employing out-of-the-box ideas like these, virtual events don’t have to be the same old, same old log-into-a-virtual-room events that we’ve become accustomed to experiencing.

Reminder: I’m speaking at #SQLSaturday this weekend #SQLSat1017

This is a reminder that I will be speaking at virtual SQL Saturday #1017 (Minnesota) this Saturday, December 12.

A vast number of people, myself included, are looking for work. I will do my presentation titled “I lost my job! Now what?!?” this Saturday. I will discuss topics that include, among other things, dealing with the emotional impact, resumes, interviewing, and things you can do to hold yourself over during this period of uncertainty.

Hope to see you virtually this Saturday!

Reinventing the #resume (again) #JobHunt

I had a conversation today with a recruiter — technically, it was an interview, but the way we spoke, it was more of a conversation between an agent (her) and a client (me) — who gave me some advice regarding my resume. I came away from the conversation with a few insights, and I’d like to share those insights here. This is not the first time I’ve written about resumes. I continually learn something new about them.

We left the conversation with her giving me a homework assignment: revamp my resume to incorporate what we had discussed.

Probably the biggest takeaway was to rethink how I was presenting my resume. I shouldn’t have the mindset of a job seeker telling prospective employers to hire me. Rather, I needed to approach it as a marketer. I’m marketing a product. The product I’m marketing is me.

This mindset is important. When you’re trying to present yourself to an employer, you feel a need to impress them with your extensive experience, everything you’ve done, and the many reasons why the employer should hire you. But if you’re marketing yourself, the thought process shifts. Instead, you’re advertising yourself and your skills. “Hire me! Here’s why!” She told me that it’s okay to not put everything on your resume — not lie, mind you, but rather, not throw in the kitchen sink when putting your resume together. Just highlight the important selling points. If they want to know more, they can refer to your LinkedIn profile — and maybe even call you in for an interview (which, of course, is the purpose of a resume).

I found this to be profound, because this is a point that I espouse as a technical writer, and yet I don’t practice what I preach when it comes to my resume. I am a believer in not necessarily including everything on a document. And yet it never occurred to me to apply my own technical writing skills to my own resume. Don’t try to provide every little detail. If they’re interested, they’ll ask for more (and if they want more, they can look at my LinkedIn profile).

I mentioned ageism as a concern, and a possible reason as to why I haven’t had a job nibble in seven months. (I believe ageism exists in the job hunt; it is illegal, but is nearly impossible to prove.) In the same vein of not needing to include everything, one of the takeaways was to only list positions for the past ten or so years. One of my concerns was that my experience before 2009 would likely reveal my age, but at the same time, it was all professionally relevant, and I didn’t want to leave it off. She suggested an idea that had never occurred to me: list the jobs (employer and title), but leave off the dates. Just say “here’s where I worked before 2009.” Again, if an employer wants to know more about those positions, check out my LinkedIn.

As an afterthought, after I’d removed the dates from the older positions, I still had a potential age identifier on my resume: my educational experience included my dates of graduation. Sure enough, in my latest resume revamp, my graduation dates will be removed. Employers just need to know I have a Masters degree; they don’t have to know when I got it.

The recruiter also asked me another question: what accomplishment at each position are you proudest of? I have to admit that that was a good question. She said that it was a question that should be asked for every listed position, and the answer for each was something that should be included on the resume.

I was told, be your own client. Market yourself. When it comes to marketing yourself, you’re your own blind spot. Only when it was pointed out to me did I know that the blind spot was even there.

Upcoming speaking engagements (as of 12/1/2020) #SQLSaturday

I received an email this morning about an upcoming speaking engagement, so I figured it was time to update my list.

I received word this morning that I will be speaking at Minnesota virtual SQL Saturday on December 12. I will be doing my job hunt presentation (which reminds me: I still need to update my slides).

Anyone can register for SQL Saturday, and it’s free to do so. (And you don’t even have to be a techno-geek to attend!) Go to the site to register for this event.

Hope to see you online on December 12!

#PASSSummit2020 part 5: The debrief #PASSSummit #PASSVirtualSummit

(Ed. Note: I had intended to get this out last week, but a family emergency prevented me from doing so, so this article is a week later than I’d wanted to post.)

Now that I’ve had the weekend to recover from a busy PASS Summit 2020 week, I can write about my thoughts and impressions.

Overall, I thought PASS did a good job with holding a virtual PASS Summit under trying pandemic circumstances. These are, after all, trying times, and we have to play the cards that we’re dealt. That said, there were some glitches.

I’ll start with my own presentation. I had prerecorded my session, per instructions from PASS. My initial impression was that I would do my presentation live, and the recorded session would serve as a backup in case I ran into any problems with my presentation. That turned out not to be the case. PASS used my prerecorded presentation. I was, however, required to stand by to field any questions from attendees.

So, before the appointed time, I logged in and opened a chat window. My friend Andy Levy was kind enough to join me in the video chat room, and we chatted about a variety of topics while we waited.

The appointed time arrived, so I started my video. I found that it was impossible to monitor the chat rooms to field questions and to watch the video at the same time, so I turned off the video; after all, I had no pressing need to watch my own prerecorded presentation — or so I thought. I found out, much to my chagrin, that a number of slides had no audio to go with it.

This was a big disappointment. My first instinct was to point the finger at PASS and tell them, “your technology didn’t work,” but that would’ve been disingenuous on my part. When I prerecorded my session a while back, I went back and did a quick listen of each section I recorded to make sure it was okay. When I was finished, I watched some of the presentation, but not all, and that was my mistake. I probably should’ve watched the entire presentation to make sure it was okay, but I didn’t. That was a mistake on my part to which I will own up. That said, it’s my understanding that there were a number of other presentations that also had audio problems (in fact, I tried to sit in on one that had issues, and they ended up rescheduling it — for a time that I couldn’t attend), so I’m guessing that it might not have entirely been on me.

I did post to the chat that I was available in the chat room for any questions, and a few attendees took me up on it. We ended up having a great discussion (and Andy, who also has his own ‘blog, was great with answering some questions and contributing to the conversation). In that sense, we ended up making lemonade out of the technical lemons.

That said, I haven’t yet looked at the feedback, and I don’t look forward to doing so.

A few of my friends also wrote their impressions of PASS Virtual Summit. I haven’t yet had a chance to read them, but I’m posting them here, both for you to peruse and for my own reference.

With that, here are a few of my quick thoughts regarding PASS Virtual Summit 2020.

As I mentioned earlier, these are trying times, and PASS did a decent job with Summit, given the cards they were dealt. The pandemic has affected them, as well as many of the rest of us (as of this article, I’m still looking for a job — it’s been over six months now), and PASS is dealing with those effects. As critical as I — and others — might be of PASS, I want them to survive, and I sincerely hope that they’re still around when we emerge from the other side of this pandemic.

I was not particularly fond of their decision to make use of mostly prerecorded sessions. I would have much preferred to have done my session live. PASS’s concern was with potential technical glitches with live sessions, so their thinking was that a prerecorded session would alleviate that situation. In fact, the opposite happened. The prerecorded session was the glitch, and I never had a problem with my live connection. While I understand why PASS decided to do it that way, I found the decision to be somewhat questionable.

(And if anyone reading this would like to see my presentation, I did this same presentation for the Professional Development Virtual Group back in January. You can view the recording of my January presentation here.)

Overall, I did enjoy PASS Virtual Summit, but as anyone who has attended PASS Summit or other virtual events can attest, the experience just isn’t the same. For me, a huge part of the appeal of events like these is the opportunity to network and to connect with my friends whom I don’t get to see that frequently. To their credit, PASS made accommodations with networking events and channels, but there’s only so much you can do, and only so many people you can see, with online channels. There’s something to be said about randomly bumping into one of your friends while walking down the hall.

Another big part is the travel. I love to travel, and I wish I could do more of it (pandemic aside, usually the lack of time or lack of money keeps me from traveling more). I enjoyed visiting Seattle last year, one of my favorite west coast cities to visit. This year’s Summit would’ve been in Houston, a city I’ve only visited once before.

Overall, I enjoyed PASS Virtual Summit, but it was not without its faults. Hopefully, PASS can take the feedback and lessons learned from this event, and use it to create a truly spectacular experience the next time around. Hopefully, the pandemic will be over for the next time, but these days, you can never tell.