There is a new MySQL Users Group in the United Kingdom for those in the Bristol area. On Thursday August 14th be sure to be at the Watershed on 1 Conon’s Road at 7PM. A big thanks to Andrew Moore and Ben Mildren for organizing this group.

Looking for a MySQL User Group in your area? Let me know if you do not have a group in your area and wish to start one as I can help get swag, meeting locations, and speakers.

I’ve often wished that PROCESSLIST exposed when a connection was first established, and I find myself wishing for this information more now with MySQL 5.6.  Improvements to PERFORMANCE_SCHEMA make it trivial to see how much time is being spent in various operations for a given connection – but it would make some analysis (“what percentage of connection time is spent doing X?”) easier.

That said, it is possible to approximate connection age with PERFORMANCE_SCHEMA in MySQL 5.6.  I say “approximate” because results will vary based on what instrumentation exists, is enabled, and is collecting timing data.  That’s because we’re just doing a SUM() on the SUM_TIMER_WAIT column for all instrumented waits.  Here’s an example (FYI, I’m using the format_time() function from Mark Leith’s …

This is part 3 of a 3 part series covering the new InnoDB full-text search features in MySQL 5.6. To catch up on the previous parts, see part 1 or part 2

Some of you may recall a few months ago that I promised a third part in my InnoDB full-text search (FTS) series, in which I’d actually take a look at the performance of InnoDB FTS in MySQL 5.6 versus traditional MyISAM FTS. I hadn’t planned on quite such a gap between part 2 and part 3, but as they say, better late than never. Recall that we have been working with two data sets, one which I call SEO (8000-keyword-stuffed web pages) and the other which I call DIR (800K directory records), and we are comparing MyISAM FTS in …

In a previous post, I described how to leverage PERFORMANCE_SCHEMA in MySQL 5.6 to identify connections which had not been properly closed by the client.  One possible cause of connections being closed without explicit request from the client is when another process issues a KILL CONNECTION command:

mysql> SHOW GLOBAL STATUS LIKE 'aborted_clients';
+-----------------+-------+
| Variable_name   | Value |
+-----------------+-------+
| Aborted_clients | 0     |
+-----------------+-------+
1 row in set (0.02 sec)

mysql> KILL CONNECTION 3;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW GLOBAL STATUS LIKE 'aborted_clients';
+-----------------+-------+
| Variable_name   | Value |
+-----------------+-------+
| Aborted_clients | 1     |
+-----------------+-------+
1 row in set (0.00 sec)

You …

Installing Nginx With PHP5 (And PHP-FPM) And MySQL Support On Fedora 19

Nginx (pronounced "engine x") is a free, open-source, high-performance HTTP server. Nginx is known for its stability, rich feature set, simple configuration, and low resource consumption. This tutorial shows how you can install Nginx on a Fedora 19 server with PHP5 support (through PHP-FPM) and MySQL support.

The new Percona Server 5.6 is the most manageable, highest performance, and most scalable version of MySQL available. Percona Server 5.6 is the best open source MySQL choice for enterprise-grade applications because it combines new features with the best features of Percona Server 5.5 and MySQL 5.6 to provide unparalleled performance.

Join me tomorrow as I explain how Percona Server 5.6 takes MySQL performance to new heights. In this webinar, aptly titled “Percona Server 5.6: Enterprise Grade MySQL,” I’ll compare Percona Server 5.6 to …

This article is part of a series. You might also like: 10 More Common Mistakes Java Developers Make when Writing SQLYet Another 10 Common Mistakes Java Developers Make When Writing SQL Java developers mix object-oriented thinking with imperative thinking, depending on their levels of: Skill (anyone can code imperatively)Dogma (some use the "Pattern-Pattern", i.e. the … Continue reading 10 Common Mistakes Java Developers Make when Writing SQL →

Peter Zaitsev speaks at the Percona Live MySQL Conference and Expo in Santa Clara, Calif. in April 2013.

In the MySQL ecosystem, there is some sort of conference or another all year long. But why are they important?

To answer this, we can split the audience into 3 groups:

- MySQL Professionnals
- MySQL Community Members
- MySQL (Future?) Users

Depending on which category you are in, you can have different expectations about conferences.

For MySQL Professionals, it’s the best opportunity to meet partners, customers and also other business players in real life – and this is a very important point. As most of our contact with customers is virtual, meeting people and discussing things with them in person is very beneficial for future collaboration. This is also …

Recently, we inquired: “What is your main security and compliance concern for your MySQL database?”

The results:

• Prevent access to sensitive data: 39.3%
• SQL injection attacks: 28.3%
• Regulatory compliance: 20.3%
• Block unauthorized external users: 9.2%
• Block unauthorized internal users: 2.9%

This survey shows some positive trends. Looks like the general IT public has embraced the concept that protecting sensitive information is absolutely essential. One fifth of respondents are driven by the need to comply with increasing governmental regulations, so legal hassles are as worrisome as corporate reputation for many. Whatever the reason, people are becoming more aware and vigilant about security concerns. Separation of duties via establishing levels of access is a key factor in securing sensitive data. Dynamic data masking is an …

One optimization that I’ve employed several times involves batching write queries. MySQL has some very efficient ways to load multiple rows of data in a single query. Multi-row inserts are one common way to do it, but if you’re adventurous you can also try using LOAD DATA INFILE. Multi-row inserts are just what you would [...]