Showing entries 8171 to 8180 of 44865
« 10 Newer Entries | 10 Older Entries »
Emulating Sequences in MySQL and MariaDB

Sequences are objects defined by the SQL standard that are used to create monotonically increasing sequences of numeric values. Whenever nextval is called on a sequence object, it generates and returns the next number in the sequence. For MySQL and MariaDB users, this might sound similar to MySQL’s AUTO_INCREMENT columns, but there are some differences: Sequences are defined by the ... Read More

ProxySQL 1.2.1 GA Release

The GA release of ProxySQL 1.2.1 is available. You can get it from https://github.com/sysown/proxysql/releases. There are also Docker images for Release 1.2.1: https://hub.docker.com/r/percona/proxysql/.

ProxySQL is a high-performance proxy, currently for MySQL and its forks (like Percona Server and MariaDB). It acts as an intermediary for client requests seeking resources from the database. ProxySQL was created for DBAs by René Cannaò, as a means of solving complex replication topology issues.

This post is published with René’s approval. René is busy implementing more new ProxySQL features, so I decided to make this announcement!

[Read more]
How to Password-Protect Directories with mod_authn_dbd and MySQL on Apache (Debian 8)

This guide explains how to password-protect web directories (with users from a MySQL database) with mod_authn_dbd on Apache2 on a Debian 8 (Jessie) server. It is an alternative to the plain-text password files provided by mod_auth and allows you to use normal SQL syntax to create/modify delete users.

SQLyog MySQL GUI 12.2.5 Released

With SQLyog MySQL GUI 12.2.5, JSON comes to SQLyog. This is a new and major thing.  Also, Foreign Key management with NDB tables was added and the user- filter was improved in the User Manager. Additionally, some non-critical GUI bugs were fixed.

Changes as compared to MySQL GUI 12.2.4 include:

Features:

* Added basic support for the JSON datatype as of MySQL 5.7.8+ and MySQL Cluster 7.5.2+. The datatype is now available in the CREATE/ALTER TABLE dialog and JSON data will open in the BLOB-viewer. In the BLOB-viewer we have added validation that content is valid JSON. Also JSON-related keywords and functions are recognized in syntax highlighting and autocomplete. Also please see note at the bottom.
* SQLyog GUI now supports Foreign Key constraints between NDB tables for MySQL Cluster 7.3+.
* It is now possible to filter the users based on a string in the …

[Read more]
SQLyog MySQL GUI 12.2.5 Released

With SQLyog MySQL GUI 12.2.5, JSON comes to SQLyog. This is a new and major thing.  Also, Foreign Key management with NDB tables was added and the user- filter was improved in the User Manager. Additionally, some non-critical GUI bugs were fixed.

Changes as compared to MySQL GUI 12.2.4 include:

Features:

* Added basic support for the JSON datatype as of MySQL 5.7.8+ and MySQL Cluster 7.5.2+. The datatype is now available in the CREATE/ALTER TABLE dialog and JSON data will open in the BLOB-viewer. In the BLOB-viewer we have added validation that content is valid JSON. Also JSON-related keywords and functions are recognized in syntax highlighting and autocomplete. Also please see note at the bottom.
* SQLyog GUI now supports Foreign Key constraints between NDB tables for MySQL Cluster 7.3+.
* It is now possible to filter the users based on a string in the …

[Read more]
Security Validation and Password Expiration in MySQL 5.7

This blog post focuses on MySQL 5.7's newly improved features of security validation and password expiration.

The post Security Validation and Password Expiration in MySQL 5.7 appeared first on Datavail.

Exposing Innodb Internals via System Variables: Part 1, Memory

Introduction

A couple of months ago I decided to give myself a refresher on the mechanics of InnoDB. Having a high level understanding of what’s going on under the hood can help provide the context needed in order to resolve issues you may encounter as well as assist you in ensuring that your MySQL instance is running efficiently. Everyone can stand to go back to basics every now and then, as it can help you pick up concepts that you may have missed the last time you researched the topic.

This time around I decided to give myself a refresher by re-reading the MySQL 5.6 reference manual, chapter 14, which covers the InnoDB engine. Despite having a wealth of documented knowledge and insights, I found that a lot of the points in the documentations were unclear, leading me to do more research and experimentation in order to get a bit of clarity on some of the specifics that I felt were missing. In order to help make the information …

[Read more]
BSL BS: How do you backport fixes from MaxScale 2.0 to MaxScale 1.0?

I have created a GitHub fork of MaxScale which does not include the 2.0 branch.  The repository is called GPLScale.

There is a big potential problem with this.  Take for example the file server/core/utils.c, which now has a new license:
https://github.com/mariadb-corporation/MaxScale/blob/2.0/server/core/utils.c

This file WAS covered under GPL:
  https://github.com/mariadb-corporation/MaxScale/blob/cb3213af6382c380df9fc47347764f087ae7ecb4/server/core/utils.c

When there is a bugfix in 2.0 for server code that existed in 1.0, can that code be backported directly into GPLscale?

a) util.c in 2.0 is clearly …

[Read more]
BSL BS: How do you backport fixes from MaxScale 2.0 to MaxScale 1.0?

I have created a GitHub fork of MaxScale which does not include the 2.0 branch.  The repository is called GPLScale.

There is a big potential problem with this.  Take for example the file server/core/utils.c, which now has a new license:
https://github.com/mariadb-corporation/MaxScale/blob/2.0/server/core/utils.c

This file WAS covered under GPL:
  https://github.com/mariadb-corporation/MaxScale/blob/cb3213af6382c380df9fc47347764f087ae7ecb4/server/core/utils.c

When there is a bugfix in 2.0 for server code that existed in 1.0, can that code be backported directly into GPLscale?

a) util.c in 2.0 is clearly …

[Read more]
TokuDB/PerconaFT fragmented data file performance improvements

In this blog post, we’ll discuss how we’ve improved TokuDB and PerconaFT fragmented data file performance.

Through our internal benchmarking and some user reports, we have found that with long term heavy write use TokuDB/PerconaFT performance can degrade significantly on large data files. Using smaller node sizes makes the problem worse (which is one of our performance tuning recommendations when you have faster storage). The problem manifests as low CPU utilization, a drop in overall TPS and high client response times during prolonged checkpointing.

This post explains a little about how PerconaFT structures dictionary files and where the current implementation breaks down. Hopefully, it explains the nature of the issue, and how our solution helps addresses it. It also provides some contrived benchmarks that prove the solution.

PerconaFT map file disk format

NOTE. …

[Read more]
Showing entries 8171 to 8180 of 44865
« 10 Newer Entries | 10 Older Entries »