I’m speaking at NYC #SQLSaturday #SQLSatNYC

I found out over the weekend that I’ve been selected to speak at SQL Saturday NYC on May 6! This is one of my favorite events, and I try to attend every year. To the best of my memory, I’ve only missed one SQL Saturday, as either a speaker or an attendee, in NYC since they’ve been holding this event.

I will be doing two presentations:

  • Disaster Documents: The role of documentation in disaster recovery — Documentation is a critical part of disaster recovery. This became evident on September 11, 2001. At the time, I was working for a company that had an office in the World Trade Center. When the towers fell, documentation was a critical for our recovery. In this presentation, I tell my story of how documentation played a role in helping my organization recover from that fateful day.
  • Whacha just say? Talking technology to non technical people — The language of technology might as well be a foreign language to people who don’t understand technology. In this session, I talk about how non-technologists can be overwhelmed by this language, and offer tips as to what technical people can do to convey that language.

New York SQL Saturday is always a good time! I hope to see you there on May 6!

Advertisement

March Monthly CASSUG Meeting

Greetings, data enthusiasts!

Our March meeting is scheduled for Monday, March 13, at 5:30 pm! We will meet in person at Datto, 33 Tech Valley Drive, East Greenbush, NY.

This will be a hybrid meeting!

  • For those joining us in person, we will meet in person at Datto, 33 Tech Valley Drive, East Greenbush, NY.
  • For those joining us online, use the Zoom link to join the meeting. We will send out the passcode as we get closer to the date. You MUST RSVP for the Zoom link to be visible!

For more information and to RSVP, go to our Meetup event page at https://www.meetup.com/capital-area-sql-server-user-group/events/290678782/

Our meeting schedule is usually as follows:

  • 5:30 PM: Food, soft drinks, and networking
  • 6:15 PM: Chapter news and announcements
  • 6:30 PM: Presentation

We usually wrap up between 7:30 PM and 8:00 PM.

Thanks to Datto for sponsoring our event!

Our guest speaker for the month is Surbhi Pokhama!

Topic: Principles of architecting a cloud data migration

Is your company planning to move your on-prem, hosted application to cloud? Have you been asked to assess your on-prem data workload and design the new castle in the cloud?
Designing the new castle is an important aspect but also this is more important to live happily in that castle once you migrate to the cloud. That’s where the art of architecting the operationalization aspect comes into play.

In this demo centric session, we will understand the fundamental building blocks of migrating on-prem SQL server workload to cloud via lift and shift or to Azure SQL/Managed Instance. We will build our hierarchy of needs checklist, a secured data migration plan and perform a sample migration to IaaS and PaaS Azure SQL databases keeping Data Security, Size, Performance, and Cost aspects in mind. By the end of this session, you will have a good idea on how to execute a secured and scalable cloud data migration solution.

We all get rejected. Don’t take it personally

You’ve been let go from your job. Or maybe you were passed over for the promotion. Or you applied to a position you very much wanted, and didn’t get so much as an acknowledgement of your application. Or you were turned down by the school or program that you had your heart set on attending. Or maybe your “great idea” got shot down. The list is nearly endless. Whatever the situation, or whatever the reason, we will all inevitably be rejected.

A couple of things made me think about this: a very recent situation where I was rejected for something (I won’t get into the details of it here), and the job hunt presentation that I just gave this past weekend at WE Local Hartford. In my presentation, I include a slide that talks about what to do when you’re rejected. I figured I should expand upon that. It occurred to me that, when it comes to professional development, we talk a lot about improving yourself and things to do to improve your chances. But we rarely talk about what happens when — not if — we get rejected.

Let’s face it. Getting rejected sucks. It’s a blow to your ego. You start thinking about what you did wrong. You start wondering if you’re really qualified to be doing what you’re doing. It’s often a major contributor, if not the root cause, of imposter syndrome. I can tell you that I’ve suffered my share of it, and it’s shaped my professional career in a number of ways. I would be lying to you if I said that I’m immune to rejection and it doesn’t get me down, because I’m not, and it does.

That said, when it comes to professional development, getting rejected is rarely personal. Now, I’m not going to lie and say that getting rejected for personal reasons doesn’t exist, because it does. But think of this: if you’re applying for a job or a school, what are the chances that someone making the decision knows who you are and is rejecting you because of a personal issue? I’d think that those odds are almost zero.

(It’s possible that maybe you were rejected because of some form of discrimination, such as racism, sexism, or ageism. However, this goes outside the scope of this article, and is another topic for another time.)

So how do you deal with rejection? I don’t know about the psychology behind dealing with rejection (that’s a conversation that goes beyond my education and expertise), but here’s what I think.

Remember that you are human. We are not machines. You are not expected to be perfect. You are going to make mistakes. In most cases, one or two slip-ups shouldn’t be enough to sink you. Don’t spend your time dwelling on what you did wrong. It’s often not worth the stress.

