I'm part of the product marketing team at ManageEngine, and we're currently preparing content for an upcoming webinar on preventing DBA burnout. While I work closely with database professionals, I don't have hands-on DBA experience myself, so I'd really value learning from those who do.
What does a typical day as a DBA look like for you, and what ends up consuming most of your time? And what key performance metrics do you focus on primarily?
We will use your views to fine tune our content.
Jump to Post— Reverend Jim 6,665When I was a DBA, if I did a proper job on design and implementation, my daily routine consisted of checking that the nightly backups ran. On the first of every month, and at every transition to/from daylight saving there were a few additional checks. I wrote a number of …
Having to attend burnout seminars is really wearing me down TBH.
When I was a DBA, if I did a proper job on design and implementation, my daily routine consisted of checking that the nightly backups ran. On the first of every month, and at every transition to/from daylight saving there were a few additional checks. I wrote a number of monitoring scripts that would automatically text me if anything went amiss in the middle of the night (our control centre was staffed 24x7). Unless I was doing design, my DBA work only counted for about an hour per day of my time.
The one thing I would NEVER do is give AI access to company data. The number of stories about AI wiping out company data means it's an untrustworthy system and should NEVER be deployed on mission critical systems.
AI is great as an assistant at times but simply nope to giving it control or access to mission critical systems.
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.
