Showing entries 7103 to 7112 of 44029
« 10 Newer Entries | 10 Older Entries »
Optimizing and repairing MySQL databases with mysqlcheck

We’ll show you how to repair a MySQL database ane, how to optimize MySQL database and tables. We will talk about mysqlcheck which is a maintenance command line tool that allows you to check, analyze, repair, and optimize MySQL/MariaDB tables and databases. Repairing MySQL database is not complicated process, just follow the steps bellow carefully. […]

Upgrading to MySQL 5.7? Beware of the new STRICT mode

This blog post discusses the ramifications of STRICT mode in MySQL 5.7.

In short

By default, MySQL 5.7 is much “stricter” than older versions of MySQL. That can make your application fail. To temporarily fix this, change the

SQL_MODE

 to

NO_ENGINE_SUBSTITUTION

 (same as in MySQL 5.6):

mysql> set global SQL_MODE="NO_ENGINE_SUBSTITUTION";

MySQL 5.7, dates and default values

The default

SQL_MODE

 in MySQL 5.7 is:

ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

That makes MySQL operate in “strict” mode for transactional tables.

“Strict mode …

[Read more]
MySQL Downgrade Caveats

In this blog, we’ll discuss things to watch out for during a MySQL downgrade.

Previously, I wrote the blog MySQL upgrade best practices. Besides upgrading your MySQL version, sometimes you need to downgrade. When it comes to downgrading MySQL, there are two types of downgrade methods supported:

  1. In-Place Downgrade: In this method, you use the existing data directory and replace MySQL binaries, followed by a
    mysql_upgrade
     execution. This type of downgrade is supported within the same release series. For example, in-place downgrades are supported when moving from 5.7.12 to 5.7.10.
  2. SQL Dump Downgrade: An SQL dump is …
[Read more]
MySQL Query Tuning Trilogy: Working with optimizer and SQL tuning (3rd and final part)

Join us on Tuesday, October 25th, for the third and final part of our webinar trilogy on MySQL Query Tuning, in which we look at the query tuning process and tools to help with that. So far in this trilogy we’ve covered topics such as SQL tuning, indexing, the optimizer and how to leverage EXPLAIN to gain insight into execution plans.

For Part 3, Krzysztof Książek, Senior Support Engineer at Severalnines, will now take a look at working with the optimizer as well as SQL tuning. This will include a discussion on how execution plans are calculated and a closer look at InnoDB statistics, how to hint optimizer and finally, how to optimize SQL.

MySQL Query Tuning (III): Working with optimizer and SQL tuning

Tuesday, October 25th

Sign up for the webinar

[Read more]
MySQL Cluster 7.5 Is Now GA!

The MySQL team at Oracle are excited to announce the immediate availability of the MySQL Cluster 7.5.4 GA release!

The development focus has been on improving overall performance and ease of use, combined with improved SQL support and the introduction of read optimized and fully replicated tables, all of which allow for better support of a variety of use cases. 

Use Case: Hadoop Performance Records Smashed by Hops and MySQLCluster--delivers over 1.2 million operations per second

The key enhancements delivered by MySQL Cluster 7.5 are summarized below:

Improved Performance: Improvements in index/range scan performance and internal thread handling will allow for better use of existing hardware and …

[Read more]
Evolving MySQL Compression - Part 1

Pinterest Infrastructure engineers are the caretakers of more than 75 billion Pins–dynamic objects in an ever-growing database of people’s interests, ideas and intentions. A Pin is stored as a 1.2 KB JSON blob in sharded MySQL databases. A few years back, as we were growing quickly, we were running out of space on our sharded MySQL databases and had to make a change. One option was to scale up hardware (and our spend). The other option–which we chose–was using MySQL InnoDB page compression. This cost a bit of latency but saved disk space. However, we thought we could do better. As a result, we created a new form of MySQL compression which is now available to users of Percona MySQL Server 5.6.

JSON is efficient for developers, not machines

As a small start-up, Pinterest built and scaled its MySQL …

[Read more]
Percona Server 5.6.33-79.0 is now available

Percona announces the release of Percona Server 5.6.33-79.0 on October 18th, 2016. Download the latest version from the Percona web site or the Percona Software Repositories.

Based on MySQL 5.6.33, including all the bug fixes in it, Percona Server 5.6.33-79.0 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free – this is the …

[Read more]
MySQL 8.0 Labs: [Recursive] Common Table Expressions in MySQL (CTEs), Part Two – how to generate series

Here is the second in a series of posts about CTEs, a new feature of MySQL 8.0, available in this Labs release. The first post ended with:

Inside the recursive CTE definition (the part in AS (…)), some syntax constraints must be respected […]

  • a recursive SELECT mustn’t contain GROUP BY, aggregate functions
    (like SUM), ORDER BY, LIMIT, DISTINCT (this rule doesn’t apply to the non-recursive/anchor/seed SELECT)
  • a recursive SELECT must reference the CTE only once and only in its
    FROM clause, not in any subquery.

MySQL Connector/Node.JS 1.0.4 now on npmjs.com

MySQL Connector/Node.JS 1.0.4 was recently released as a development milestone release. This is the first version available via npmjs.com. npmjs.com is the central registry for Node.JS packages. This and potential future official MySQL packages can be found using the @mysql organisation. For this to work we had to change the package name to contain that prefix and have chosen the name @mysql/xdevapi as this package provides the implementation of our X DevAPI for Node.JS and we have a free namespace for potential future libraries as part of our Connector/Node.JS product.

Given an existing Node.JS project we can easily install the library:

$ npm install --save @mysql/xdevapi …
[Read more]
MySQL Replication Smackdown – October Meetup Event

From our October NYC Meetup, Ronald Bradford gave a presentation on “MySQL Replication Smackdown – Evaluating current replication capabilites”. Some of the details of his presentation included:


Download PDF Presentation

  • What are the common approaches to data replication?
  • Why do you want to use data replication in your application?
  • What MySQL offers with different replication types.
  • What are the limitations of different MySQL replication.
  • How to evaluate your architecture needs
  • A new architecture mindset …
[Read more]
Showing entries 7103 to 7112 of 44029
« 10 Newer Entries | 10 Older Entries »