I acknowledge that everyone's experience and abilities are different. Having said that, I want to avoid setting expectations too high (or too low) for a DBA that through actions; appears to be an 'administrator'.
- I am a developer that is deep diving into SQL Server trouble shooting and performance issues. At night I'm watching Brent Ozar videos with a bucket of popcorn.
- A company with several divisions, this division having around 100ish team members
- Many customers with databases having millions of rows with ETL
- A small DBA team that is stretched to handle these same customers. Handle HAG issues, backup, restores, create new deployments for new or upgrading customers.
I am NOT attempting to justify my own opinion. I wish to adjust either my opinion or others in the company.
Given the above, should expectations be that a DBA is simply an 'administrator'? Is this something you've typically seen?
I went into this soap opera (see my other recent questions) with the expectation that a DBA is 'expected' to deep dive. I have come to believe that I have misunderstood and I am leaning towards a DBA - being an 'administrator'.
I welcome others' experiences and perhaps advice on refining this question.