Showing entries 2981 to 2990 of 44105
« 10 Newer Entries | 10 Older Entries »
What’s New in MySQL Shell 8.0.21

The MySQL team is proud to announce the general availability of version 8.0.21 of the MySQL Shell.

MySQL Shell Logical Dump and Load Utilities

A new suite of logical dump utilities was introduced in MySQL Shell 8.0.21.
util.dumpInstance(), util.dumpSchemas() and util.loadDump()

Facebook Twitter LinkedIn

MySQL Group Replication – Default response to network partitions has changed

MySQL Group Replication allows you to create an highly-available replication group of servers with minimum effort. It provides automated mechanisms to detect and respond to failures in the members of the group. The response depends on the characteristics of each failure and it is configurable.…

Tweet Share

Hiding instances on MySQL InnoDB Cluster/ReplicaSet

MySQL Router is a core component of InnoDB Cluster/ReplicaSet that enables the automatic routing of client traffic to the right instances of your database architecture. Router can automatically adapt to topology changes, however, there are some scenarios on which one would certainly benefit from having the possibility to tag an instance with a certain attribute that indicates a specific behavior change to Router’s default behavior.…

Facebook Twitter LinkedIn

MySQL Shell AdminAPI – What’s new in 8.0.21?

The MySQL Development Team is happy to announce a new 8.0 Maintenance Release of MySQL Shell AdminAPI – 8.0.21!

As always, we have listened to the growing community of users and introduced a very useful feature for any production deployment of MySQL InnoDB Cluster or ReplicaSet.…

Facebook Twitter LinkedIn

MySQL – Keep an eye on your auto_increment values

In MySQL, it’s very common and recommended to you an auto_increment as Primary Key.

However that integer can have different types each having their size limitation, and they can also be signed or not.

Many people when creating a table use by default the following syntax do define their auto_increment primary key:

id int auto_increment primary key

This is a signed integer where the maximum value is 2,147,483,647.

It’s recommended as a DBA to keep an eye on how fast your tables are filling up and how much records can still be added to your tables.

And this can happen even to the bests ! (see this Github Availability Report on May 5th at 00:45)

MySQL Shell Plugin

Once again, MySQL Shell comes to the rescue with an easy plugin: …

[Read more]
You Can Now Use Binary Log Checksums with Group Replication

Group Replication enables you to create fault-tolerant systems with redundancy by replicating the system state to a set of servers. Even if some of the servers subsequently fail, as long it is not all or a majority, the system is still available.…

Tweet Share

Announcing The Continuent Tungsten Clustering MySQL Use Case Webinar Series

We’re excited to announce our new Continuent Tungsten Clustering MySQL Use Case Webinar Series for 2020 with Eero Teerikorpi, Founder & CEO of Continuent.

Tags:  MySQL tungsten clustering Webinar use case High Availability data protection geo-scale Geo-Distributed

[Read more]
MySQL Query Performance Troubleshooting: Resource-Based Approach

When I speak about MySQL performance troubleshooting (or frankly any other database), I tend to speak about four primary resources which typically end up being a bottleneck and limiting system performance: CPU, Memory, Disk, and Network.

It would be great if when seeing what resource is a bottleneck, we could also easily see what queries contribute the most to its usage and optimize or eliminate them. Unfortunately, it is not as easy as it may seem.

First, MySQL does not really provide very good instrumentation in those terms, and it is not easy to get information on how much CPU usage, Disk IO, or Memory a given query caused.  Second, direct attribution is not even possible in a lot of cases. For example, disk writes from flushing data from the InnoDB buffer pool in the …

[Read more]
Automatic Schema Synchronization in NDB Cluster 8.0: Performance Schema Tables

The Automatic Schema Synchronization mechanism, detailed in a two part series: part 1 and part 2, automatically detects and synchronizes mismatches in metadata between NDB Dictionary and MySQL Server’s Data Dictionary. Information about the mechanism is exposed through different MySQL Server status variables.…

Tweet Share

Releasing ProxySQL 2.0.13

ProxySQL is proud to announce the release of the latest stable version of ProxySQL 2.0.13 on the 15th of July 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

New Features

Although only bug fixes are supposed to go into ProxySQL 2.0, we had to introduce a few minor new features:

  • A client can force ProxySQL to run a query in a new connection using a query annotation using create_new_connection=1 in a comment. For example SELECT /* create_new_connection=1 */ 1 . See #2874
  • Added …
[Read more]
Showing entries 2981 to 2990 of 44105
« 10 Newer Entries | 10 Older Entries »