MySQL for Visual Studio is a product including all of the Visual Studio integration previously available as part of Connector/Net. The 1.2.1 version is a beta release of this product which is feature complete but still can contain minor bugs and is not suitable for production environments.

Why do we need to recover InnoDB dictionary

c_parser is a tool from TwinDB recovery toolkit that can read InnoDB page and fetch records out of it. Although it can scan any stream of bytes recovery quality is higher when you feed c_parser with pages that belong to the PRIMARY index of the table. All InnoDB indexes have their identifiers a.k.a. index_id. The InnoDB dictionary stores correspondence between table name and index_id. That would be reason number one.

Another reason – it is possible to recover table structure from the InnoDB dictionary. When a table is dropped MySQL deletes respective .frm file. If you had neither backups nor table schema it becomes quite a challenge to recover the table structure. This topic however deserves a separate post which I write some other day.

Let’s assume you’re convinced …

The MySQL Windows Experience Team is proud to announce the release of MySQL for Excel version 1.3.1.  This is a RC release for 1.3.x.

As this is a Release Candidate version the MySQL for Excel product can be downloaded only by using the product standalone installer at this link: http://dev.mysql.com/downloads/windows/excel/

Your feedback on this release candidate version is very well appreciated, you can raise bugs on the MySQL bugs page or give us your comments on the MySQL for Excel forum.

Percona is glad to announce the release of Percona Server 5.5.38-35.2 on July 2, 2014 (Downloads are available here and from the Percona Software Repositories). Based on MySQL 5.5.38, including all the bug fixes in it, Percona Server 5.5.38-35.2 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the  …

This article discusses the storage (inline and external) of field data in the InnoDB storage engine. All fields of variable length types like VARCHAR, VARBINARY, BLOB and TEXT can be stored inline within the clustered index record, or stored externally in separate BLOB pages outside of the index record (but within the same tablespace). All of these fields can be classified as large objects. These large objects are either binary large objects or character large objects. The binary large objects do not have an associated character set, whereas the character large objects do.

Within the InnoDB storage engine there is no difference between the way character large objects and binary large objects …

I recently had an opportunity to migrate a customer from a physical server into Amazon’s RDS environment. In this particular case the customers’ platform makes extensive use of MySQL triggers and views.  I came across two significant issues that prevented me from following Amazon’s documentation, which basically states “use mysqldump” but doesn’t call out a specific method of dealing with MySQL triggers and views.

Amazon Relational Database Service (Amazon RDS) is a great platform if you’re looking for complete hands-off management of your MySQL environment, but comes at a cost in the area of flexibility, i.e. you don’t have SUPER privilege and this brings up additional challenges.

1. You need to ensure you set log_bin_trust_function_creators=1 ( by default this is off, 0).
2. You need to clean up your mysqldump syntax.

#1 is easy, you simply make a configuration change …

Is your application multi-tenancy, where each tenant lives in its own database? We have such a scenario at VividCortex, and many of our customers do as well. Wouldn't it be nice to understand which tenants are causing more load than others, which are the noisy neighbors impacting others' experience, and so on? Well, now you can!

We now support per-database metrics in Top Queries. You can change the Rank menu from Queries to Databases, and you will see a breakdown of database activity in the familiar format, all in 1-second resolution.

As you can see from the Lock Waits column in the image, computed columns work as usual too, so you can quickly figure out which databases are consuming more resources such as CPU or IO in addition to the standard metrics (time, count, latency, and so on).

We detect the database by …

THe MySQL APT Repository provides an easy and convenient way to get the latest MySQL software. My test server was need of a refresh so I put on a fresh install of Ubuntu 14.04 and downloaded mysql-apt-config_0.2.1-1ubuntu14.04_all.deb.

sudo dpkg -i mysql-apt-config_0.2.1-1ubuntu14.04_all.deb
[sudo] password for dstokes:
Selecting previously unselected package mysql-apt-config.
(snip)

You will get a choice to install MySQL 5.6 or the latest 5.7 DMR.

sudo apt-get update Pulls the latest information from the repository for the various packages.

sudo apt-get install mysql-server Installs the server and will start it running. And then a quick sudo apt-get install mysql-workbench to get me where i needed to be.

There is a detailed information at …

Percona is glad to announce the release of Percona Server 5.6.19-67.0 on July 1, 2014. Download the latest version from the Percona web site or from the Percona Software Repositories.

Based on MySQL 5.6.19, including all the bug fixes in it, Percona Server 5.6.19-67.0 is the current GA release in the Percona Server 5.6 series. All of Percona’s software is open-source and …

The MySQL Workbench team announces availability of version 6.1.7 of its flagship product.

MySQL Workbench 6.1.7 is a periodic maintenance release including 17 bug fixes. Additionally, the supported Linux distribution list has been refreshed. Users of the product are recommended to upgrade to this version.

MySQL Workbench 6.1

With over 30 new features, this version has many significant enhancements focusing on real-time performance assessment and analysis from the SQL statement level to server internals and file IO. You can see this from additions to the SQL Editor as well as new dashboard visualization and reporting that take advantage of MySQL Server 5.6 and 5.7 Performance Schema, and enhancements to the MySQL Explain Plans.

Additionally Workbench 6.1 is leveraging work from various teammates in MySQL Engineering by introducing a schema called "SYS" that provides simplified views …