Accidental DBA
Posts
What DBAs Want You to Know, Part 2

What DBAs Want You to Know, Part 2

For the non-DBA audience

Kevin Hill
December 13, 2024

Here are 5 more issues SQL Server DBAs often encounter, that could probably be improved (the first 5):

1. Security vs. Convenience Battles

Pushing for best practices (least-privilege access, encryption) often puts DBAs at odds with developers and users who want ease of access. SQL Server’s security model isn’t exactly easy, but giving application user accounts sysadmin is just begging for ransomware.

Solution: Work together to create a corporate policy and have upper management approve deviations.

2. Poor Indexing and Query Design

Bad queries from application code can wreak havoc on performance, and it’s usually the DBA’s problem to fix it after the fact. Application coding and database coding are not the same thing. Procedural vs. Set based is a common issue.

Solution: Collaborate with developers on the SQL they are writing and test both methods.

3. Shadow IT/Unauthorized Databases

Other teams sometimes spin up databases or instances without informing the DBAs, leading to issues down the line.

Solution: Use a tool such as Microsoft’s MAP Toolkit to identify all SQL Servers on the network

4. Emergency-Only Feedback

DBAs often go unnoticed until something goes wrong, which can lead to frustration and burnout.

Solution: Proactively share wins, such as performance improvements or successful disaster recoveries, with the team.

5. Backup/Restore Misunderstandings

Teams often assume backups are the same as high availability or disaster recovery, leading to confusion when issues arise. Also, 3^rd party tools doing backups that the DBA is not aware of can adversely affect the recoverability of a database.

Solution: Educate stakeholders on the differences between backups, HA, and DR, emphasizing their unique roles.