A database administrator (DBA) operates, maintains, secures, and manages database systems. The title should not be a catchall for everyone who works with databases: SQL Server environments require distinct competencies across administration, development, and data movement. section 1.0
Common mistakes and distinctions include:
- Mistake #0—“It’s just a database”: underestimating the data tier leads to inadequate budgets, insufficient development time, weak operational support, and ambiguous DBA responsibilities. section 1.1
- Accidental DBA: an application developer with limited SQL Server experience may suddenly own development, optimization, administration, and security. section 1.1
- Physical DBA: manages SQL Server instances; logical DBA: develops and tunes databases. section 1.3
The accidental DBA scenario
A small application database grows into a wider SQL Server responsibility. The original application developer now faces performance optimization, administration, security, high availability, and disaster recovery without having planned for those competencies. section 1.1
DBaaS and managed instances reduce some infrastructure work but do not remove DBA skills. Code still needs development and optimization, and hosted services may be unsuitable or too costly for some workloads. section 1.3