That said, make sure that you…

Fix whatever is broken. Each mistake we make is a learning experience. Find out what the mistake is and take steps to fix it so you’ll know better the next time it comes up.

So how do you find out what’s broken? For one thing…

Get feedback. It is perfectly okay to ask why you were rejected. Maybe you didn’t have the right skill set, or a skill was lacking. Maybe you didn’t communicate well. Whatever the reason, asking why you were rejected helps you to identify any issues that you need to fix.

It might also simply be that you just weren’t the right fit. I keep thinking of a scene at the beginning of Tootsie where Dustin Hoffman’s character was auditioning for a show. After arguing with the director as to why he should be picked, he was finally told, “we’re looking for somebody else, okay?” It takes two to tango, and not every match is a perfect fit, whether it’s different cultures, mindsets, skill sets, or whatever. Think of it this way: if it’s not the right fit, do you really want to be there, anyway?

Consider the competition. Maybe someone else has a better skill set, or is more experienced. Maybe there were 200 applicants for only one position, which means that 199 people were going to get rejected… and you just happened to be one of them. Only one person can be the best, so chances are that no matter how good you are, there will likely be someone who is better than you.

Always take the high road. Whatever you do, keep a positive mindset (yes, I realize that this is easier said than done). As I said earlier, it is okay to ask why you were rejected, and if you can get an honest answer, you can fix it and move on. You also don’t want to burn bridges; you never know whether or not you’ll need to deal with that person or company again. Even for jobs for which I’ve been rejected, I’ve asked if it was okay for me to connect with them on LinkedIn, and most of them have obliged.

Have a short memory. It’s human nature to dwell on what went wrong, so the ability to forget about it and move on can often be an asset. Even Mariano Rivera, the Hall of Fame relief pitcher who seemed nearly untouchable, gave up an occasional home run or walkoff hit. He often mentioned that one of his assets was to forget about it and move on to the next game.

Distract yourself. Something to get your mind off your experience might not be a bad thing. Forget about your issue for a while and go do something you enjoy. Go to a movie, work on your hobbies, play golf, hang out with friends, whatever it takes for you to get your mind off of it for a while.

Talk to someone. Don’t keep your emotions bottled up. Get it out of your system. Talk to a friend and say what’s on your mind. Not only will it feel good to unload your feelings, it’s also an opportunity to network.

When I gave my presentation in Hartford this past weekend, I asked if anyone had lost their job and was looking. One lady raised her hand. I didn’t get a chance to talk to her, but I did get a sense that she was frustrated by her situation. If she is reading this, I want to you know that it happens to the best of us. We’ve been there and done that. Don’t let the rejections define you.

Keep plowing through, and eventually, you’ll get accepted.

Greetings from #WELocalHartford #WELocal @SWETalk #SWELocal #WELocalHartford2023

I am writing this from a workstation area in the Connecticut Convention Center, location for the WE Local Hartford conference.

I arrived in Hartford around 6:30 pm last night, managing to arrive before a snowstorm hit several states in the Northeast (I wanted to make sure I left early as I could for exactly this reason). The conference takes places over two days, although I arrived too late to take part in any Friday activities. Friday night was uneventful; I checked into my hotel, got myself dinner, and retired to my room for the night.

Today (Saturday), for me, is pretty much where all the action has happened. After checking out of the hotel, I went to the convention center, registered, found my room, and went to the main ballroom to get myself breakfast, as well as the opening keynote. I’ll admit that I went primarily for the free breakfast! The keynote was given by Dr. Jenny Gusba, a senior director at Pepsico. She mentioned a couple of things that resonated with me. She talked about taking advantage of your strengths and addressing your weaknesses (or, as she called them, “opportunities”), and also mentioned how her challenge in her work was “how to take science and be able to get the masses to relate to it.” The former addresses things that are in one of my presentations, which the latter is a good description of what I do for a living.

My two presentations went well. Both were well-attended (there were at least twenty people in each), and I had a very receptive audience. A lot of questions and comments (which I encourage) were shared at both sessions. I assume that they solicit session evaluations for these presentations, but so far, the feedback I’ve gotten has been positive!

Pepsico, one of the sponsors for this event, sponsored a “networking lounge,” where I hung out in-between my two sessions. I did strike up a conversation with a young lady from Pepsico who said to me something to the effect of “thank you for supporting (women in engineering)!” That was a nice little acknowledgement of my participation at an event that is dominated by women.

