Percona Server

[drtech]

Anyone tried to run Percona Server on linux as a drop-in replacement for MySQL? I am going to try it on a backup server and see if OD connects to it and if there are any performance advantages as they claim. It looks like it has all kinds of advanced features that only MySQL enterprise supports, but in this case, with no cost. I was mainly intrigued by the hot backups, optimization for SSD (at least in 5.6 version) and promise of really fast performance over standard MySQL.

Any thoughts?

http://www.percona.com/software/percona-server/ps-5.6
http://www.percona.com/software/percona ... comparison

[jsalmon]

Does "drop in replacement" mean they use the same framework? the same connector? the same syntax / keywords? I doubt it will just work unless it's like a hybrid version of MySQL that uses MySQL as it's core.
If you go to try it out, I highly recommend you use the MySQL DatabaseType. You might also have to create your own connection string (assuming Percona can even utilize the MySQL connector). I very much doubt it can use the Oracle connector.
If you have to use your own Percona connector it's going to get ugly. You're pretty much going to have to rewrite your own DataConnection class(es) and make sure to import their special Percona.dll (connector). Then you'll have to start looking into making sure all communication going through the DataCore class goes to the new dataconnection class you just wrote?

Then, after the months of programming, you might be able to relish in the .04 milliseconds of increased speed per query that you achieve by switching.

[drtech]

no, i am not writing my own connector, only if it works as a true drop in...I will try it out as a test.

[dqadri]

Wasn't there some mention in the past that Mysql v5.6 was not supported? Was that due to changes in the connector dll?

Percona seems to be a modified fork of the original mysql source code, so I would assume it would drop in. David, I'll help with testing if you want, I'm still working on getting an OD instance setup for production, and one also for development.

Also, I can see how it is easier for OD support to just grab a few files to get the entire database copied over, but it should also be possible with just SQL? Using mysqldump for example?

backup: # mysqldump -u root -p[root_password] [database_name] > dumpfilename.sql
restore:# mysql -u root -p[root_password] [database_name] < dumpfilename.sql

[jsalmon]

Wasn't there some mention in the past that Mysql v5.6 was not supported?

Not supported and won't work are two totally different ball parks. I'd wager that MySQL 5.6 works like a champ. Its got some pretty cool stuff surprisingly enough. However, if there is something wrong we can't make any bug fixes or anything (ergo "support") for you to help you get it to work. We just have too much else to do rather than spend time supporting 5.6 when 5.5 works just fine.

Was that due to changes in the connector dll?

I haven't heard back from anyone even trying 5.6 in the first place so to my knowledge there isn't anything in particular that doesn't work with 5.6

[dqadri]

Got it, I'll try out 5.6 and report back if there are any issues. I just spent the past hour moving my test OD database onto a MacOS mysql v5.5 server without too many problems.