In our last post, Bradley described how auto increment works in TokuDB. In this post, I explain one of our implementation’s big benefits, the ability to combine better primary keys with clustered primary keys.

In working with customers, the following scenario has come up frequently. The user has data that is streamed into the table, in order of time. The table will have a primary key that is an auto increment field, ‘id’, and then have an index on the field ‘time’. The queries the user does are all on some range of time (e.g. select sum(clicks) from foo where time > date ‘2008-12-19′ and time < date '2008-14-20';).

For storage engines with clustered primary keys (such as TokuDB and InnoDB), having such a schema hurts query performance. Queries do a range query on a secondary index (time), and then perform point queries …

Most wished by HeidiSQL users: having more than one query tab. Just implemented that, trying to adapt most nice tabbed interface details:
* Create new tab with Ctrl+T or by doubleclicking the empty tab space
* Close tab either by clicking a close button or with Ctrl+F4




Not the newest one, but also not in the recent 4.0 final yet: A completely rewritten editor for table structures. Replaces various legacy dialogs in one powerful GUI, with even more functions than before:
* In-memory editing until you press "Save"
* Grid like editing of all column properties
* Advanced table options gathered on a seperate tabsheet
* CREATE and ALTER code for preview and copy+paste purposes



Give it a try and download a …

In our last post, Bradley described how auto increment works in TokuDB. In this post, I explain one of our implementation’s big benefits, the ability to combine better primary keys with clustered primary keys.

In working with customers, the following scenario has come up frequently. The user has data that is streamed into the table, in order of time. The table will have a primary key that is an auto increment field, ‘id’, and then have an index on the field ‘time’. The queries the user does are all on some range of time (e.g. select sum(clicks) from foo where time > date ‘2008-12-19’ and time < date '2008-14-20';).

For storage engines with clustered primary keys (such as TokuDB and InnoDB), having such a schema hurts query performance. Queries do a range query on a secondary index (time), and then perform point …

Jan Wildeboer pointed us to the Mayflower post about their letter from the European Commission.

It seems like the the European Commision , more specifically the Directorate General for Competition , really is interested in our input regarding the matter, I mailed them and also got a questionnaire to fill in.

So if you have something interesting to tell them don't hesitate to contact them too.

Technorati Tags: eu mysql orace …

Some news about a change in my career path that I've been meaning to announce. I now have moved on from Lycos and now work for NorthScale Inc!

In parting Lycos, I'd like to thank them for the great challenges I had while there. I designed and developed, along with my team members in the web publishing and support from the OPs group, PHP offerings for Tripod users, a long-awaited feature that premium users can use to install numerous PHP applications. Also, with that was a great interface I developed for installing applications. It required some work on the applications themselves to make them as easy to install as possible (similar to APS). The other task while there was to switch Tripod and Angelfire blogs from Oracle to MySQL. Thank you Lycos -- It was a pleasure working with all of you!

Now, I'm excited to announce I'm working with NorthScale. This is a great team of people -- including Dustin Sallings, Steve Yen, …

Asynchronous Replication for High Availability

MySQL replication is often positioned as a solution to provide extra throughput for your database (especially when dealing with high numbers of read operations). What tends to be overlooked is how it can be used to provide high availability (HA) – no matter how much redundancy you have at a local level, your system remains at risk from a single catastrophic failure – loss of power, earthquake, terrorist attack etc. By using MySQL asynchronous replication to maintain a geographically remote copy of that data, service can be maintained through any single site failure.

As this replication is asynchronous, there are no low latency demands on the network and so the two sites can be thousands of miles apart while utilising low-cost connections.

This article …

Departmental or subject-specific data warehouses – known as “data marts” in the industry – seem to be gaining in popularity.  Fueled partly by companies wanting to start small with focused projects in today’s economy, and partly by advances in data warehousing technology improving affordability and deployability, data marts seem to be popping-up everywhere.

In most cases, data mart projects are driven by the head of a business unit or a functional group (like Sales) needing to analyze their own slice of data in order to run their department more efficiently and effectively.  The data may come directly from an operational system or a combination of source systems resulting in what’s called an “independent data mart”, or it may come directly from a larger, enterprise data warehouse in a hub-and-spoke or “dependent data mart” configuration.

In either case today, according to industry analysts, companies …

270 folks took MySQL Certification exams in July and 118 earned certifications. This is our best month outside of our annual Users Conference. For the fiscal year, MySQL Certifications were up 150.27% over the previous year.

Since the program inception, we had almost 8,000 exams taken and over 3,300 certifications. Not bad but it pales in comparison to Java exams and certifications.

Prometric is our new testing partner. Those of you with unexpired Pearson VUE vouchers can request a exchange by contacting Certification@sun.com with your Voucher ID number. And those of you wishing to sign up for the exams (they are part of the Sun 310-series at http://www.prometric.com/Sun/default.htm) need to contact you local Sun sales office to purchase a voucher.

And the North Texas MySQL Users Group meets tonight -- see http://www.northtexasmysql.org for details.

Mat Keep and I will be presenting a Webinar on Wednesday, August 12, 2009 describing the new capabilities of MySQL Cluster 7.0. The time is designed to be Asia/Australasia-friendly but of course it’s open to everyone.

Register for the MySQL Cluster 7 Webinar here.

By attending this webinar, you will learn more about the next generation of MySQL Cluster, and how it enables you to deliver 99.999% database availability, with real time performance and linear scalability, while slashing TCO.

Boasting a range of breakthrough capabilities, MySQL Cluster 7.0 will enable you to stay ahead of your most demanding, mission-critical application requirements. Enhanced scalability delivers higher database performance with fewer nodes to simplify deployment and administration. Expanded platform support and interoperability delivers more …

Departmental or subject-specific data warehouses - known as "data marts" in the industry - seem to be gaining in popularity.  Fueled partly by companies wanting to start small with focused projects in today's economy, and partly by advances in data warehousing technology improving affordability and deployability, data marts seem to be popping-up everywhere.

In most cases, data mart projects are driven by the head of a business unit or a functional group (like Sales) needing to analyze their own slice of data in order to run their department more efficiently and effectively.  The data may come directly from an operational system or a combination of source systems resulting in what's called an "independent data mart", or it may come directly from a larger, enterprise data warehouse in a hub-and-spoke or "dependent data mart" configuration.

In either case today, according to industry analysts, companies are looking for data …