Ideas, releases, practical guides, and perspectives from the people building with MySQL.
Good bye bzr, welcome git!
After latest releases we moved development of MariaDB Connectors for C, ODBC and Java from launchpad to github.
The connector repositories can be found under https://github.com/MariaDB
Repository-Links:
Feel free to watch, fork and contribute!
Check Out Our Latest Technical Resources for MySQL, MariaDB & MongoDB Clusters
Like every month, we have created new content and tools for you; here is a summary of what we’ve published. Please do check it out and let us know if you have any comments or feedback.
New Live Technical Webinars
A DevOps Guide to Database Infrastructure Automation for eCommerce
Tuesday, February 17th
Infrastructure automation isn’t easy, but it’s not rocket science either, says Riaan Nolan. Automation is a worthwhile investment for retailers serious about eCommerce, but deciding on which tools to invest in can be a confusing …
[Read more]
The next release of MongoDB includes the
ability to select a storage engine, the goal being that different
storage engines will have different capabilities/advantages, and
user's can select the one most beneficial to their particular
use-case. Storage engines are cool. MySQL has
offered them for quite a while. One very big difference between
the MySQL and MongoDB implementations is that in MySQL the user
gets to select a particular storage engine for each table,
whereas in MongoDB it's a choice made at server startup. You get
a single storage engine for everything on the particular mongod
instance. I see pros and cons to each decision, but that's a blog
for another day.
In MongoDB 3.0 …
MySQL Fabric will be used set up a three node High Availability server farm and this is the second part of a series. If you missed the last post, I will be doing a live demo (gulp!) on Fabric for the Triangle MySQL User Group in Raleigh. But part of the pain of live demos is how do you get multiple servers set up to make a server farm. E-I-E-I-oh?
Of course getting the slaves up on one laptop and running
correctly is the biggest expenditure of time for this demo. For
this I will use Vagrant. I am using Vagrant to set up three
identical servers using VirtualBox to provide the servers I need
for the demo. I am using Ubuntu.
sudo apt-get install vagrant VirtualBox
mkdir vagerant
cd vagrant
vagrant box add db1 …
The MySQL grant syntax allows you to specify dynamic database names using the wildcard characters. This article explains the usecase of dynamic section of mysql grants.
The post MySQL grant syntax & dynamic database using wildcards first appeared on Change Is Inevitable.
Today we announced the release of VividCortex Developer edition. You can find the full press release here.
VividCortex’s new Developer service tier makes industry-leading query-level visibility available for no charge.
Baron Schwartz is quoted: “As a technology startup, VividCortex appreciates the value of moving fast. When a small team of smart developers have just founded a business and are searching for product/market fit with a minimal viable product, an excellent tool for database performance management is a must. The last thing you want to do is spend time on burdensome tasks like slow query log analysis. We’re big proponents of the lean startup mindset here at VividCortex, and we’ve benefited greatly from the opensource community, so this is one way we can say thanks.”
To keep costs low and …
[Read more]
UPDATE: I should clarify. This ticket is an internal ticket at
DealNews. It is about what the defaults on our servers should be.
It is not about what the defaults should be in MySQL. The
frustration that UTF8 support in MySQL is only 3 bytes is quite
real.
This epic ticket of the day is brought to you by Joe
Hopkinson.
#7940: Default charset should be utf8mb4
------------------------------------------------------------------------
The RFC for UTF-8 states, AND I QUOTE:
> In UTF-8, characters from the U+0000..U+10FFFF range
(the UTF-16
accessible range) are encoded using sequences of 1 to 4
octets.
What's that? You don't believe me?! Well, you can read it
for yourself
here!
…
Taxonomy upgrade extras: enterprise monitorBackupworkbenchenterprise
MySQL provides some great enterprise features beside the MySQL Server. The ones we are asked the most at customers are:
MySQL Enterprise Backup (MEB)
MySQL Enterprise Backup (MEB) is an
alternative to the mysqldump backup utility. Its big
advantage is its fast backup but even faster …
I’m happy to announce Go packages for MySQL. Particularly exciting is a new query fingerprint function which is very fast and efficient, but I’ll talk about that later. First, go-mysql is currently three simple Go packages for parsing and aggregating MySQL slow logs. If you’ve been following Percona development, you’ve no doubt heard of Percona Cloud Tools (PCT), a somewhat new performance management web service for MySQL.
One tool in PCT is “Query Analytics” which continuously analyzes query metrics from the slow log. The slow log provides the most metrics and therefore the most performance insight into MySQL. percona-agent, the open-source agent for PCT, uses …
[Read more]Last week passed the 5th anniversary of the closing of Oracle's acquisition of MySQL. That also means that the 5 year term of the infamous 10 commitments to MySQL users that Oracle made to the EU commission expire.
Since I work for another database technology nowadays, I have made a point of not blogging about MySQL related issues anymore (and mostly do not follow MySQL close enough to say anything wise). But in 2009 I was so closely involved in the EU investigation into the Oracle-Sun merger, that I feel this is a topic I could write a retrospective on. For nostalgic reasons if nothing else... In any case, these commitments have very little practical relevance in 2015 anyway, so anything in this blog post is clearly more historical than about current state of anything in MySQL land.
