THE CORE AIM OF VOCABULARY MASTERY · DATABASE ADMINISTRATION VOCABULARY · AVAILABILITY → PERFORMANCE → BACKUP → SECURITY → RECOVERY
Database administration vocabulary is the language used to operate databases reliably, securely and efficiently. Terms such as backup, restore, replication, failover, index, query plan, connection, lock, transaction log and maintenance window matter because database administration is about keeping data usable while protecting integrity and availability.
The core aim of vocabulary mastery for database administration vocabulary is operational database clarity. Learners should be able to explain whether a problem concerns availability, performance, security, capacity, backup or recovery—and describe the evidence that supports the diagnosis.
This page is the Database Administration Vocabulary owner inside the eduKateSG Vocabulary hub. For database structure and queries, use Database Vocabulary and SQL Vocabulary.
Central proposition: Database administration vocabulary is mastered when the learner can describe the system state, identify the operational risk and name the safe recovery or performance action.
The 60-Second Database Administration Vocabulary Router
- Availability: instance, uptime, failover, replica.
- Performance: index, query plan, latency, lock, contention.
- Capacity: storage, memory, connection pool, growth.
- Protection: role, privilege, encryption, audit.
- Backup: full backup, incremental, snapshot, retention.
- Recovery: restore, recovery point, recovery time, transaction log.
The Database Administration Vocabulary Architecture
| Area | Core terms | Core question |
|---|---|---|
| Availability | replica, failover, uptime | Is the database reachable? |
| Performance | index, plan, latency | Why is the workload slow? |
| Concurrency | lock, blocking, deadlock | Are sessions interfering with each other? |
| Capacity | storage, memory, connections | Is a resource being exhausted? |
| Security | role, privilege, audit | Who can access or change data? |
| Recovery | backup, restore, RPO, RTO | Can data and service be recovered? |
Backup and Replication Are Different
Replication copies data changes to another database instance to support availability or scale. A backup is a recoverable copy retained for restoration. Replication can reproduce accidental deletion or corruption, which is why it does not replace a backup strategy.
A Worked Example: Index
An index can speed up certain reads by providing a more efficient access path, but it also consumes storage and adds work to writes. Database administration vocabulary should therefore connect indexing to workload trade-offs rather than assume “more indexes is better.”
A Worked Example: Lock and Blocking
A lock protects data consistency while a transaction operates. Blocking occurs when one session must wait for another because of an incompatible lock. A deadlock occurs when sessions wait on each other in a cycle that the database must resolve.
Recovery Point and Recovery Time
A recovery point objective expresses how much data loss can be tolerated, while a recovery time objective expresses how quickly service should be restored. These terms help connect backup design to business impact.
Database Administration and Security
Useful terms include role, privilege, least privilege, audit log, encryption and credential rotation. Administration should minimize broad access and preserve traceability for sensitive changes.
How to Learn Database Administration Vocabulary
- Use a safe development database.
- Observe connections and query plans.
- Create and remove indexes experimentally.
- Practise backup and restore workflows.
- Simulate replica and failover concepts.
- Read logs during performance problems.
- Document recovery objectives and verification steps.
Common Database Administration Vocabulary Mistakes
Treating replication as backup
Repair: separate availability copies from recoverable historical copies.
Assuming every slow query needs an index
Repair: inspect the query plan and workload first.
Confusing blocking with deadlock
Repair: distinguish ordinary waiting from circular waiting.
Testing backups without testing restore
Repair: verify recovery, not merely backup completion.
Frequently Asked Questions
What is database administration vocabulary?
It is the specialised language used to manage database availability, performance, security, capacity, backups and recovery.
What terms should beginners learn first?
Start with backup, restore, replica, failover, index, query plan, lock, connection and transaction log.
What is the difference between backup and replication?
Replication supports current copies for availability or scale; backups preserve recoverable copies for restoration.
What is a deadlock?
It is a circular wait in which transactions block one another until the database resolves the situation.
How can I learn DBA vocabulary?
Use safe test databases and connect each term to performance, backup, security or recovery actions you can observe.
Where This Article Fits in the eduKateSG Vocabulary Ecosystem
- Vocabulary Hub — the broad route.
- Database Vocabulary — relational foundations.
- SQL Vocabulary — query language.
- Systems Administration Vocabulary — operations.
- Cloud Computing Vocabulary — managed database infrastructure.
The Database Administration Vocabulary Standard
Database administration vocabulary reaches its core aim when the learner can identify whether a database problem concerns performance, concurrency, security, capacity, availability or recovery—and describe the appropriate operational response.
That is the standard: database operations language precise enough to protect both service and data.