Practical Partitioning With MySQL

Architecture and Technology
Location: Ballroom H
Average rating: ****.
(4.00, 2 ratings)

Learn when to use MySQL partitioning and why. Get answer to the questions such as:

  • Why would I use MySQL partitioning if I do not do Data Warehousing?
  • Can I have too many partitions?
  • Should I use indexes with my partitions?
  • Why would I want to make a unique index non-unique when using partitions?
  • Which partitioning strategy will work best to solve my problem?

While MySQL partitioning can often dramatically improve performance and scaling in many database solutions, in can also cause heartaches and pain if implemented incorrectly. Often a new mindset that focuses more on partitions and less on indexes is needed in designing and implementing a large scale data warehouse. In addition, partitioning can be used in other, non data warehouse solutions, to greatly improve both performance and uptime of common OLTP systems. Implemented wrong, partitioning can cause more problems than it solves, implemented right, it can dramatically improve performance and lower the load on your system.

Brian Miezejewski

MySQL

Brian is a manager in MySQL professional services that still finds time to deliver services to MySQL clients. He currently leads the MySQL PS storage engine and migration practices. He has over 25 years of experience in database design, engineering and usage.

His experience includes:

  • lead architect for the ZFour database system,
  • Senior Principal Architect for the American Airlines enterprise data warehouse,
  • and Director of database systems for Travelweb.com.

While he claims to be mainly a C++/OO architect and developer he has also found time to build several data warehouses up to 12TB in size, design large scale Java/XML based web systems, and work with many of MySQL’s largest users. He has designed, built, and managed database systems on MySQL, Oracle, MS SQL, Informix, and a few other databases nobody remembers anymore. Brian’s hobby is ping pong and trying to grok why Object Relational Databases were never successful.

Comments on this page are now closed.

Comments

Picture of Rick James
Rick James
04/15/2010 3:52pm PDT

Mostly on-target (When to partition), but ran out of time, perhaps because of having too much ‘overview’.

  • Oracle
  • Monty Program
  • Calpont
  • Facebook
  • Gear6
  • Infobright, Inc
  • JasperSoft
  • Joyent
  • Kickfire
  • NorthScale, Inc.
  • Percona
  • Schooner Information Technology
  • Solid Quality Mentors (SolidQ)
  • Intel
  • Pentaho
  • Linux Pro Magazine

Sponsorship Opportunities

For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at yromaine@oreilly.com

Download the O'Reilly MySQL Conference & Expo Sponsor/ Exhibitor Prospectus

Media Partner Opportunities

Download the Media & Promotional Partner Brochure (PDF) for information on trade opportunities with O'Reilly conferences or contact mediapartners@ oreilly.com

Press and Media

For media-related inquiries, contact Maureen Jennings at maureen@oreilly.com

O'Reilly MySQL Conference Newsletter

To stay abreast of conference news and to receive email notification when registration opens, please sign up for the O'Reilly MySQL Conference newsletter (login required).

Contact Us

View a complete list of O'Reilly MySQL Conference contacts.