Deep dives on PostgreSQL, MySQL, MongoDB and more — performance tuning, high availability, migrations and production war stories from our DBAs.
11 articles
Showing 11 of 11 articles
A step-by-step guide to migrating an on-premises Microsoft SQL Server database to Amazon RDS for SQL Server — covering native backup/restore via S3 with the rds_restore_database stored procedure, AWS DMS full-load + CDC for near-zero downtime, option group and IAM setup, cutover, and post-migration hardening.
Production setup of Ola Hallengren's SQL Server Maintenance Solution: the four jobs that matter, FULL/DIFF/LOG backup cadence for your RPO, DBCC CHECKDB scheduling, IndexOptimize tuning, encryption, and CommandLog-based alerting.
Production MariaDB Galera Cluster: mariabackup-based SST, MaxScale Galera-aware routing, schema-change strategy with TOI vs RSU, and a troubleshooting playbook for the failures that actually take down production.
Build a production database DR runbook covering RTO/RPO definitions, failover steps, PITR recovery commands, and a verification checklist. Test it quarterly.
Compare Redis persistence modes: RDB snapshots for fast restarts, AOF for sub-second durability, and the combined RDB+AOF approach. Includes data loss and I/O tradeoff matrix.
Secure database credentials with AWS Secrets Manager, automatic rotation, Kubernetes secrets, and git-secrets scanning. Never hardcode connection strings.
Implement MySQL point-in-time recovery using binary logs. Covers binlog configuration, mysqlbinlog replay with stop-datetime, GTID-based filtering, and S3 binlog archival.
Compare PostgreSQL backup approaches: logical dumps, physical base backups, and WAL-G incremental cloud backups. Covers PITR, restore speed, and backup verification.
Deploy a production PostgreSQL HA cluster with Patroni and etcd. Covers configuration, patronictl commands, HAProxy integration, and failover procedures.
PostgreSQL 17 is one of the most impactful releases in years. Incremental backups, vacuum improvements, logical replication failover slots, and planner enhancements are all production-critical changes.
pg_dump takes 4 hours on your 200GB database. pg_basebackup takes 20 minutes and enables point-in-time recovery to any second. Learn to set up WAL archiving, take base backups, and execute a PITR restore.
Get the latest database insights and expert tips delivered to your inbox.
Subscribe to our RSS feed for instant updates.
RSS Feed