This is Part 3 in a three-part series. Please see Part 1 and Part 2 for more.
What does your average day look like?
I’m going to punt to my “A Day in the Life” series here.
When you started, did you know what your position was going to look like 1 month, 6 months, 1 year, 5 years from then? How accurate has that been so far?
I’ve only been at my current job for about 2 1/2 years, but I can speak to the shorter intervals.
This is Part 2 of a series. Please see [Part 1]/2019/09/03/qa-dealing-with-thousands-of-databases/) for the background and more.
What is the most unexpected experience you’ve had in this position?
I have two answers to this question.
I write more dynamic SQL in any given week than I had previously in my career - all years combined!
Many DBAs deal with issues around parameter sniffing and plans being stuck in cache that don’t work well for a number of their requests as a result.
This is part one of a three-part series.
I’ve mentioned in various places, including in blog posts on occasion, that my production SQL Server instance hosts several thousand (nearly 9000 as of this writing) databases. People are usually surprised to hear this and it often leads to interesting conversation.
Jon Shaulis (blog | twitter) asked me on Twitter recently:
@ALevyInROC Have you written before about your experience managing thousands of databases by chance?
This is my fourth installment in a series responding to Steve Jones’s (blog | twitter) #SQLCareer challenge. I jotted down most of what I did through the day, filling a page and then some in a small notebook with timestamps and short reminders of what happened. For more, check out the #SQLCareer hashtag on Twitter.
Background I bet you thought I’d forgotten all about this “project”. I decided to pick things back up on this day because I’ve been light on content lately, I had a few things going on, and keeping notes for this series strangely helps me focus on my day.
This is my third installment in a series responding to Steve Jones’s (blog|twitter) #SQLCareer challenge. I decided to jot down most of what I did through the day, filling a page and a half in a Field Notes notebook with timestamps and short reminders of what happened. For more, check out the #SQLCareer hashtag on Twitter.
Background I chose to record this day because I was working from home as my car was in the shop and I thought I might get some bigger things done without the distractions of being in the office.
This is my second installment in a series responding to Steve Jones’s (blog|twitter) #SQLCareer challenge. I decided to jot down most of what I did through the day, filling a page and a half in a Field Notes notebook with timestamps and short reminders of what happened. For more, check out the #SQLCareer hashtag on Twitter.
Background I’m one of two DBAs in my company, and my colleague is (still) on holiday on the opposite side of the planet so I’m juggling everything – on-call, regular operations, consults with developers, you name it.
This is my first installment in (I hope) a series responding to Steve Jones’s (blog|twitter) #SQLCareer challenge. I decided to jot down most of what I did through the day, filling a page and a half in a Field Notes notebook with timestamps and short reminders of what happened. For more, check out the #SQLCareer hashtag on Twitter.
Background I’m one of two DBAs in my company, and my colleague is on holiday on the opposite side of the planet (literally) for a couple weeks so I’m juggling everything - on-call, regular operations, consults with developers, you name it.
I really enjoy my job. I became a full-time production DBA about 14 months ago and it has been an overwhelmingly positive move. I work for a good company and with a terrific group of people. Many days, I have to force myself to leave the office because I was so engrossed in a task and just didn’t want to set it aside.
But there’s something that not everyone might consider before taking on this job.