tl;dr: Try it out here: https://preetam.github.io/explain-analyzer/#!/explain/

I introduced my explain analyzer for MySQL a little over a month ago. Here’s what I wrote at the end of that post:

It could look a lot better. The real thing isn’t as nice as the design, and the design is still pretty bad. I’ll work on that soon. In terms of the implementation, the explain analyzer is a single page app without any state, so if you refresh the page, you’ll lose everything. I think I’m going to add a “share” feature so that you can get a permalink with all of the values saved. That’ll take some more work but I think it would be a neat opportunity to use AWS Lambda for a user-facing site!

Both the design and the sharing feature have been addressed with …

tl;dr: Try it out here: https://preetam.github.io/explain-analyzer/#!/explain/

I introduced my explain analyzer for MySQL a little over a month ago. Here’s what I wrote at the end of that post:

It could look a lot better. The real thing isn’t as nice as the design, and the design is still pretty bad. I’ll work on that soon. In terms of the implementation, the explain analyzer is a single page app without any state, so if you refresh the page, you’ll lose everything. I think I’m going to add a “share” feature so that you can get a permalink with all of the values saved. That’ll take some more work but I think it would be a neat opportunity to use AWS Lambda for a user-facing site!

Both the design and the sharing feature have been addressed …

tl;dr: Simple, MIT-licensed, available on GitHub: https://github.com/Preetam/mysqllog

I couldn’t find a simple slow query log parser in Go so I decided to write one. The two I found are:

• Honeycomb’s in Honeytail which is Apache licensed. But it does query text normalization which requires SQL parsing which I don’t need.
• Percona’s in their go-mysql repo. It’s AGPL licensed.

I don’t like how those packages use channels. There’s just too much plumbing required when you have an input channel and an output channel, or a stop channel. With my package you just need to create a parser and feed it slow query log data …

tl;dr: Simple, MIT-licensed, available on GitHub: https://github.com/Preetam/mysqllog

I couldn’t find a simple slow query log parser in Go so I decided to write one. The two I found are:

• Honeycomb’s in Honeytail which is Apache licensed. But it does query text normalization which requires SQL parsing which I don’t need.
• Percona’s in their go-mysql repo. It’s AGPL licensed.

I don’t like how those packages use channels. There’s just too much plumbing required when you have an input channel and an output channel, or a stop channel. With my package you just need to create a parser and feed it slow query log data …

As a Database Administrator(DBA), your job want you to know the most atomic details of databases in your server. It happens for me many times, my boss/ delivery manager asking me, what is the size of a specific database or specific table, in this kind of situation, producing the right data will help make right decision. From my experience, I understood, it is always better to say, I will give you data in few minutes, instead of producing the incorrect data, which I had been doing for a long time.

This post is about identifying the size of a database(s) or table(s).  The simple script, I have been using it for quite a long, if not wrong when I started my career as DBA. You could have probably seen this/similar script on other forums as well and there are many other methods too. I am reproducing this handy script here to get work done.







Size of a specific table: …

The MariaDB project is pleased to announce the availability of MariaDB 10.3.3, the first beta release in the MariaDB 10.3 series, as well as MariaDB Connector/J 2.2.1, the latest stable release in the MariaDB Connector/J 2.2 series, and MariaDB Connector/J 1.7.1, the latest stable release in the MariaDB Connector/J 1.7 series. See the release notes […]

The post MariaDB 10.3.3 and MariaDB Connector/J 2.2.1 and 1.7.1 now available appeared first on MariaDB.org.

In this topic I would like to make some notes about questions, how we can contribute or help on Open Source project.
The first thing is, to learn the product itself, how to install, how to remove, how to use etc.
Of course, the first place for this information is an official documentation.
How you can use the DOC? I am taking following approach:
* Read the doc to learn the needed thing.
* Test the info provided in the DOC –
if the info is valid(i.e you have different results)
continue
if it is not valid:
Report a bug – then continue reading.

The issue can be in DOC itself or in the product.
Did you find small typo in DOC? Did you think some info about topic is wrong? Or maybe you found wrong code samples?
Report it immediately and you will be the part of community.

Let’s take some DOC bug reports and examine them to get the idea.
The first is -> …

The MariaDB project is pleased to announce the availability of MariaDB 10.1.30, the latest stable release in the MariaDB 10.1 series, as well as MariaDB Connector/C 2.3.4, the latest stable release in the MariaDB Connector/C 2.x series. See the release notes and changelogs for details. Download MariaDB 10.1.30 Release Notes Changelog What is MariaDB 10.1? […]

The post MariaDB 10.1.30 and MariaDB Connector/C 2.3.4 now available appeared first on MariaDB.org.

User variables, even though not part of standard SQL, are great objects in MySQL. They allow to keep some “state” for the life of a session: a session can execute a statement to compute a value, store that value in a user variable, and use it in all next  statements.…

Join Percona Chief Evangelist Colin Charles as he covers happenings, gives pointers and provides musings on the open source database community.

I think the biggest news from last week was from cPanel – if you haven’t already read the post, please do – on Being a Good Open Source Community Member: Why we hesitated on MySQL 5.7. cPanel anticipated MariaDB being the eventual replacement for MySQL, based on movements from Red Hat, Wikipedia and Google. The advantage focused on transparency around security disclosure, and the added features/improvements. Today though, “MySQL now consistently matches or outpaces MariaDB when it comes to development and releases, which in turn is increasing the demand on us for providing those upgraded versions of MySQL by our users.” And …