Invitation and roundup from Kevin Kline.

My invitation is about the social side of life as an data professional, specifically conferences and events. As one of the original nine founders of PASS and an early president of the association from 2004-2010, I always looked forward to the fall and the yearly PASS Summit. The leadership of PASS always worked hard to make the event feel like not only the best SQL Server and Azure SQL training event, but also like a big family reunion. (Check out the #sqlfamily hashtag on social media. It’s a thing!) Many bloggers have already written about #sqlfamily goodness from their attendance at the PASS Summit. Maybe we will see a couple of those blogs reposted?

With the last couple years pandemic lockdown behind us, we might not have many recent examples from the past two years. On the other hand, we have so much to look forward to with anticipation this fall! For many of us in this industry, conferences and events are the highpoint of our yearly business cycles. And with good reason, because we attended an event that had a lifelong positive impact on us. The invitation –

Tell us the story of how attending an IT conference or event resulted in an amazing career or life opportunity.

Of course, job and career opportunities readily jump to front of mind. But I ask you not to limit yourself to stories solely focused on career opportunities or job changes. I’ve seen so many other great outcomes happen for people who attended events like the PASS Summit, SQLBits, and others. I’ve even seen people meet, fall in love, and begin their journey as a couple because they both attended the same event. How wonderful is that?!?

Here are some other ideas. Did you connect with a new group of friends who are now a constant part of your life? Maybe you found a mentor who helped you in a multitude of ways? Perhaps you attended an event that started as the launch point of your own personal advancement as a speaker, blogger, writer, mentor, or community leader? Or maybe you learned an entirely new set of skills that amplified your success at your current job? It could be something even simpler, like finding out about a new musical act, writer, or artist who now is your favorite! Whatever your story might be, I would love to read your blog post about the conference that changed everything for you.

I hope I have inspired you to participate. Your action might then inspire others, starting a virtuous cycle of continued improvement for our community. Now, read the blog party rules below and get started!

Invitation from Kenneth Fisher.

This month for TSQL Tuesday I’d like to hear about your first technical job(s). I know most DBAs don’t start out working with databases so tell us how you did start. I’m generally thinking of your first tech job, but if you had a job early in your career that wasn’t technical at all but still makes for a good story feel free to share! I can’t wait to hear about it.

Invitation and write-up from Alex Yates.

Bringing people together

I’m excited about DevOps. I first heard the term as a sales person at an IT company. I recognised the gulf between the sales and tech silos at my company and I could observe conflicts with many of my customers between developers and DBAs. I had a lightbulb moment when I realised the potential – if you could just get all these different people and teams to work together effectively with a shared vision.

I’m also increasingly aware that we aren’t just conflicted in our work lives. I live in the UK and my society is increasingly polarised. I know the same is true in lots of other places. Our community tends to communicate through social media, most commonly on Twitter, where we create echo chambres for ourselves as we follow people who share our views and we consciously or unconsciously unfollow or block anyone who disagrees with us. Even if we try to avoid it, the algorithms tend to show us the content we like to read anyway.

It seems to me that at work, online, and in society at large we are becoming more stubborn and less open to exploring ideas that challenge us. It’s my belief that if we were all (myself included) more open, not just to talking, but to genuinely challenging our existing ideas, we would all benefit. I believe that’s true both in our professional and our personal lives.

The challenge

I would like you to write about something in your IT career that you have changed your mind about. What was your original opinion? Why did you believe that? What do you believe now? Why did you change your mind?

You are welcome to discuss technical or non-technical topics. Feel free to go as deeply technical or as personal and human as you like. Brain-melting technical posts about the inner workings of the SQL engine or effective machine learning architectures in Azure are great. SQL 101 posts or perspectives on age old debates such as tabs and spaces or where to put your commas are great too. Human posts about effective teamwork or diversity or wellbeing in tech are also great.

I hope that if we think hard about the ways we have changed our minds in the past, and if we read about how and why other people have changed their mands, it will help us to have better conversations in the future. I hope this will help us to work together more effectively at work – and maybe in other parts of our lives as well.

Invitation and roundup from Mohammad Darab.

Yesterday was my 41st birthday. Twenty years ago, I remember my best friend asking me, “Where do you see yourself when you’re 40?” My reply was something like, “I can’t see myself as a 40 year old.” For some weird reason my mind went blank at 40. It wasn’t like I thought I’d be dead by 40, but I remember thinking of 30 or 35, but not 40. Maybe because 40 was twice my age and just too “far into the future” to think about?! But in a “blink of an eye” here I am twenty-one years later. Funny enough, now I can see myself as an 80 year old. Weird.

Time sure does fly by.

Introspection

This past weekend I presented at SQL Saturday Dallas. Unfortunately, I had lost my voice when I landed Thursday afternoon. I did all I could to get it back by Saturday morning by drinking lots of liquid and getting rest. I got enough of my voice back to do my session (which was first thing in the morning) but had to leave shortly after for some much needed rest. I spent the rest of Saturday in bed and some of Sunday before I had to head to the airport. To top it off, I had 5 flight delays and ended up spending 7 hours at Dallas airport.

During those long hours at the airport, I had some time to introspect. I went over my session. I noticed how over the past couple SQL Saturdays I’ve spoken at, the younger attendees approach me asking questions at the end. The elder attendees mainly say, “thanks!” and the young attendees stick around and ask questions. I absolutely admire and respect that. A lot their questions are very easy to answer. But it’s easy *now* since I have more years of experience.

That brings me to this month’s T-SQL Tuesday idea…

This is my invitation to you this T-SQL Tuesday: Write your 20 year old self a letter. If you could go back in time and give yourself advice, what would it be?

Here are a few potential ideas:

• Things you would have done differently
• Any words of encouragement
• A “Do” and “Don’t Do” list

Obviously we cannot go back in time and live all over again. However, we can write down our advice so that way we have it ready for the next young aspiring technical professional (or any profession for that matter) who comes seeking advice.

As the saying goes, “learn from your mistakes.” I say, it would be even better to “learn from the mistakes of others so you don’t even have to make them.”

Remember to have fun during this process. I can’t wait to share my letter next week!

Invitation and roundup from Andy Leonard.

What is Your “Why?”

I enjoy math. I noticed a pattern learning math, perhaps you experienced something similar. I found arithmetic an exercise in memory. I have a good memory (well, I had a good memory…) so memorizing a bunch of rules was no big deal. 

When I learned algebra, arithmetic made more sense. In addition to the memorized rules, I saw why the rules existed. I understood the rules better as a result.

This pattern held all through my math education. I understand algebra better once I learned geometry. I understood geometry better once I learned trigonometry. I understood trigonometry better once I learned single-variable calculus.

An Axiom (for me)

I notice a similar pattern applies to my career (or careers, as the case may be). I’ve served in many roles: 

• Farm laborer
• Musician
• Stockyard laborer
• Truck driver
• Service technician
• Soldier (part-time in the Virginia Army National Guard)
• Electrician
• Electrical engineer
• Electronics technician
• Manufacturing automation integrator
• Software developer
• Author
• Data professional
• Entrepreneur

The similar pattern manifests itself in this manner: I’ve enjoyed the position – and more success in the position – when I had a reason to do the work; some reason other than a paycheck. In some cases, I had multiple “why’s” beyond remuneration. For example, I join the Virginia Army National Guard to learn electronics and serve my country – to especially protect everyone’s right to free speech guaranteed by the First Amendment. I may not agree with what people say, but I was (and still am) willing to fight and die to preserve the right of US citizens to say whatever they want. 

As a result, I enjoyed serving in the National Guard (for the most part). I learned more. I learned better, I think, because I enjoyed serving.

Entrepreneurship

Entrepreneurship can be challenging. I believe one needs a “why” – or perhaps several “why’s” to remain an entrepreneur. The “why” cannot simply be money. Money isn’t inconsequential, mind you, but I believe the best “why’s” are less tangible.

Passion plays a major role for me. When business isn’t going well or when business is going too well, a couple intangible “why’s” – passions for both entrepreneurship and the kind of work I am blessed to do – inspire me to keep a steady hand on the tiller.

What is Your “Why?”

That’s the question this month: Why do you do what you do?

I look forward to your replies.

Invitation and recap from Jason Brimhall.

T-SQL Tuesday 109: Influence Somebody Invite

In November 2017, Ewald Cress (b | t) invited everybody to talk about and basically give thanks to people that have helped impact their careers or lives. Check out the roundup here.

In December 2017, Mala Mahadevan (b | t) invited everybody to set goals for themselves. These goals were supposed to be about learning. But when you get down to the nitty gritty, anything that helps build character and career really comes from something that must be learned. It all starts with a bit of introspection. It is this introspection that I ask you to use as a building block for the party this month.

Lastly, in May 2018, Riley Major (b | t) asked everybody to reflect a bit on the theme from Ewald. This time though, the task was to give back to the community. Pay it forward, if you will, given that you had previously benefited from the kindness of somebody else.

Invitation

Building on the work of these three fine individuals, here comes the difficult task. You have been the benefactor of some awesome help from somebody else. You even wrote about it and in a way, told that person how they impacted you, your career, or both. You have set goals for yourself to become a better you after some personal reflection, meditation, introspection. Then you have given back to the community in some way.

I am not asking you to be braggy, just aware and cognizant. What have you done to impact somebody else in the last 13 months?

How do you know you have impacted them? This is really the hard question. I want stories of how you impacted somebody else for the better. This may mean you will need to talk to some people and have a little retrospective with them.

Why?

This past year we lost some real juggernauts in the SQL Community such as Robert Davis (blog). We all know he impacted many people. We can also assume that he knew he impacted peoples lives. How great would it have been to sit down and have a personal discussion with him to let him know for certain how he impacted your career?

At PASS Summit, I had the opportunity to have such a discussion with somebody completely out of the blue. I know how much that meant to me. I also know that I was rather unaware of the influence I had on this individual.

How?

If you have not already had the opportunity to discuss your influence, make the opportunity. If you have mentored somebody, have a chat with them. If you work with somebody that you might have influenced, have a candid chat. Ask them directly if you have been able to be a good influence to them. Ask them how you might be able to better help them.

I know, this gets us all out of our comfort zones – but we need to do things like this. It is a method of both giving thanks as well as just giving (it is the season).

If you are reading this and don’t feel you have influenced somebody, then talk to somebody that has influenced you. Let them know how you influenced them.

Then, after having this candid chat, please write about both the experience (even the awkwardness), anything you learned from the conversation, as well as some details around what it is you did that impacted said individual.

Doing this little exercise will not only help you to become a more involved team member, community member, and leader it will also help you improve on some of the interpersonal skills used for networking as well as public speaking.

Invitation and wrap up from Riley Major.

Giving Back

A few months ago Ewald Cress asked you to share stories about people who have made a difference in your professional life. Dozens of you wrote about who impressed you, inspired you, taught you, helped you, and guided you. It’s a testament to the Microsoft data community that so many were recognized by so many– that we have those willing to give of their time and those who are publicly appreciative of it.

Now I will give you an opportunity to give back. Everyone reading this has benefitted from their fellow data professionals. And that benefit puts you in a position to share alike. You’ve learned something, so you can teach. You’ve been supported, so you can help. You’ve been led, so you can lead. But you don’t have to do it alone. We’re all going to do it together.

So here is my call. Pick some way you can help our community. (Ideally, this would be our technical community, but if you’re passionate about some other type of service, that works too.) Then, make a plan– a real plan, with specific steps and dates. Just like Mala Mahadevan asked you to do with your learning goals for this year. Then, and this is the important part, you’re going to write it down for the world to see.

Back when I was still toying with the idea of speaking, it was specific persuasion and public accountability which gave me the push to make it happen. So now I’m giving that to you. I am specifically asking you, dear reader, to make and publish this plan, and I’m going to help make it a reality by gently holding you accountable. You will set your own goals and I will check-in to see how things are going. I will offer what encouragement I can. And I will celebrate your accomplishments.

And if you think there is nothing you can contribute to this community, I am excited to tell you that you are wrong! Some ideas:

• Join Twitter and post links to articles and blog posts you find interesting. Make yourself available for questions. Monitor #SQLHelp and contribute when you can. Signal boost those looking for work.
• Meet people at industry events and see if anyone you know could help them with a problem.
• Volunteer at a SQLSaturday or other conference.
• Write a recommendation for a colleague on LinkedIn.
• Go to user group meetups and conferences and tell everyone you meet about PASS.
• Answer questions on DBA Stack Exchange.
• Convince your boss to send you to PASS Summit. (That revenue helps fund our ecosystem.)
• Write an instructional blog post.
• Host a “lunch and learn” at work.
• Make an instructional video or screencast.
• Speak at your local user group or SQLSaturday. (You can start with a 10 minute lightning talk.)
• Convince your boss to sponsor your local user group or SQLSaturday.
• Nominate someone to be a Microsoft MVP.
• Take your magic beans scripts and make them public utilities like sp_Blitz, sp_whoisactive, and Ola Hallengren’s index maintenance solution.
• Contribute to existing open source tools like dbatools.
• Work at improving diversity in tech.
• Join the board of a user group or start your own.
• Guide others through a process like Brent Ozar did for Summit submissions.
• Encourage others to begin speaking, like Andy Yun did with T-SQL Tuesday #84.
• Host a T-SQL Tuesday.
• Become a mentor.

Pick something. Tell us why. Tell us how. Tell us when.

We’ll ask “are we there yet?” and give you a high five when we are.

Now to be fair, many #tsql2sday contributors already pour boundless energy into the community. And some might simply not be willing to step up publicly. So for those who still want to party, I submit the alternative topic of your favorite improvement in SQL Server 2017. (If none of the new features excite you, tell us how you successfully used something new from 2016.)

Update 2018-05-02: For those who routinely give back to our community, thank you again for all of your service. I’m not asking you to give any more. A better angle for you on this topic would be to tell us how and why and you started. How did you discover the community’s need? How did you figure out what your role would be in helping? How did you learn the skills you needed to contribute? Where did you find the confidence to take the leap? How would you recommend others proceed? Thanks again and hopefully this provides a better avenue for you to participate this month.

The current invitation (January 2017) is for T-SQL Tuesday #98. Invitation and round up from Arun Sirpal.

Please write about and share with the world a time when you faced a technical challenge that you overcame and you can go really technical with both the issue and solution if you like.

From data recovery, tempdb contention, concurrency issues to even DTU exhaustion within Azure SQL Database – there is plenty to potentially write about.

So tell us what the issue was, your troubleshooting mind-set, how knowledge in that specific area guided you and more importantly what you did to overcome this challenging event. Hopefully with this topic we will get to read from both advanced and beginner level bloggers.

You know the saying, “When the going gets tough, the tough get going”.