I’m a little late getting this together, but that’s not entirely my fault.
For this month’s T-SQL Tuesday, I wanted to once again talk about Aging! But not in the human sense. I mean in the code sense. It’s a simple question that can be interpreted in many ways, and I look forward to all the ways you might see this.
The question is. “How has your code aged?”
Pick a project or code script and decide if it “aged well”. Is it still in use? Is it functioning? Did it do what was needed, and now it’s no longer around? Perhaps talk about how useful it was for the time, but now it would never be needed because of AI or other aspects.
Knowing what we have done in the past and how we have improved is very important to moving forward. It’s also a great time to be grateful for something you created in the past, and perhaps it is still working. Very often in this fast-paced world, we spend all of our time looking at the new project and the next big thing, and we forget to enjoy the things that created the foundation for our future.
I hope you will join this exercise by posting on February 10th, 2026. Please make sure to link to this original post and include the T-SQL Logo on the post. I’ll write up the summary after Tuesday, and we have all the posts listed.
I attended a different event this weekend. It wasn’t specifically a technical event, and it wasn’t specifically NOT a technical event. It was about something we are all facing in the future.
Aging.
That’s right, whether we like it or not,t we are all getting older. For me personally, ly it’s something I’ve been thinking about a lot lately. I’ve always thought about and focused on the future. I believe in two major concepts in my life.
Visit your Default Future.
I’ve presented on this before. This idea comes from a book called Change Anything: The New Science of Personal Success(Amazon Audible link). I highly recommend this book; I typically re-read it every few years. Default future means that you can meet/see someone who will be your future if you change nothing else right now. Perhaps you are in the same roles as a family member, perhaps you do similar things to that family member. You can quickly see what you will become in 5-10 years by observing this person like you. If you don’t like what you see in your future, you need to change it. The book outlines steps to do so.
Chapters.
I see my life as a series of chapters. As we go through life, we experience big events and moments. I don’t believe anyone has just one path that they stay on for the entirety of their life. I believe it changes, and when you leave a path or change it, you open a new chapter. I believe I am in Chapter 3 of my life right now, and I have no idea how many more chapters there will be.
During the event, we heard from many participants of diverse ages and backgrounds. The items below are my key takeaways.
Keep talking to each other! Making connections, having friends, and even just having discussions are statistically proven to prolong life. I wrote about connections recently, and that post confirmed it even more.
We have a serious problem with our Senior population right now. Scammers are targeting them. We need to help educate and support them in these times. Legislation is also a good idea to help address this problem. I will personally volunteer for more events to get involved.
90% of Seniors are now connected to the internet and using applications, just like the rest of us. But the tech industry is not building for this Demographic. They are not developing applications for older adults. We need to start considering this when designing applications and building solutions.
AI can greatly help the aging population, but it is not designed for seniors to use. We can’t just provide the same tools everyone else has; we need to customize them and make this better. Several people at the event were working on solutions around this.
Your identity should not be related to your work. Many of us in this industry devote so much of our time and lives to our jobs that they become our identity. I plan to write a blog post soon about how to separate these items. Think about this now, though,h as it becomes a big part of your life moving forward.
Some of the simplest things you can do to improve your life are to show Gratitude to yourself, others, and to play! That’s right, enjoy some of life and make sure you have time for play.
I have a lot more to share on these topics and events, but this is enough to get the discussion started. Please take a minute to start thinking of these things now. Time is always moving, and it moves very quickly.
You can find all the key rules and information on hosting if you would like to host at this link. https://tsqltuesday.com/
The Request.
I haven’t participated in a #TSQL Tuesday in quite some time. I saw this topic and said, “That’s perfect!” I love talking about Failure and mistakes! I have a whole presentation about it, and I’m hoping to make a series of blog posts about it very soon.
You do not learn from success in life; you learn from failure. I hope you are making lots of mistakes so that you can learn!
“This month, I am asking you to share about a mistake you made that touches on data in some way. Whatever the mistake was, maybe when you were a complete newbie, maybe just last week.”
I have lots to choose from, but I have been very nostalgic as of late, so I’ll go to one of my very first mistakes as a DBA.
Some of you won’t even be able to go back this far in technology, but some of you will appreciate this. It was Mid 1999. I was just learning about Databases and had only recently inherited a Sybase SQL Anywhere DB. I had no formal training in SQL and just a general understanding of what the Database was and what it did. I was a customer support manager and needed to figure out this new DB that we were using. It quickly became evident that I preferred working on the DB items to the manager items. My passion at the time was the technical side of things.
It started with a simple request: The DB had a front-end called HEAT (later Goldmine CRM). This system allowed the creation of simple forms and the entry of data about support tickets and customers. We needed a backend process that would update the phone number whenever another field was updated. I had just read something about Triggers… yeah, some of you know where this is going.
So I wrote up a Trigger that updates the phone number field whenever another field is updated. Pretty simple…..Unfortunately, the trigger updated every phone number in the table every time an agent updated a field in the system. I didn’t understand that each update was row-level, but the query was acting on the whole table, and I didn’t specify that it should only update the record that was changed. As people started using the system, it would wait about a minute each time to update all the other records. Luckily, the data was still correct since it was just updating the same row, but it was using all the system resources. Since this was the late 90’s, we didn’t have high-powered servers. The DB didn’t stand a chance of staying up and running correctly. It took most of the afternoon for us to bring the server down, start it back up, and remove the trigger. We weren’t sure what the issue was at first, but then I remembered the change I made.
Luckily, it was a small company, and they were pretty used to the system going down throughout the day. Uptime wasn’t as big a thing back then as it is now. I learned some great lessons on this day, and they have continued to shape me as a DBA.
Lessons Learned
Test everything! I did not have a testing environment for this system.
Respect all Triggers. I’ve seen tons of triggers since this first issue, and I’ve questioned every one of them to understand whether they are fully needed and how they are used. They are very powerful and very dangerous.
Enjoy the early days and the small companies. Suppose you find yourself in a DBA position in a small company and are just learning new things. Enjoy that time! Use that time to really learn about some of these things that can go wrong. I learned a ton of important lessons at this company.
Ask questions and seek out others. I was the lone DBA at the time and had no one else to bounce ideas off. I didn’t find community till years later, and I’m sure it would have helped if I had a community back then.
Sql Insane Asylum (A Blog by Pat Wright) 
