Becoming a Better DBA

One of the things that I try to advocate for is that more of you actively manage your careers and find ways to improve your skills. I want you to be more impressive and find an amazing job for you. Not my job, because I have the best job in the world, but I hope you find a job that you love as much as I love mine.

It does take effort, work, and focus. It’s something else to manage in life. I certainly don’t want you to only care about work. After all, we work to live, not live to work.

That being said, I think you can build the habit of regular career improvement. For those of you that work as DBAs, I found this list of things that help improve your productivity. The first few items are practical having a routine of things to check and a way to monitor your systems. Those are core skills and a base from which to build. I might stress backups, restores and DR as well, since the main thing is that you can protect and recover data if everything else falls apart.

However, the last few items are less tangible. How do you keep up, explore, and try things? In what area or topic should you start? What’s important? I find many people struggle with these less directed pieces of advice. If I want to keep up, what do I do? If I want to experiment or ask about something, what is the most efficient way to do this?

There’s advice in the article, but here’s my main thought. Don’t try to be efficient or perfect. Just pick the thing that’s in front of you. Pick something that someone asked you about and you didn’t know. Or maybe the thing that looked interesting? Just move forward.

Most of the work we do to improve ourselves isn’t tightly focused at first. It’s just a step forward and it’s not a permanent step. If you decide to start learning about something such as Availability Groups and then realize you don’t like this area or it isn’t important, just switch to something else. Your time isn’t wasted because even if you don’t use that skill, you learned about learning something. And you learned something about yourself and what you enjoy. Move on and try something else.

For me, I started SQL Server Central. but I liked newsletters similar to the one I send out each week because they gave me something to learn about. I used to troll forums at various places and see the “active threads“. I’d try to answer random questions, even if I didn’t post the answers. I started to blog and write, mostly to see if I could explain things back in a way that made sense. It became a career, but before that it was a way to impress hiring managers. It also forced me to learn more about little topics and all of that knowledge helped me to be more effective at my job.

Taking a little time every week to learn something, work on your career, and document it (hopefully as a #SQLNewBlogger). It is a good way to improve your skills and also showcase them for the next person that hires (or promotes) you. Hopefully into a position that you desire and choose.

Steve Jones

Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.

Posted in Editorial | Tagged | Comments Off on Becoming a Better DBA

Daily Coping 15 Jun 2022

I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag.

Today’s tip is to think of what is a little thing you are grateful for today?

I’m grateful that I enjoy my job. There are lots of things to be grateful for in my life, but this is one that occurred to me. My job can be tough some times, especially now with a lot of travel, and it can stink sometimes when deadlines or responsibilities create stress.

However, overall, I enjoy my job. I like the people, the challenges, the discussions, and the travel. That’s a nice perk that I can earn a good living and enjoy the process of doing so.

Posted in Blog | Tagged , , | Comments Off on Daily Coping 15 Jun 2022

Daily Coping 14 Jun 2022

I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag.

Today’s tip is to list what values are important? Use them today.

Compassion, Positivity, Perseverance.

For me, these matter. This past weekend I was camping with family and friends. Friends can be hard, and I had some in my family that were struggling with the extra people. I made it a point to listen and not offer solutions or judgment, but be understanding and supportive. And give a hug.

I’ve also been working to rehab my ankle. I couldn’t do a lot of walking, though I did some. Still using a cane, but also trying to remain positive that it is getting better.

I also had to persevere and keep moving along, even when the ankle hurts and I’m a little sad I can’t participate as much as everyone else. However, I keep moving forward.

Posted in Blog | Tagged , , | 1 Comment

T-SQL Tuesday #151 Coding Standards

This month the T-SQL Tuesday blog party is hosted by my good friend, Mala. This is her fourth time hosting and she has a good topic this time. While I love her hosting, and a few others, I would like to see more people participate and take a month on their technology of choice.

You can submit to host by contacting me on Twitter and reading the host page.

Coding Standards

I am a big fan of standards, both for coding and naming, when building software. I feel that having some standards help share information among staff. Since staff might come and go on a project, the less friction that we have, the better off we are.

With that being said, the main standard for me is that the team has a standard. Preferably the organization has a standard, but we want to ensure that everyone follows a similar style of coding. This includes naming and style.

For example, if we want plural names for all entities, let’s stick to that. I think singular makes more sense, and despite my habit of years of plural, I have been working to change. If my team wanted to go one way or the other, I’d just work with them.

The same thing goes for commas. I like commas before a column list, but if the team prefers after, then that’s OK. I can adapt. Especially with a tool like SQL Prompt that let’s me easily reformat to another style.

The other advantage of coding standards, apart from transferring information, is that we can use templates and snippets of code as a way to speed up coding. We can even write or use code generators to ensure that we build the code that everyone understands.

A Few Specifics

For me, these are things I’d set up if there were no standards. I’d be welcome to debate on them and be willing to change. These are for SQL. For other languages, there would be similar choices based on the language.

  1. commas before column list columns
  2. start column list on a new line
  3. FROM, WHERE, ORDER, GROUP, HAVING all indented 1 space or tab from left
  4. I prefer spaces, but only lightly.
  5. align all clauses in WHERE on separate lines
  6. entities use singular names
  7. primary keys are named <tablename>PK
  8. if surrogate keys, use <tablename>ID as the column header
  9. FK constraints use FK_<source>_<destination>_<column1>_<column2>
  10. ALL indexes named as CDX_<table>_<column> for clustered or NDX_<table>_<column> for non clustered. CCX or NCX for columnstore.
  11. FK column in the child table uses the same name as the PK column in the parent.

There are more, but this is a quick list. The important thing is to have standards.

Posted in Blog | Tagged , , | 1 Comment