I would like to point out some 'small' things you may not have noticed in the MySQL 8.0.17 Release Notes.  They are small changes compared to things like MVIs, InnoDB cloning, and the like but these are the types of changes that are subtle that may catch you unaware.

1. Host names have grown from 60 to 255 characters.  However your SSL/TLS package may not be able to handle the longer names.

2. If you are an old C/C++ programmer, 'C-style &&, ||, and ! operators that are synonyms for the standard SQL AND, OR, and NOT operators, respectively, are deprecated and support for them will be removed in a future MySQL version'.

3. The ZERO fill attribute is being deprecated as is unsigned FLOAT, DOUBLE, and DECIMAL. You can no longer AUTO_INCREMENT FLOAT and …

Since MySQL 8.0.16, the Router as the possibility to launch an internal webserver (see Jan’s blog post).

Even if this webserver could serve static files, it was the first piece of a much more interesting solution that is now available since 8.0.17.

It’s possible now to query the MySQL Router via its REST API and get a lot of useful information.

Setup

Let’s first configure our MySQL Router to take advantages of this new feature. In this example, I will add the following lines to /etc/mysqlrouter/mysqlrouter.conf that I created using the --bootsrapcommand line argument:

[http_server]
port=8080

[rest_api]

[rest_router]
require_realm=somerealm

[rest_routing]
require_realm=somerealm …

Starting at version MySQL5.6+ by default innodb_file_per_table is enabled and all data is stored in separate tablespaces.

It provides some advantages. I will highlight some of them:

• You can reclaim disk space when truncating or dropping a table stored in a file-per-table tablespace. Truncating or dropping tables stored in the shared system tablespace creates free space internally in the system tablespace data files (ibdata files) which can only be used for new InnoDB data.
• You can store specific tables on separate storage devices, for I/O optimization, space management, or backup purposes. …

As follow up to the previous blog announcement about the conferences and events MySQL Team is attending, we would like to inform you about where you can find us during August & September 2019. Please find the list below.

• August 2019:

  • Mid-Atlantic Developer Conference, Baltimore, US, August 1-2, 2019

    • MySQL Community team is a Bronze sponsor of this Developer conference. Our MySQL Community Manager, David Stokes will be giving 2 sessions as follows:
      • "MySQL & GIS" scheduled for Aug 1 @11:30-12:30pm
      • "MySQL without the SQL — Oh My!" Aug 2 …

Introduction In this article, we are going to see how we can sort an SQL query result set using an ORDER BY clause that takes a RANDOM function provided by a database-specific function. This is a very handy trick, especially when you want to shuffle a given result set. Note that sorting a large result set using a RANDOM function might turn out to be very slow, so make sure you do that on small result sets. If you have to shuffle a large result set and limit it afterward, then it’s... Read More

The post SQL ORDER BY RANDOM appeared first on Vlad Mihalcea.

The MySQL Shell 8.0.17 introduces a novel way of extending its base functionality through plugins, which are JavaScript or Python scripts that allow the user to:

• Register reports that can be used in monitoring tasks through the \show and \watch Shell Commands.

… Facebook Twitter LinkedIn

As announced in the previous blog post, MySQL InnoDB Cluster just got a very much requested feature which makes a complete, out-of-the-box, easy-to-use and versatile HA solution – Automatic Node Provisioning.

InnoDB cluster users can now rely on it for every single step of cluster deployment and management.…

Tweet Share

Cloning MySQL instance data reliably and efficiently is required in many scenarios. This includes MySQL HA solutions where one needs to provision an instance before joining it to a Group Replication cluster or adding it as Slave in classic the replication model.…

Facebook Twitter LinkedIn

In the conclusion of our blog series, Benefits of SQL Diagnostic Manager for MySQL (formerly Monyog), we explore features of SQL Diagnostic Manager for MySQL that allow database administrators to proactively monitor and manage MySQL and MariaDB servers. If you missed it, feel free to read last week’s post on monitoring MySQL and MariaDB servers.

Fix Problems Proactively with Hundreds of Monitors

SQL Diagnostic Manager for MySQL includes hundreds of monitors that are designed to examine the configuration and security of MySQL and MariaDB servers automatically, identify problems and tuning opportunities, and provides database administrators with specific corrective actions.

Use Advisor Rules

The Advisor Rules feature is a set of best practices that enables database administrators to monitor MySQL …

Dear MySQL users,

MySQL Connector/ODBC 8.0.17 is a new version in the MySQL Connector/ODBC 8.0 series,the ODBC driver for the MySQL Server.

The available downloads include both a Unicode driver and an ANSI driver based on the same modern codebase. Please select the driver type you need based on the type of your application – Unicode or ANSI. Server-side prepared statements are enabled by default. It is suitable for use with the latest MySQL server version 8.0.

This release of the MySQL ODBC driver is conforming to the ODBC 3.8 specification. It contains implementations of key 3.8 features, including self-identification as a ODBC 3.8 driver, streaming of out for binary types only), and support of the SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver only).

The release is now available in source and binary form for a number of platforms from our download pages at

…