Uutissyötteet

Planet MySQL

Planet MySQL - http://www.planetmysql.org/

MariaDB 5.1.50 Released
Dear MariaDB users, MariaDB 5.1.50, a branch of the MySQL database which includes all major open source storage engines, myriad bug fixes, and many community patches, has been released. MariaDB: Community developed, feature enhanced, backward compatible. For an overview of what’s new in MariaDB 5.1.42, please see the release notes. Highlights include MariaDB 5.1.50 based on MySQL 5.1.50, includes XtraDB 5.1.49-12, and have some bug fixes in the Aria storage engine. For finer grained details, please view the changelog. MariaDB is available in source and binary form for a variety of platforms and is available from the download pages. Enjoy!
MyQuery 3.3.1 releases - Fixes MyQuery 3.3.0 platform issues
I have released MyQuery 3.3.1 now. This is a minor release in many ways, but still significant in others. MyQuery 3.3.0 had issues on platforms where the runtime library I used wasn't installed. Also, there was a minor (but crashing) bug that caused Ndb Monitor to fail. All this, and a few other minor things, are fixed now.I will eventually blog a bit more on the new features in MyQuery 3.3, such as the plugins, the InnoDB Lock monitor and how to easily define your own monitor dialogs with a simple SELECT statement.Til then, download MyQuery 3.3 from Sourceforge.Cheers/KarlssonAnd by the way, I'm sorry that I failed some QA with version 3.3.0, but it's just me coding away here, and I have a limited amount of machines and above all, time.
Oracle Certified MySQL Certifications
I may no longer be in charge of MySQL Certification but it does not mean I am not looking out for those of us with those certs. I am still moderating the MySQL Certified Professionals Group on LinkedIn and running the North Texas MySQL USers Group. But I missed Oracle University re-branding the Sun certifications as Oracle certifications earlier this month. This includes the MySQL certifications that were re-branded as Sun. And for those wanting to take the certification exams, they retain the Prometric numbers set up by Sun. But you will find them listed as:310-810 - Oracle Certified MySQL 5.0 Database Administrator Part 1 310-811 - Oracle Certified MySQL 5.0 Database Administrator Part 2 310-812 - Oracle Certified MySQL 5.0 Developer Part 1310-813 - Oracle Certified MySQL 5.0 Developer Part 2310-815 - Oracle Certified MySQL 5.1 Cluster Database Administrator310-814 - Oracle Certified MySQL Associate
The best MySQL SSL Cipher?
This is more of a question than me sharing knowledge, but I'm testing the effects of MySQL SSL on replication delay. Interestingly, my tests show faster replication when I enable SSL, versus disable. The slave_compressed_protocol has an effect too, and I get the best result when I use SSL and slave compression in a non-CPU bound test. The question came up, however, of what SSL Cipher I'm using. I'm not specifying one in my CHANGE MASTER statement, so I'm guessing I'm getting the same default cipher as if I connect with the regular mysql command line client with SSL, which is: read more
Easy MySQL: transaction isolation and ACID, the simple explanation
Clients often ask what the differences are between the various InnoDB isolation levels, or what ACID means. Here are some simple explanations for those that have not yet read the manual and committed it to memory. READ UNCOMMITTED Every select operates without locks so you don’t get consistency and might have dirt reads, which are potentially earlier versions of data. So, no ACID support here. READ COMMITTED Has consistent reads without locks. Each consistent read, even within the same transaction, sets and reads its own fresh snapshot. REPEATABLE READ The InnoDB default isolation level for ACID compliance. All reads within the same transaction will be consistent between each other – ie, the C in ACID. All writes will be durable, etc etc. SERIALIZABLE Same as REPEATABLE READ but MySQL converts regular select statements with preface of LOCK IN SHARED MODE when autocommit is enabled. If it’s disabled then each select is started in a separate transaction which will always make sure that reads are consistent. It also, uh, allows for XA distributed transactions support. You have to be using SERIALIZABLE to correctly use XA transactions. =========================================================================== ATOMICITY All transactions fail or no transactions fail. Basically that if a transaction fails because of a hardware issue, connection issue, etc – that partial changes won’t commit. It’s 100% or 0% operation. CONSISTENCY Data being read by a select is all at the same state. So when you use a transaction you’re getting the most current and consistent data available. This is related to MVCC (multi version concurrency control) ISOLATION Nothing that’s being read is actively being changed by another transaction. Your connection or transaction’s read is not going to be changed by another transaction while you’re dealing with that data. DURABILITY Changes to the database persist – basically that means that if a transaction is committed and the DB fails or server crashes your changes will be there – which is why innodb uses transaction log files (where data is kept before being written to disk. The engine will read the logs on next startup and commit any remaining transactions in the logs that did not make to disk based tables.)
Three wishes for a new year
It’s a new year by Jewish calendar (and, incidently, today is the first day of the next 365 days). And what do I wish for in the following year? World peace Good health to all Support for ORDER BY & LIMIT in MySQL multi-table UPDATE and DELETE statements, This is sometimes a real show stopper! Have a good year / next 12 months everyone!
MySQL Connector/Net 6.3.4 GA has been released
We’re proud to announce the next release of MySQL Connector/Net version 6.3.4. This release is GA (Generally Available). We hope you will make MySQL Connector/Net your preferred set of .NET components including our ADO.Net library and other Microsoft .NET frameworks components such as our Visual Studio plugin and Entity Framework for MySQL. We are dedicated to providing the best tools for your MySQL database .NET applications. Special thanks go to all the great MySQL beta testers that provided valuable ideas, insights, and bug reports to the Connector/Net team. Your beta feedback truly helped us improve the product. Version 6.3.4 provides the following new features: - The ability to dynamically enable/disable query analysis at runtime. - Visual Studio 2010 compatibility - Improved compatibility with Visual Studio wizards using our new SQL Server mode - Support for Model-First development using Entity Framework - Nested transaction scopes - Other improvements and bug fixes! For details see http://dev.mysql.com/doc/refman/5.1/en/connector-net-news-6-3-4.html http://dev.mysql.com/doc/refman/5.1/en/connector-net-news-6-3-3.html http://dev.mysql.com/doc/refman/5.1/en/connector-net-news-6-3-2.html http://dev.mysql.com/doc/refman/5.1/en/connector-net-news-6-3-1.html http://dev.mysql.com/doc/refman/5.1/en/connector-net-news-6-3-0.html If you are a current user, we look forward to your feedback on all the new capabilities we are delivering. As always, you will find binaries and source on our download pages. Please get your copy from http://dev.mysql.com/downloads/connector/net/6.3.html To get started quickly, please take a look at our short tutorials. MySQL Connector/NET Tutorials http://dev.mysql.com/doc/refman/5.1/en/connector-net-tutorials.html Blog postings and general information can be found on our Developer Zone site. MySQL Developer Zone http://dev.mysql.com/usingmysql/dotnet/ .NET Forum http://forums.mysql.com/list.php?38 Blog http://planet.mysql.com Connector/NET Documentation and details on changes between releases can be found on these pages http://dev.mysql.com/doc/refman/5.1/en/changes-6.3.x.html http://dev.mysql.com/doc/refman/5.1/en/connector-net.html http://dev.mysql.com/doc/refman/5.1/en/connector-net-news-6-3-4.htm If you need any additional info or help please get in touch with us. Post in our forums or leave comments on our blog pages.
Exploring mk-table-checksum
I recently started exploring the wonders of mk-table-checksum after spending too long dismissing the magic-like maatkit toolkit. What follows is not an exhaustive treatment of mk-table-checksum, but just an overview and some things I had to learn by trying the tool out. The basic principle is based on the CHECKSUM TABLE table maintenance statement supported in the MySQL Server. The mk-table-checksum runs a CHECKSUM TABLE command on all (or some) tables. The results of that are stored in another table on the server. read more
MyQuery 3.3.0 problems about to be fixed.
If you have tested MyQuery 3.3.0 and have problems with a dialog poping up saying that the "application configuration is incorrect", then I am working on this. The reason for this problem is that I now use Visual Stuio 2008 for building, and now Microsoft insists on things such as manifests and stuff. To be frank, insisting on manifests isn't necessarily a bad thing, actually it's pretty cool. The issue is that when there is a problem with them, the messages you get from Windows are, well, less helpful.In the message you get when you try to run MyQuery probably says nothing about the manifest or anything. In my mind, it should. Also, if you link dynamcically with the Microsoft redistributable DLLs, then you want manifests for those also. Ah well. I am working on it anyway.I will move to a new VS 2008 generated project, instead of migrating the old as I did before, and build a new distribution. As far as I can see, this will fix these problems and will also create a better, more clean, project. I'll release a 3.3.1 version later today with these fixes in it./Karlsson
I love my new job!
I just have to chime in about how happy I am with my new job. I now work for Blue Gecko, as of August 30th. My role is a Senior Database and Systems Administrator. Blue Gecko is based out of Seattle though I'll be working out of my home in New Hampshire, albeit with my frequent travels to Seattle for family reasons, this will work out quite well.Already in the last week, I've engaged in several tasks, all of which have been very interesting problems to solve. Not only that, but I've spoken with several existing and potential customers and never realized I really enjoy consulting with and acquiring customers-- hearing what problems they need to solve and being able to ascertain quickly how to solve those problems, making the customer look forward to engaging with us.Who is Blue Gecko?Based out of Seattle, their website states (http://www.bluegecko.net/) "We don't eat, sleep, or go on vacation. We live for three things:* Smooth, uninterrupted database operation for your company* Proactive monitoring for potential problems* Rapid, expert response with no restrictions or delays"We are a remote DBA (Database Administrative) service. We provide a service that would require an organization to have to hire a bunch of DBAs and even sysadmins. We provide this for Oracle, MySQL, and recently PostgreSQL and SQL Server. Just from my first week here, there are some top-notch people that I'm already enjoying working with.Some of the tasks I've worked on:* Restoring data that a developer accidentally truncated from tables using InnoDB Tools (http://code.google.com/p/innodb-tools/). I hadn't done this before, and it was fantastic to be able to restore that data in such a dire situation* Optimizing a query and ultimately how the data is stored in a table for a query that used a file sort that would be extremely slow unless you forced use of the index that the order by was using. The teaser was that EXPLAIN would show a full-table scan if the force index was used. This was a good exercise in understanding the buffer pool as well as how InnoDB works with indexes.* Crawling through a schema with a bunch of tables and finding many optimizations* Discussing deployment of The Sphinx Search Engine for a client who needs search functionality* Various Perl questions from one of my Co-workers. I was able to send the code that I wrote for my book to help them solve a problem. I felt great being able to help someone so soon after starting a new jobThe thing that has really dawned on me is that I prefer working on components within the LAMP stack, especially MySQL, with an eye on where NoSQL fits in as well. I just wanted to write about my realization that I've had over the last several days!