Quick Summary
A database is a structured collection of data — customer records, financial transactions, inventory, employee information — stored in a system that allows it to be queried, updated, and reported on reliably. Database management is the set of tasks required to keep a database performing well, secure, and recoverable: installation and configuration, schema design, user access management, query optimisation, patching, monitoring, and backup. For Ethiopian businesses, the choice of database platform, the decision between on-premise and cloud-hosted databases, and the importance of power protection for on-premise database servers are material decisions that affect daily operational performance.
Database Types for Ethiopian Businesses
| Database Type | Examples | Best For | Ethiopian Business Context |
|---|---|---|---|
| Relational (SQL) | MySQL, PostgreSQL, Microsoft SQL Server, MariaDB | Structured business data — financial records, customer data, inventory, HR, ERP | The dominant database type for Ethiopian business applications — ERP systems, accounting platforms, and custom business applications are typically built on relational databases |
| Document (NoSQL) | MongoDB, CouchDB, Firebase | Flexible data structures — content management, product catalogues, mobile app data | Used in custom web and mobile application development; not typically the primary business database type |
| Time-series | InfluxDB, TimescaleDB | Monitoring data, IoT sensor data, infrastructure metrics | Used in IT infrastructure monitoring (Zabbix, Prometheus); not typical for general business data |
| Cloud managed database | AWS RDS, Azure SQL Database, Google Cloud SQL | Relational databases hosted and managed by a cloud provider — no on-premise database server required | Eliminates need for on-premise database hardware; appropriate for businesses with reliable internet connectivity |
Core Database Administration Tasks
Installation and Configuration
Installing the database engine on the server, configuring memory allocation, storage paths, network access, and initial security settings. Default configurations are not appropriate for production use.
Schema Design and Maintenance
Tables, columns, data types, indexes, and relationships determine how effectively data can be stored and queried. Poor schema design creates performance and integrity issues that become harder to fix as the database grows.
User Access Management
Creating database users with appropriate permissions — least privilege applied to database access. No application should connect with administrative (root/sa) credentials.
Performance Monitoring and Tuning
Identifying slow queries, missing indexes, and resource constraints. Performance problems in a database manifest as slow application response across the entire organisation.
Backup Configuration and Verification
Scheduling automated database backups, verifying jobs complete, testing restoration, and managing off-site copies. A server snapshot may not capture the database in a consistent state.
Patch Management and Upgrades
Applying security patches and planning major version upgrades before end-of-life. Unpatched database engines are commonly targeted in cyber attacks.
Capacity Planning
Monitoring storage growth and resource utilisation 12 months ahead. A database server that runs out of storage stops accepting writes.
On-Premise vs Cloud-Hosted Databases
Ethiopian context: The combination of power variability and long lead time for server hardware replacement in Ethiopia makes the cloud-hosted database model attractive for businesses with reliable internet connectivity. An on-premise database server damaged by a power surge may not be recoverable for weeks. A cloud-hosted database is unaffected by local power events.
| Factor | On-Premise | Cloud-Hosted (DBaaS) |
|---|---|---|
| Hardware dependency | Requires server hardware — procurement, maintenance, power protection, cooling | No on-premise hardware; managed by cloud provider |
| Power vulnerability | Requires UPS and ideally generator; outages risk data corruption | Cloud provider manages power redundancy at data centre level |
| Internet dependency | Local network access — works during internet outages | All access requires internet connectivity |
| Administration overhead | Full DBA responsibility — OS, engine, patches, backup, monitoring | Provider handles engine, patches, hardware; business handles schema, users, data |
| Cost structure | Capital expenditure (hardware) plus ongoing management | Operational expenditure — monthly fee, scales with usage |
| Data sovereignty | Data remains on-site in Ethiopia — relevant for regulated sectors | Data stored in provider's data centre (typically outside Ethiopia) |
| Recovery after hardware failure | Requires hardware replacement — can take days to weeks in Ethiopia | Provider replaces hardware with no service interruption; SLA typically 99.95%+ |
Database Security Fundamentals
- Change default credentials immediately: Default administrative passwords are widely known and actively exploited.
- Disable external network access unless required: Databases exposed to the internet are one of the most common attack vectors.
- Encrypt data at rest and in transit: Enable encryption for stored data and require TLS connections.
- Audit database access: Enable database audit logging to record who accessed what data and when.
- Separate database users per application: Each application should use a dedicated user with only the permissions it requires.
Frequently Asked Questions
What is the difference between a database and a spreadsheet?
A spreadsheet is a flexible grid appropriate for analysis and small-scale data. A database is a structured storage system enforcing data types, referential integrity, concurrent multi-user access, large data volumes, and powerful query capabilities. Businesses move from spreadsheets to databases when data grows beyond spreadsheet manageability, multiple users need simultaneous access, or reporting requirements exceed spreadsheet capabilities.
Which database is best for an Ethiopian business?
The choice is usually determined by the application — ERP and accounting platforms use specific databases. For new custom applications, MySQL and PostgreSQL are excellent open-source relational databases widely used in Ethiopia. Microsoft SQL Server is used by many Microsoft ecosystem applications including Dynamics 365. The best database is the one correct for the application, well-administered, backed up, and monitored.
Database Management for Your Ethiopian Business
Bright IT Solutions provides database administration, optimisation, and support for Ethiopian organisations — covering MySQL, PostgreSQL, Microsoft SQL Server, and cloud-hosted databases.
Prefer to talk first? Contact us