Problems with MySQL table optimisation
Example: mysql> optimize table wp_actionscheduler_actions; +——————————————-+———-+———-+——————————————————————-+ | Table
Example: mysql> optimize table wp_actionscheduler_actions; +——————————————-+———-+———-+——————————————————————-+ | Table
Background You might find on a MySQL 8.x or MariaDB 10.4 server that suddenly disk space just evaporates. After using ncdu you see the problem
To see what’s happening on a busy MySQL server, use this: mysql -uroot -e “show full processlist” If you want to do this continuously, try
Background When installing Virtualmin, the system will prompt for small, medium, large and huge. The question is how are these parameters defined? By examining the
Working servers suddenly start giving the error below when restoring a MySQL database that contains datetime fields with 0000-00-00 defaults: user@server:/tmp# mysql -uuser -ppassword database_name
MongoDB is a weird little database but seems really popular and works nicely with low overhead Javascript applications. This article highlights a few key pointers
Background On a legacy server with an older version of MariaDB, restoring to a newer Virtualmin server that run MySQL 8 might be problematic. The
When performing certain MySQL backup operations you might end up with the following message: [ERROR] mysqldump: Couldn’t execute ‘show create table `wp_options`’: Table ‘./site_wordpress/wp_options’ is
Background After upgrading from Ubuntu 18.04 to Ubuntu 20.04, MySQL isn’t working and systemctl status mysql.service show there are problems. You see this line lurking
Here are some useful commands when working with Microsoft SQL and Linux, specifically pertaining to the `sqlcmd` mssql-cli utility. Update 16 July 2021 It appears