MySQL Database Administration Commands

To login (from unix shell) use -h only if needed. # [mysql dir]/bin/mysql -h hostname -u root -p Create a database on the MySQL server. mysql> create database [databasename]; List all databases on the MySQL server. mysql> show databases; To delete a database. mysql> drop database [database name]; To delete a table. mysql> drop table... Continue Reading →

Securing MongoDB with X.509 Authentication

We look at how to configure transport encryption on a deployed MongoDB replica set.Encrypting intra-node traffic ensures that no one can “sniff” sensitive data on the network.This article will guide you through the process of setting up a MongoDB cluster that will utilise X.509 authentication with self signed certificates. Our cluster will consist of 3... Continue Reading →

CPU Utilisation and Slow Queries in MongoDB

If we have a  performance issue on MongoDB database, there are a number of things to look at, such as indexing strategies, database schema design issues, abnormal traffic load, network problems, inadequate available physical memory resources, locking problems, inappropriate access strategies, hardware limitations, and the number of open database connections. An obvious place to start... Continue Reading →

Deploying PostgreSQL on a Docker Container

PostgreSQL, often simply "Postgres", is an object-relational database management system (ORDBMS) with an emphasis on extensible and standards-compliance. As a database server, its primary function is to store data, securely and supporting best practices, and retrieve it later, as requested by other software applications, be it those on the same computer or those running on... Continue Reading →

MySQL Connection Usage

By default 151 is the maximum permitted number of simultaneous client connections in MySQL 5.5. If you reach the limit of max_connections you will get the “Too many connections” error when you to try to connect to your MySQL server – which means all available connections are in use by other clients. MySQL permits one extra connection on top of the... Continue Reading →

PostgreSQL Point-in-time Recovery (Incremental Backup)

PostgreSQL “Point-in-time Recovery” (PITR) also called as incremental database backup , online backup or may be archive backup. At all times, PostgreSQL maintains a write ahead log (WAL) in the pg_wal/ subdirectory of the cluster's data directory. The log records every change made to the database's data files. This log exists primarily for crash-safety purposes: if the system crashes, the database can... Continue Reading →

Powered by

Up ↑