Many MySQL users also use the Oracle database and other associated Oracle software. Oracle is integrating MySQL with many of its other software products. The Oracle product certifications and integrations will allow you to use a common set of tools for Oracle and MySQL databases as a data source or as a metadata repository using the same software. Some products have already been integrated, and others are in the works.The products I will cover include Oracle Goldengate, Secure Backup, Audit Vault, OVM, and Firewall as well as some middleware products.
A unique selling point of MySQL is that is supports multiple storage engines, which basically means users get to use the same top-level SQL interface while storing their data in many different sorts of methods. However as these are benefits they also come with some trade-off's and we discuss some (and point to solutions): * transaction support - not all storage engines support transactions, and storage engines that do use different locking strategies, so cross-storage engine transactions are always interesting. Do you choose a transactional engine for your workload? When is it right to use a non-transactional engine like MyISAM? * backup - cross-storage engine backup does not work unless you use OS-level approaches like LVM/ZFS snapshots. In-memory engines will naturally not allow snapshots to work. How do you backup across engines? * replication for different storage engines differ in the sense that we already write a second binlog, despite transactional engines having their existing one. How do you replicate when you have a mix of engines? * how do you monitor when you have several engines? What resources do you allocate to each in the configuration? * how does the optimiser deal with all the different storage engines? Today in MySQL 5.5 and greater, InnoDB is the default storage engine. It has spawned two large forks - XtraDB and HailDB (for Drizzle). Previously, MyISAM was the default storage engine. MySQL by default ships with about a dozen engines, and other branches like MariaDB ship with close to twenty. Naturally we'll cover cool tricks you can do with storage engines. For example, how you can make good use of the Spider storage engine for vertical partitioning? When do you use the Archive storage engine to store log tables? When do you use the Federated tables to get different views or execute remote commands? How do you use the Blackhole engine for replication relay despite an engine that really is the equivalent of /dev/null in Unix? We will go through the entire landscape, including the commercial landscape, and show you what engine is correct for your use-case. If you're a developer, you will benefit from learning about the extended storage engine API, in MariaDB which for starters supports an extended CREATE TABLE functionality.
MariaDB is a branch of the popular MySQL database. The project began in 2009 circled around a storage engine, but quickly evolved to being another database, with two major releases in 2010. MariaDB is community developed, feature enhanced and backward compatible with MySQL.
This session will introduce the project, and will help a DBA or developer come to grips with MariaDB.
MySQL® Cluster is a separate product from the standard MySQL database, despite their being tightly linked. Due to the distributed nature of MySQL Cluster, it has a far more complicated architecture than a standard MySQL database. In this presentation, Max Mether, SkySQL's Training Services Manager, will describe the architecture of the MySQL Cluster product and how the process and data flow takes place between the nodes of the cluster.
MySQL Replication is a native feature of MySQL. This session will give a broad overview of replication within MySQL as well as a simple real world configuration example to get you started. We will then continue with a more in-depth investigation of the MySQL Replication Features in MySQL 5.6.
- MySQL Replication Overview
- Replication Configuration
- --- Examples of a Real World Setup
- MySQL 5.6 Replication Features
- Replication Monitoring
MySQL has added several new features with the 5.5 release and the 5.6 previews. This session is an over view of the new features and how they can best be utilized. New features in replication, InnoDB, plug-in authentication, connection pooling, enterprise tools, performance, and NoSQL access of data will be included. This session is intended for all levels of attendees. This will cover changes and updates to the MySQL database server, data connectors, enterprise tools, MySQL cluster, Workbench, and more. The new features of the preview releases will be details to help the community prepare for new features being developed.