Features, Features, Features!!! Everybody wants more, but what's involved in getting those features deployed in a real production environment, and what are the pitfalls? Upgrading MySQL versions has been more involved than a simple binary upgrade for LiveWorld.

Views, Triggers, Stored Procedures, Subqueries, Prepared Statements, Character Sets, innodb_file_per_table, and more--did you need to rebuild your databases to get to 4.1 and are scared of doing it again to get to 5.0? What will happen when I want to move to 5.1?

With software developers screaming for access to new MySQL features, and operations staff pleading for stability and caution, what can we learn from LiveWorld's experiences in migrating from MySQL 4.0 to 4.1 and on to 5.0? What do the Character Set changes really mean? What exactly are character sets? Do I need to convert my data? What is the best way to do that? How can I avoid those incredibly large InnoDB shared Table Space files?

Join LiveWorld's Bruce Dembecki as he looks at the lessons learned from upgrading MySQL to serve the needs of their discussion board clients. With over 100 million dynamic page views each month, LiveWorld has 100 products deployed in 20 languages for 35 countries, serving clients such as AOL, eBay, HBO, QVC, Warner Brothers, Expedia, Hotels.com, Intuit, A&E TV, and many more.