Learn when to use MySQL partitioning and why. Get answer to the questions such as:
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 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:
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.
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at firstname.lastname@example.org
For media-related inquiries, contact Maureen Jennings at email@example.com
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).
View a complete list of O'Reilly MySQL Conference contacts.