We have an exciting webinar coming up tomorrow (12/15) on migrating from SQL Server to MySQL.  LiveTime Software is a leader in ITIL service management and help desk products.  They have started offering a free migration service and this webinar will go over everything from toolsets used to character sets. 

You can read more about it and register for this webinar here.  So I know you have an hour you can spare and when it comes time to renew that SQL Server license you’ll be glad you did.

I'm pleased to announce the release of Spider storage engine version 2.10(beta).
Spider is a Storage Engine for database sharding.
http://spiderformysql.com/

The main changes in this version are following.
- Add table parameter "ssl_ca", "ssl_capath", "ssl_cert", "ssl_cipher", "ssl_key", "ssl_verify_server_cert", "default_file" and "default_group".
- Add UDF parameter "ssl_ca", "ssl_capath", "ssl_cert", "ssl_cipher", "ssl_key", "ssl_verify_server_cert", "default_file" and "default_group".
You can use ssl for Spider's communication to remote servers.
Spider can read config file(my.cnf) at connecting to remote servers.

Please see "99_change_logs.txt" in the download documents for checking other changes.
Thanks to Shinya for bug report.

Enjoy!

One of MySQL’s notable projects was splitting the product into two editions: Enterprise Edition and Community Edition. This move alienated many in the community, and failed to create meaningful differentiation on either side, even with a team of people beating the community bushes for “contributions.” The net differentiation was ultimately Jeremy Cole’s SHOW PROFILES functionality, which made Community better than Enterprise. Sun put less effort into making this split work, and eventually they abandoned it.

But that could change under Oracle’s stewardship. Oracle’s promises to maintain a GPL …

Following talks with European regulators regarding its planned Sun takeover, Oracle makes 10 commitments to help keep MySQL a competitive database product.

MySQL Cluster Connector for Java is a new feature in the upcoming Cluster 7.1.

It is an easy to use, high-performance Java and JPA interface for MySQL Cluster. We currently call it simply Cluster/J and Cluster/JPA. It is an Objection Relational bridge that maps Java classes to tables stored in MySQL Cluster, and implements an OpenJPA interface.

How does it work?

The new MySQL Cluster Connector for Java and JPA implementation consist of two parts: an OpenJPA plugin and the standalone Cluster/J API.
The standalone Cluster/J API allows you to write very simple Java programs for MySQL Cluster. A read by primary key is then as easy as

Fish e = session.find(Fish.class, 4711);

A query like the above is executed without using the MySQL Server. Cluster/J API is a native MySQL Cluster-specific API, which is a direct access path to Cluster which is very simple to …

What many people don't get is that Monty's appeal to the MySQL community to help save MySQL is really quite selfless.

The fact is, Monty's own company, Monty Program Ab, stands to benefit the most from bad stewardship of MySQL by Oracle.

If Oracle slows and closes up development, rejects community contributions and creates a commercial version of MySQL, then Monty Program's MariaDB fork will become very popular, very quickly.

Which would translate into income for Monty Program Ab as customers come to his company for additions, features and bug fixes that they need to secure there own production.

What Monty is concerned about is the commercial vendors of MySQL (one of which …

Oracle’s proposed acquisition of Sun Microsystems looks set for approval by the European Commission after the competition commission welcomed commitments from Oracle related to the future development and licensing of the open source MySQL database.

The EC has until January 27, 2010, to reach a final decision however it appears that significant progress has been made following hearings in Brussels last week where Oracle made its case for approving the acquisition and opponents including SAP, Microsoft and Monty Program AB argued against the proposed acquisition.

Oracle has published a list of ten commitments that it is prepared to make to assuage the EC’s concerns over the future of MySQL, which were quickly and enthusiastically welcomed by the European Commission.

Oracle’s commitments …

You’ve probably seen Monty’s post Help Saving MySQL. This is about

1. Development (will Oracle put significant effort into MySQL, actually innovating)
2. Brand (”MySQL” has a huge footprint), the trademark owner can enforce this – there have already been issues with companies offering MySQL related services via Google AdWords not being able to use the word MySQL in their ad text even though it was correctly used as an adjective.
3. Forking is fine, but still has to deal with the branding. For MySQL, that’s possibly the most significant issue of any OSS product ever encountered. You’re not competing against a company, but against an existing brand footprint that you (because of the trademark) have to steer clear of. So “just fork it” is not an easy or short term option, there’s more involved than …

And I looked back and thought of updating this post… We all are aware about the acquisition happened to MySQL; Sun and now Oracle. A common understanding tells me that…

The post Monty: Help Saving MySQL – The Oracle & EC first appeared on Change Is Inevitable.

The chart shows benchmark results taken using sysbench.  Rough understanding would be that (for this scenario) the performance ratio is HDD:SSD:in-memory = 1:10:50.

Details:

The benchmark was taken using MySQL 5.1.41 using innodb_plugin running on linux 2.6.31/x86_64 (Ubuntu 9.10 server).  Options passed to sysbench were: --test=oltp --db-driver=mysql --mysql-table-engine=innodb …