Lunch was also an interesting event as well. They billed it as a “power networking” lunch. The rule was that you were not allowed to sit at a table where you knew more than half of the people. (To facilitate this, each ID badge had a sticker on the back that designated your “assigned” table.) I sat at a table along with four young ladies, all (as far as I knew) of whom were students. One was a student at NJIT, and two (who knew each other) were from Ohio State. (I didn’t get much info from the fourth, and she didn’t stay very long.) I found out that they were chemical engineering students. (As it turned out, I happen to know chemical engineers from each of their geographic regions. Hey, more reason to network!) We had a wonderful conversation; I gave them my business card and told them to drop me a line if I could be of assistance.

I thought the networking lunch was a great idea! In my networking presentation (which, unfortunately, I didn’t do today), my attendees get an opportunity to network. When we do so, I tell them that I have one rule: you are not allowed to engage someone you know. You can’t; that defeats the entire purposes of developing networking contacts. Networking is such a huge deal in career development these days; I do have an entire presentation dedicated to it, after all, and I’ve been attending more events where they put an emphasis on networking (including this past PASS Summit). I hope more events schedule activities that facilitate and encourage networking!

I should also mention that this is the second time I have spoken at a WE Local conference (the first was in Buffalo last year), and for me, it’s a bit of an interesting experience. I’ve been speaking at various events (mostly SQL Saturdays) since 2015, but Buffalo last year was the first time that I spoke at an event where the attendees were predominantly female. STEM professions tend to be predominantly male, so there have been efforts by groups such as SWE and WIT to get more girls and women interested in pursuing STEM careers. That comment I got today in the networking lounge meant a lot to me, and I like to think I’m doing my part to contribute.

As I write this, there’s still a couple of hours left in this event. I’m going to see how the rest of the day winds up, maybe do something for dinner, then make the two-hour drive back home. Looks like the weather has cleared, the roads are clear, and I think it should be smooth sailing back home.

Speaking this Saturday at #WELocalHartford #WELocal @SWETalk #SWELocal #WELocalHartford2023

This Saturday, March 4, I will be speaking in Hartford, CT, at the WE Local conference, presented by the Society of Women Engineers! This will be my second time speaking at this event; last year, I spoke at their conference in Buffalo.

I will be doing two presentations.

At 9:30 am in room 24, I will be doing my presentation about surviving an unemployment situation, titled: “I lost my job! Now what?!?” I will discuss topics such as how to deal with your emotions, how to improve your job prospects, and how to pass the time while you’re out of work.

At 11:45 am, also in room 24, I will do my technical writing presentation titled: “Tech Writing for Techies: A Primer.” Technical writing is likely the most misunderstood and ignored technical functions. This presentation is intended to clear up many of the misconceptions behind technical writing, explain why it’s important for your organization, and ways to improve the process.

To view the agenda for this event, click here! Hope to see you in Hartford on Saturday!

February Monthly CASSUG Meeting

Greetings, data enthusiasts!

Our February meeting is scheduled for Monday, February 13, at 5:30 pm!

This will be a hybrid meeting!

  • For those joining us in person, we will meet in person at Datto, 33 Tech Valley Drive, East Greenbush, NY.
  • For those joining us online, use the Zoom link to join the meeting. We will send out the passcode as we get closer to the date. You MUST RSVP for the Zoom link to be visible!

For more information and to RSVP, go to our Meetup event page at https://www.meetup.com/capital-area-sql-server-user-group/events/290678755/

Our meeting schedule is usually as follows:

  • 5:30 PM: Food, soft drinks, and networking
  • 6:15 PM: Chapter news and announcements
  • 6:30 PM: Presentation

We usually wrap up between 7:30 PM and 8:00 PM.

Thanks to Datto for sponsoring our event!

Our guest speaker for the month is John Morehouse!

Topic: Accelerated Database Recovery – A Deep Dive Behind the Magic
Hocus Pocus!

We have all heard the stories. Horror story after horror story being regaled from database administrators all over the world of waiting for hours or sometimes days for a rollback operation to complete. DBA’s hoping beyond hope that the rollback finishes soon before someone else gets the notion to reboot the server.

With the release of SQL Server 2019, a new talisman was conjured that will save us all from hearing about future horror stories. Accelerated Database Recovery or also known as “ADR”. This new mystical feature changes the way transaction rollback performs and will undoubtedly prove invaluable in your arsenals of magical tricks!

In this session, we’ll show you the secret behind it!

You will –

  • Learn about new components of the transaction log
  • Discover the magic behind ADR
  • Determine when you wouldn’t want to implement it

Don’t be the protagonist in a rollback horror story! After all, the time you save might be your own!

Speakers Are Normal People

This is a great post by Steve Jones. I have made a lot of great friends through my association with SQL Saturday and PASS. I can tell you firsthand that #SQLFamily is real!

Voice of the DBA

The #SQLFamily is amazing, at least I think it is. Like many families, it’s welcoming, supportive, and comforting. It’s also maddening, frustrating, and exacerbating at times. Like most families, or at least the ones I know, it’s not perfect, but it’s what we have and at the end of the day, most of us get along with each other.

