Yesterday, it was announced that SkySQL has raised an additional 2.5 million dollars in Series A funding from California Technology Ventures.
This comes along with the news of the new CEO, Patrik Sallner, taking the CEO role at SkySQL on July 1st.
Here are some relevant snippets:
“SkySQL also announced today that CTV, a venture capital fund that makes direct investments in technology and life science companies globally, invested an additional $2.5 million as part of the company’s recent A round of funding. With this latest investment, SkySQL has collected EUR 6 million to fund further growth.”
“About California Technology Ventures, LLC
California Technology Ventures, LLC is a venture capital fund that makes direct investments in technology and life science companies. CTV has built a strong reputation for its entrepreneurial approach to investing and working with companies. They believe in guiding entrepreneurs through the strategic, operational, and management decisions critical to a company’s success. For more information, please view www.CTVentures.com.”
If interested, there are much more details on this round of funding here:
In case you may have overlooked yesterday’s post from Ulf Sandberg, I thought I’d go ahead and reiterate the main points, as it is big news, at least for those interested in SkySQL.
SkySQL has been like a rocket ship with it’s growth since we started, and now we’re making some even bigger changes to help accelerate that effort further.
As Ulf announced, we’ve named a new CEO, Patrik Sallner, to take over after the initial bootstrap period.
Patrik, a former executive at F-Secure, will officially become CEO on July 1st. “Patrik comes to SkySQL with demonstrated experience in building international software and services businesses, including delivering cloud storage solutions to the world’s largest telecommunications operators. The addition of Patrik to SkySQL’s Leadership Team is a tremendous boon to the company, and I have every confidence that he will be instrumental in catapulting SkySQL to the next level.”
Again, I just wanted to share the news for those who may have missed it.
For those interested, more on this can be found here:
Last week was full of exciting news for all things MySQL.
However, SkySQL also had some great individual news in that it announced 2 new partners:
I just wanted to take a moment and officially welcome both to the SkySQL fold!
PalominoDB and hastexo, it’s great to be partnered with you!
And we’re looking forward to all the exciting things the future has to hold! 🙂
For those interested, you can read more about each partnership here:
SkySQL & hastexo Partnership Press Release
SkySQL & PalominoDB Partnership Press Release
Well, as you or may not have heard, MariaDB 5.5 (5.5.23) was declared GA last week!
It was only about 6-ish weeks ago that MariaDB 5.5 had been released as alpha, so the fact it’s already GA is excellent news for all MariaDB users (and MySQL 5.5 users looking to migrate).
Some of the 5.5 enhancements include:
- Significantly more efficient thread pool, comparable in functionality to the closed source feature in MySQL Enterprise.
- Non-blocking client API Library (MWL#192)
- @@skip_replication option (MWL#234)
- SphinxSE updated to version 2.0.4.
- “extended keys” support for XtraDB and InnoDB
- New INSTALL SONAME statement
- New LIMIT ROWS EXAMINED optimization.
- mysql_real_connect() Changes
In MySQL, and in MariaDB versions before 5.5.21, mysql_real_connect() removes from the MYSQL object any options set with mysql_option() when it fails. Beginning with MariaDB 5.5.21, options are preserved by a failing mysql_real_connect(); use mysql_close(), as normal, to clear them.
This only has effect if the MYSQL object is reused after a mysql_real_connect() failure (which is unusual). No real-life incompatibilities are expected from this change (it is unlikely that an application would rely on options being automatically removed between connection attempts).
- The variables replicate_do_*, replicate_ignore_*, and replicate_wild_* have been made dynamic, so they can be changed without requiring a server restart. See Dynamic Replication Variables for more information.
- Updates to performance schema tables are not stored in binary log and thus not replicated to slaves. This is to ensure that monitoring of the master will not cause a slower performance on all slaves. This also fixes a crash on the slaves.
Here is the official “What is MariaDB 5.5” page:
Also of interest:
And as always, if you’d like full support for MariaDB, just contact us at SkySQL.
Hope this helps.
As some of you already know, I too have recently left the MySQL Support Team at Oracle.
However, I am happy to report that I have joined SkySQL!
So I’ll remain in the MySQL Community, and will still be providing support for MySQL. 🙂
I am grateful to everyone I’ve worked with and to everyone who has had a hand in improving MySQL (no matter how small or large) over the years! It’s been a blast working with such dedicated and passionate people, and I look forward to many more years of the same now at SkySQL! 🙂