Elevating DBA Skills: Practical Insights from a Bank’s Database Team

1. Introduction

Database administrators (DBAs) are responsible for ensuring the stable operation of production databases. Beyond handling production changes and incident resolution, they must continuously enhance their skills. This article, from a bank DBA’s perspective, discusses the "self-cultivation" of DBAs.

2. Seeing the Mountain as a Mountain

DBAs should study their work thoroughly. Typical DBA tasks include daily maintenance, environment provisioning, upgrade migrations, development support, and incident handling. Daily inspections, once manual, have been standardized, scripted, and tool‑enabled to reduce errors and improve capacity risk detection. Backup must be performed daily, and recovery testing is mandatory.

Environment provisioning has moved from standardization to automation using Golden Image software and PaaS platforms, achieving consistency and speed.

Upgrade migrations involve selecting appropriate software versions (preferably LTS), coordinating with application architecture changes, and tailoring upgrade procedures to data volume, importance, and downtime windows. Three key upgrade lessons are:

Choose suitable LTS versions for databases, middleware, OS, and hardware to align lifecycles.

Plan upgrades together with application architecture and feature upgrades to improve testing efficiency.

Develop standardized upgrade processes based on data size, criticality, and maintenance windows, and adopt a “begin with the end in mind” mindset.

Supporting development and testing consumes the largest portion of a DBA’s time. About 80% of performance issues stem from SQL. The bank incorporates SQL best practices into development standards and uses SQL review tools. Execution plans and statistics collection are crucial for stable performance.

The bank built a custom statistics collection tool that gathers, copies, or sets statistics based on table size, partitioning, workload patterns, and data change characteristics, ensuring stable SQL performance. Hints and SQL profiles/baselines remain essential.

Effective daily operations, environment provisioning, upgrade migrations, and development support naturally reduce database incidents, though incident response remains vital. During incidents, DBAs should adopt a “wartime” mindset: follow commands, report findings, prioritize minimizing business impact, respond quickly, communicate clearly, and cut connections when necessary.

3. Seeing the Mountain is Not a Mountain

DBAs often focus on a single database product, which can limit understanding when new products emerge. It is important to study each product deeply, not only its operations but also its underlying principles.

For example, PostgreSQL follows classic relational concepts, while MySQL’s notion of a database aligns more with Oracle/DB2 tablespaces, and Oracle’s schema and user concepts differ from those in other systems. DBAs should broaden their expertise across multiple products.

Suggested structure for comparing different database products is illustrated below.

Recommended resources for deeper understanding of database internals:

MySQL: MySQL Internals (dev.mysql.com/doc/internals/en/), preferably the 5.7 version.

PostgreSQL: The Internals of PostgreSQL (www.interdb.jp/pg/).

Oracle: Oracle Core Essential Internals for DBA by Jonathan Lewis.

4. Seeing the Mountain is Still a Mountain

“Lushan mist and Zhejiang tides, endless regrets until arrival. When you return, nothing remains.” – Su Dongpo Technology, like life, follows this rhythm.

Despite the proliferation of KV, document, graph, and time‑series databases, relational databases will remain the dominant mainstream for the next decade and beyond because their relational model defines the world.

All relational databases share three essential components: SQL parsing, transaction management, and storage engine. Centralized databases combine these, while distributed databases often separate them across nodes for scalability.

DBAs should strive to understand databases from fundamentals to advanced concepts, forming their own views on future trends.

5. Conclusion

In summary, the discussion emphasizes that distributed databases are the future, and DBAs should continuously think and adapt.