Aaron is offering a choice.
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”.
What are you going to automate today?
It is no surprise to those that know me that I will choose PowerShell as the topic for this month. I am passionate about PowerShell because it has enabled me to have the career I have today and to visit numerous countries all around the world, meet people and talk about PowerShell. By my reckoning searching the TSQL Tuesday website it has been over 3 years since we had a topic specific to PowerShell. So I would like you to blog about PowerShell and SQL Server (or other interesting data platform products)
If you don’t know or use PowerShell GREAT! That’s awesome.
Please spend an hour or so with it and tell us how you got on and what and how you learned. Just like Erik and Brent did. You could install one of the community modules like dbatools, dbareports , SQLDiagAPI or the Microsoft ones sqlserver or SSRS and try them out and tell us what you learned.
- Write a post on the topic below
- Schedule the post to go live on Tuesday, September 12th (between zero am and midnight, UTC)
- Include the TSQL Tuesday logo in the top of your post
- Link the post back to this one (it’s easier if you comment on this post and link it)
- Optional: Tweet a link to your post using the #tsql2sday hash tag on Twitter
For this month, I want you peers to write about those important lessons that you learned the hard way, for instance something you did and put your systems down or maybe something you didn’t do and took your systems down. It can be also a bad decision you or someone else took back in the day and you’re still paying for it…
There are so many things to share here so everybody can learn from each others mistakes, because all of us were once a beginner and no one is born with any knowledge about SQL Server.
Please do not be ashamed of sharing your experiences, you can anonymize the whole story if you want but remember all people make mistakes, the important is to learn from them and try not to repeat them in the future.
This months topic is inspired by the blog post Will the Cloud Eat My DBA Job? by Kendra Little. Technology has changed a lot in the past years, especially with cloud/globalization/automation. What an impact has this had on your job? Do you feel endangered? Or do you have more exciting features/toys to work with? Do you embrace the change and learn new skills? Or do you hide in your cubicle and fear the robot uprising? Let us know how you handle all these changes, or how you feel there are no changes at all for your current job. I’m looking forward to learn how you feel about the future of data management/analysis and how you plan to deal with it.
So, let’s get this blog party started, and kick off our international Healthy SQL campaign. Let’s spread the word to anyone and everyone managing a SQL Server Database infrastructure of the necessity to perform regular health checks on each SQL Server and repeat often. The purpose here is to get database professionals, to ensure that all their SQL Servers are healthy, and can pass a health check. It also means that you can prove this (to heaven forbid, auditors), and back it up with documentation.
If you want to excel in your career as a data professional or DBA, then you need to be concerned about your companies’ SQLFitness. Therefore, I am inviting all of you, to blog about your T-SQL Resolution, and describe what it is that you will do this year to make sure your SQL Servers are healthy and fit. Now, it’s ok to ponder Healthy SQL in the abstract, but we’re looking for some technical tips on things a DBA should do to keep your SQL Servers performing well.
It could be something as simple as implementing a new monitoring software or script, updating all your SQL Servers to the latest version or service pack, setting up maintenance and optimization jobs, HA/DR, creating a performance baseline, capturing performance stats, (ie: DMV automation scripts, or MDW), a checklist ,etc. Sky is the limit, as long as you can contribute something to the SQLCommunity that can be used in the effort to ensure SQL Fitness.
In “The Spirit of Giving”, I want to know how you plan on Giving Back to the SQL Community during the coming year. Are you going to start speaking at your local user group? Speak at your local SQL Saturday? Perhaps step up and help run your local user group? Do you want to start becoming an active blogger – or increase your blogging? Do you plan on volunteering your time with larger organizations (such as PASS), so that SQL Training can occur at a larger level? However you plan on giving back to the SQL Community during the upcoming year, and whether it is something new that you’ll be doing or continuing what you are doing, I’m looking forward to reading about it in your blog post.
So, here it is. I put the challenge out to discuss something new learned last week. I was fortunate enough to attend the PASS Summit last week in Seattle. While this post will not be my summarization of that trip (that will be another post) I did have several take-a-ways. I sat in some stellar sessions with some renowned speakers.
However, one re-occurring theme kept coming to my mind – the people. Listen, I’ve been through a lot over my 15 years with SQL, and my 3 years actively involved in the community and this past week affirmed something for me. LISTEN to the people.
I place strong value in the sessions I attended; along with that I have to note that face time; one on one time with real people in my industry is about the best form of learning I could ever hope to obtain.
With that learning comes in issues related to both SQL and non SQL attributes. I had so many positive conversations on leadership alone that sparked a new kind of fire within me; one that was not as bright as what my technical fire had been.
Guys, listen. I could write 10 blog posts on how buffer size could help with backups, the need to have always on implemented, or how to tune indexes all day long. The people, better yet the community is where I believe the learning lies within. Out of 5k people last week I ended up meeting a guy that works two blocks from me and we got to discuss the community and what it means to us.
Have you challenged yourself lately? I mean have you really challenged yourself lately in learning something. I don’t care if you are just starting out or the most seasoned vet around; the ability to learn happens everyday and I’m learning that is what separates the exceptional data professional from the data professional.
You see, the exceptional data professional hangs around the community zone at Pass Summit to help others in the community with issue they may have. The exceptional data professional sits down next to you when you are the new kid on the block and encourages you to make the most of your career then tells you some of his/her pitfalls they had that you can avoid, and the exceptional data professional takes you under his/her wing when you ask them for help or assistance.
You don’t have to travel all the way to Seattle to learn; no you have learning opportunities all around you. From SQL Saturday’s to Virtual Chapters on the web but it starts with you. That’s right, you have to be willing to take that first step; get involved and start learning.
I can tell you from experience and the roller coaster ride I’ve been on for the past three years that you will not regret it. Strive for excellence and provide that leadership through service that the community seeks. Yeah, I may be a tad passionate about what I do; you’ll find that kind of trait with others in the community.
So, I’ve challenged myself……..will you?
Invitation, no roundup.
It turns out that Tuesday, October 14th, the day your contributions are due, is also Ada Lovelace Day. As you probably know, Ada Lovelace was one of the first female computer programmers (considered by many to be the FIRST computer programmer). If you didn’t know that, here’s your chance to learn some history of our industry. Wendy suggested that we take advantage of this date and do some sort of a tribute to Ada. I agreed, and here we are.
Ada Lovelace has been an inspiration to many. In keeping with my blog theme, let’s call her a hero. We all have our heroes, those people who we admire, who inspire us, who we strive to be like. Who is your hero?
Your assignment is to acknowledge, in writing, your hero (or heroes). You don’t have to mention them by name if you’re not comfortable doing so, but you do have to tell us how you met them, how they have inspired you, and what qualities or traits of theirs you have striven to adopt.