It’s also an open group of people. In general, we welcome people with open arms and smiles. Those of us that are more visible or prominent are willing to listen to, help, and support anyone. I was overjoyed during the recent PASS Data Community Summit, where I had the chance to see so many people that I haven’t seen in person in 2-3 years. I met many other interesting people for the first time and enjoyed the experience.

Not everyone feels the same way. I loved seeing Kimberly Tripp and Paul…

View original post 630 more words

Support your local public library

I remember when I was a kid, Tuesday was my favorite day of the week. That was because that was library day. One of my parents would take me and my siblings to the local public library where we would check out books and magazines, take them home to read, and bring them back next week to do it over again. Back in those days, you were only allowed to keep books for a week (unless, of course, you renewed them).

Now that I’m much older, I still enjoy going to the library, although I don’t go as much as I used to (usually, time commitments keep me from going as much as I’d like). Nevertheless, I have a library card, and I enjoy going whenever I have the chance.

I was thinking about this earlier this evening while I was researching meeting venues. There are plenty of them that charge an arm and a leg, but why do that if a local library has meeting facilities? (I was also considering firehouses — which usually has meeting space — as well, but that’s another post for another time.)

The library is a great place. Not only can you check out books, you can also check out music, do some research (this was especially true in the days before the internet), attend talks and other events, and maybe even meet people. It’s a great public resource, and it’s free (assuming you don’t have to pay any overdue fees)! If a person doesn’t have access to a computer or the internet, (s)he can usually book computer time at a library.

I really think the public library is an underutilized resource these days, especially with the advent of electronic and online resources. Even when I’m giving my presentations, one resource that I nearly always cite is to “go check out your local library.” It’s a neat place to hang out, and there’s always something to be said about wandering around stacks of books. Even in this day and age of the internet and online resources, your local public library is still relevant.

New old presentations

As I mentioned earlier, I have a few speaking gigs coming up, including one in Hartford, CT in March. I’m actually doing two presentations for Hartford: my job hunt presentation (which seems to be one of my best sellers; I’ve done this presentation several times, and I will also be doing it for STC Summit), and my presentation on technical writing. So, I downloaded the WE Local PowerPoint templates from their speaker’s resource page so that I could apply them to my presentations.

I haven’t yet applied it to my job search presentation. To be honest, I’m not terribly worried about it. It’s mainly a matter of transferring my material to the new template, so it shouldn’t be a big deal.

The tech writing one, however, was another story. When I looked at my slides, I realized just how much it needed to be overhauled. It wasn’t very well organized, it was out of date, and I’ve grown considerably in my profession since I last gave that presentation (the last time I presented it was in New York in 2019). The presentation badly needed to be rewritten. So I spent my entire afternoon this past Sunday putting it into the WE Local template.

When I was finished, what I had was practically (though not exactly) a brand-new presentation. It is better organized, more clear, and I included points that I did not address before I restructured it. I think the new (old?) presentation is much better than it was. Not only am I looking forward to giving it in a couple of months, I’m also looking forward to submitting it to more events.

Likewise, I also plan to revamp my presentation about — well — presenting. I’ve only given this presentation once, and quite frankly, not only is it not very good, it’s also narrowly focused, and like my old tech writing presentation, it’s also not very well organized. Although I haven’t started yet, I essentially plan to pull a This Old House on it, completely tearing it down, and rebuilding it. I already have an idea in the back of my head as to how I’m going to do it, and I’ve already rebranded it (in fact, I even submitted it to SQL Saturday NYC in May).

I’ve been trying to come up with new presentation ideas. I’ve mentioned to people that I’ve reached the point where I’m starting to recycle submissions to PASS Summit and other conferences. I might still work on some new ones (stay tuned). But in the meantime, it’s worth my time to take some of my older presentations and give them new life.

The zen of the New Year

Why do we celebrate the New Year? All it is, after all, is a turn of a calendar, when December rolls into January. January 1 isn’t much different than December 31. So what’s the big deal?

As I write this, it’s January 3, three days into 2023. I’m glad 2022 is behind me, as it was a very trying year (as I mentioned earlier), and I’m looking forward to what 2023 has in store. I already have two speaking engagements lined up, and I’m sure I’ll have more fairly soon. I’m getting ready to go back to work (even as I write this, I’m getting ready to head into the office), and I feel like it’s a fresh start.

That’s what it’s all about. Any issues you dealt with in the past year is now in the rearview mirror, and you’re starting with a fresh slate, sure as you go to bed at night and wake up refreshed the next day. A new year might not, on reflection, seem like a “new year,” but at the same time, it’s a reawakening from a busy period of time.

So as most of us return to work on this third day of 2023, let’s make it better than last year!