The document outlines changes and new features in MySQL versions 5.7 through upcoming releases. Key points include:
- MySQL 5.7 development follows a milestone release process to stabilize new features before general availability. Four development milestone releases have been completed so far.
- Notable 5.7 features include statement timeouts, change replication without stopping SQL threads, and performance improvements like optimized UNION ALL queries.
- Some existing functionality will change in 5.7, like making replication more durable by default and producing errors for queries with only partial GROUP BY clauses.
- Ongoing efforts include refactoring and improving InnoDB, the optimizer, and other components for better performance and scalability. New features in development
The document discusses NoSQL APIs in MySQL. It provides an overview of the memcached caching system and the history of the HandlerSocket protocol. It then describes the NoSQL interface introduced in MySQL 5.6, which allows for memcached-style operations on MySQL data. It notes that MySQL 5.7 further improved the performance and scalability of this interface.
MySQL 5.7 introduced native support for JSON data with a new JSON data type and JSON functions. The JSON type allows efficient storage and access of JSON documents compared to traditional text storage. JSON functions allow querying and manipulating JSON data through operations like extraction, search, and generation of JSON values. Developers now have more flexibility to work with hierarchical and unstructured data directly in MySQL.
MySQL 5.7 proposes several changes to improve performance and consistency including:
1. Making replication durable by default by setting sync_binlog and repository options.
2. Deprecating features like INNODB monitor tables and ALTER IGNORE TABLE in favor of newer standards.
3. Simplifying and restricting SQL modes to encourage stricter querying and remove ambiguous options. Explanations for errors and modes will also be improved.
Tanel Poder - Performance stories from Exadata MigrationsTanel Poder
Tanel Poder has been involved in a number of Exadata migration projects since its introduction, mostly in the area of performance ensurance, troubleshooting and capacity planning.
These slides, originally presented at UKOUG in 2010, cover some of the most interesting challenges, surprises and lessons learnt from planning and executing large Oracle database migrations to Exadata v2 platform.
This material is not just repeating the marketing material or Oracle's official whitepapers.
This document discusses moving data between Oracle Exadata and Hadoop for fast loading. It begins by introducing Oracle SQL Connector for HDFS, which allows querying Hadoop data using Oracle SQL and external tables. However, initial tests of loading 1TB of data showed slow speeds of only 75MB/second due to bottlenecks. Subsequent tests revealed the bottleneck was datatype conversion CPU usage on the Oracle side. The document then introduces Oracle Loader for Hadoop, which offloads datatype conversion to Hadoop cluster CPUs, allowing much faster loading of over 1GB/second by leveraging all available CPUs. Proper partitioning is also required for direct path loads to avoid contention.
The document provides an overview of the InnoDB storage engine used in MySQL. It discusses InnoDB's architecture including the buffer pool, log files, and indexing structure using B-trees. The buffer pool acts as an in-memory cache for table data and indexes. Log files are used to support ACID transactions and enable crash recovery. InnoDB uses B-trees to store both data and indexes, with rows of variable length stored within pages.
MySQL: From Single Instance to Big DataMorgan Tocker
The document discusses various MySQL database architectures for different usage needs, from single server setups to high availability configurations. It begins with traditional single server and web/database tier setups. It then covers high availability options using MySQL replication, shared storage, and MySQL Cluster. Popular topologies include master-slave replication for scaling reads, read-write splitting between master and slaves, and using slaves for reporting queries to improve performance. Considerations like network latency, failure handling, and limitations of read-write splitting are also discussed.
Oracle Exadata Performance: Latest Improvements and Less Known FeaturesTanel Poder
This document discusses recent improvements to Oracle Exadata performance, including improved SQL monitoring in Oracle 12c, enhancements to storage indexes and flash caching, and additional metrics available in AWR. It provides details on new execution plan line level metrics in SQL monitoring reports and metrics for storage cell components now visible in AWR. The post outlines various flash cache features and behavior in earlier Oracle releases.
The document discusses locking and concurrency control in databases, demonstrating how table locks, row locks, and multi-version concurrency control work through examples of a database being backed up while concurrent changes are made. It shows how different locking strategies, like those used in MyISAM and InnoDB, allow for concurrent access to data while maintaining consistency and isolation. A live demo then highlights deadlocks and lock waits that can occur with concurrent access and how they are handled.
Tanel Poder Oracle Scripts and Tools (2010)Tanel Poder
Tanel Poder's Oracle Performance and Troubleshooting Scripts & Tools presentation initially presented at Hotsos Symposium Training Day back in year 2010
This document discusses MySQL performance tuning and various MySQL products and features. It provides information on MySQL 5.6 including improved scalability, new InnoDB features for NoSQL access, and an improved optimizer. It also discusses MySQL Enterprise Monitor for performance monitoring, and the Performance Schema for instrumentation and monitoring internal operations.
This document discusses InnoDB tablespace encryption in MySQL. It begins with prerequisites for encryption like having MySQL 5.7 installed and the keyring plugin configured. It then covers how to encrypt existing and new tables. The architecture uses a two-tier encryption model with a master key and tablespace keys. Key rotation only re-encrypts tablespace keys. Exporting encrypted tables requires additional files. Replication requires different keyring files on master and slave. MySQL Enterprise Edition supports transparent data encryption using the Oracle Key Vault for strong key protection and management.
The document discusses new features and improvements in MySQL 5.6, including significant performance gains over MySQL 5.5. Key highlights include improved InnoDB performance through features like online DDL and buffer pool pre-loading, up to 151-234% performance gains on benchmarks. Other enhancements cover full-text search in InnoDB, NoSQL support through memcached integration, replication improvements with GTIDs and crash-safe slaves, and strengthened security with audit logging and password policies.
Troubleshooting Complex Performance issues - Oracle SEG$ contentionTanel Poder
From Tanel Poder's Troubleshooting Complex Performance Issues series - an example of Oracle SEG$ internal segment contention due to some direct path insert activity.
Query Optimization with MySQL 5.7 and MariaDB 10: Even newer tricksJaime Crespo
Tutorial delivered at Percona Live London 2014, where we explore new features and techniques for faster queries with MySQL 5.6 and 5.7 and MariaDB 10, including the newest options in MySQL 5.7.5 and MariaDB 10.1.
Download here the virtual machine with the example database: http://dbahire.com/pluk14
Update: WordPress has a workaround for STRICT mode: https://core.trac.wordpress.org/ticket/26847
MySQL 5.7 - What's new and How to upgradeAbel Flórez
The document discusses new features in MySQL 5.7, including:
1) Performance improvements such as being 3x faster than MySQL 5.6 for certain workloads based on sysbench benchmarks.
2) Optimizer enhancements like a new cost-based optimizer model for better query performance and resource usage.
3) Additional features like native JSON support with functions to create, search, modify and return JSON values and improved security.
MySQL® 5.7 is a great release which has a lot to offer, especially in the development and replication areas. It provides a lot of new optimizer features for developers to take advantage of, a much more powerful GIS function and high performance JSON data type, allowing for a more powerful store for semi-structured data. It also features dramatically improved Performance Schema, Parallel and Multi-Source replication, allowing you to scale much further than ever before, just to give you a taste. In this webinar, we will provide an overview of the most important MySQL 5.7 features.
This webinar will be part of a 3-part series which will include MySQL 5.7 for Developers and MySQL 5.7 for DBAs.
Query optimization: from 0 to 10 (and up to 5.7)Jaime Crespo
This document provides an agenda and introduction for a presentation titled "Query Optimization: From 0 to 10 (and up to 5.7)". The presentation covers various topics related to query optimization in MySQL/MariaDB versions 5.5-5.7 and 10.1 such as access types and indexing techniques, multi-column indexing, joins, subqueries, query profiling, optimizer improvements and hints. Example databases from Wiktionary and OpenStreetMap are used to demonstrate the concepts.
This document discusses various MySQL performance metrics that are important to measure from within the database, operating system, and application. It outlines key InnoDB internal structures like the buffer pool and log system. Specific metrics that provide insight into buffer pool usage, page churn, and log writes are highlighted. Optimizing the working set size and ensuring sufficient free space in the log files are important factors for performance.
The document discusses Oracle's MySQL Cloud Service which provides MySQL as a database service on Oracle Public Cloud. Key features include automated backups, patching, monitoring, elastic scaling, high availability, security features from MySQL Enterprise Edition, and tools for data access, migration and restoration. The service runs MySQL 5.7 Enterprise Edition with an optimized configuration for the cloud environment.
The document discusses MySQL architecture and concepts. It describes the application layer where users interact with the MySQL database. It then explains the logical layer which includes subsystems like the query processor, transaction management, recovery management and storage management that work together to process requests. Key concepts like concurrency control, locks, transactions, storage engines and InnoDB/MyISAM are also overviewed.
The document provides an overview of diagnosing performance and other issues with the InnoDB storage engine in MySQL. It discusses various sources of information for troubleshooting like SHOW ENGINE INNODB STATUS and OS tools. Common problems covered include the InnoDB data dictionary getting out of sync, crashes/segmentation faults, locking issues, and performance problems related to disk I/O, buffer pool hit rates, high CPU usage from row operations or thread thrashing. Interpreting diagnostic output and potential solutions are also outlined.
Linux con europe_2014_full_system_rollback_btrfs_snapper_0sprdd
This document discusses using Btrfs and Snapper to enable full system rollbacks. It describes how snapshots are used to capture the state of the system at different points in time. These snapshots can then be used to rollback the entire system to a previous known good state, reducing downtime from system issues or configuration changes. The key capabilities of Snapshots include automatically capturing changes, displaying differences between snapshots, and rolling back to previous states. Integration with tools like YaST allow visualizing and undoing changes at the file level, while full system rollback supports reverting the entire operating system, including the kernel.
The document discusses developing plugins for the MySQL INFORMATION_SCHEMA by creating custom tables. It provides steps to create a simple "Hello World" plugin that defines a table with two columns and fills it with sample data. The document also describes how to build and install the plugin so it can be queried from INFORMATION_SCHEMA like a regular table.
This document provides an overview of MySQL for Oracle DBAs, covering topics such as MySQL architecture, backup and recovery strategies, managing space and tables, and connecting MySQL to Oracle. The key points discussed include MySQL's product architecture and internal memory structures, filesystem layout for binaries, data and log files, InnoDB and MyISAM storage engines for managing space, and using tools like mysqldump, mysqlhotcopy, and mysqlbinlog for backups and point-in-time recovery.
Introduction to MySQL Enterprise MonitorMark Leith
The document is a presentation on MySQL Enterprise Monitor (MEM) by Mark Leith of Oracle. It introduces MEM as a distributed monitoring system for MySQL with a central Service Manager and agents installed on monitored hosts. The presentation includes sections on MEM architecture showing its core components, and a demo of features in the MEM UI like viewing instances, advisors, events, graphs, and query analysis.
Getting to Know MySQL Enterprise MonitorMark Leith
MySQL Enterprise Monitor is the monitoring and management solution for DBAs and developers delivered as part of MySQL Enterprise Edition. It provides background monitoring, alerting, trending, and analysis of the MySQL database and the statement traffic that is running within it.
View this session to learn how to install/configure, customize, and use MySQL Enterprise Monitor to suit your environment. Whether you use a single server or have hundreds of instances, MySQL Enterprise Monitor can provide great insights into how your environment is performing.
The document describes Performance Schema and ps_helper. Performance Schema is a feature in MySQL that collects runtime performance data and ps_helper is a tool that makes Performance Schema data easier to understand. It provides views, functions and stored procedures to summarize Performance Schema data for common use cases like analyzing user activity and statements.
This document provides an overview and agenda for a presentation on MySQL 5.6 performance tuning and best practices. The presentation covers analyzing MySQL workload and internals, performance improvements in MySQL 5.6 and 5.7, benchmark results, and pending issues. It emphasizes the importance of monitoring systems to understand performance bottlenecks and the need for an iterative process of monitoring, tuning, optimizing, and improving database performance over time.
Performance Schema for MySQL TroubleshootingSveta Smirnova
The Performance Schema in MySQL provides tables and instruments for troubleshooting issues like locks, I/O bottlenecks, slow queries, memory usage, and replication failures. It contains over 500 instruments in MySQL 5.6 and over 800 in 5.7. The tables provide visibility into the internal workings of MySQL to analyze and optimize performance.
This document discusses the Performance Schema in MySQL, which records instrumentation data to help profile and monitor database activity. It provides an overview of the Performance Schema's components and tables, how it has evolved between MySQL versions to include more metrics and functionality, and examples of how to query the tables to analyze wait events, statements, stages and other performance data.
The MySQL sys schema was integrated fully into MySQL Server from version 5.7.7 and has been improved in MySQL 8.0. Whether you are a DBA trying to determine where the resources are being used on your database instance and by whom, or a developer trying to figure out why your MySQL statements are running too slowly, the MySQL sys schema can help. Join this session to learn how to better use the MySQL sys schema to answer your day-to-day questions—from the original developer of the MySQL sys schema.
This document provides an overview of the MySQL sys schema. It discusses how sys schema provides views and functions on top of the Performance Schema to implement common DBA and developer use cases. It covers installing sys schema, the various formatting and helper functions it includes, and the summary views it provides for analyzing user activity, I/O, schema objects and more.
Instrumenting plugins for Performance SchemaMark Leith
This document discusses how to instrument plugins for the MySQL Performance Schema to provide visibility into plugin operations and avoid "black holes" in performance data. It covers the main interfaces for instrumenting threads, file/memory/network operations. An example audit plugin is provided that instruments mutexes, files, stages. The Performance Schema output shows the staged, waited events for a query.
Performance Schema and Sys Schema in MySQL 5.7Mark Leith
MySQL 5.7 now includes the Sys Schema by default, which builds upon the awesome instrumentation framework laid by Performance Schema.
Performance Schema has had 23 worklogs completed in 5.7 alone, such as memory instrumentation, tying in transactions and stored programs in to the current statement/stage/wait instruments and wait graph, prepared statement instruments, metadata lock information, improved session status and variable reporting, the new structured replication tables, and more.
The Sys schema builds upon this strong foundation with easy reporting views and functions, as well as procedures to help both set up and manage the configuration of Performance Schema, and help diagnose performance issues with your database instances on the whole.
Come along and hear from the original developer of the Sys schema about all of these exciting improvements in MySQL instrumentation for the upcoming MySQL 5.7 release!
MySQL Cluster Asynchronous replication (2014) Frazer Clement
Slides from 2014 describing basic features and implementation of MySQL Cluster asynchronous (binlog) replication, with some monitoring and tuning guidance.
MySQL 5.6, news in 5.7 and our HA optionsTed Wennmark
Join us for this free MySQL Tech Tour to learn straight from the source how you can benefit from Oracle’s latest MySQL innovations. Our technical experts will help you understand how to take advantage of the wide range of new features and enhancements available in MySQL Fabric, MySQL 5.6, MySQL Cluster and other MySQL solutions. They will share tips & tricks to help you get the most of your database. You will also discover what’s coming next in MySQL 5.7.
Oracle Database 12c includes over 500 new features. Some key new features include:
- Oracle Database 12c Express (EM Express) which replaces Database Control and has less features than Database Control but does not require Java or an app server.
- New online capabilities like online DDL operations with no DDL locking, online move of partitions with no impact to queries, and online statistics gathering for bulk loads.
- Adaptive SQL Plan Management which allows the optimizer to select a more optimal plan at execution time based on current statistics.
- Multitenant architecture which allows consolidation of multiple databases into one container database with pluggable databases.
This document provides an overview of MySQL server performance tuning. It discusses laying the foundation for performance tuning by examining the server, OS, network and filesystem. It also covers examining current server settings and status variables, and tuning various aspects of MySQL like InnoDB, MyISAM, queries and session settings. The document aims to provide guidance on areas to optimize to improve MySQL server performance.
Replicate from Oracle to Oracle, Oracle to MySQL, and Oracle to AnalyticsContinuent
Oracle is the most powerful DBMS in the world. However, Oracle's expensive and complex replication makes it difficult to build highly available applications or move data in real-time to data warehouses and popular databases like MySQL.
In this webinar you will learn how Continuent Tungsten solves problems with Oracle replication at a fraction of the cost of other solutions and with less management overhead too – think "Oracle GoldenGate without the price tag!" We will demo constructing a highly available site using Oracle-to-Oracle replication. We will then show you how to replicate data in real time from Oracle to MySQL as well as load a data warehouse.
This document provides an overview and summary of MySQL Cluster. It discusses how MySQL Cluster provides high availability, scalability and performance through features like auto-sharding, multi-master replication, ACID compliance, and built-in high availability. It also provides examples showing how MySQL Cluster can scale to handle over 1 billion updates per minute and discusses how operations like restarts have been improved in MySQL Cluster 7.4.1.
My MySQL and NoSQL presentation from the NoSQL Search event in Copenhagen: http://nosqlroadshow.com/nosql-cph-2013/speaker/Ted+Wennmark
MySQL offers solutions to implement NoSQL concepts like auto-sharding, key-value access or asynchronous operations. This adds all known solutions from the SQL world to the NoSQL space.
The combined approach of SQL and NoSQL gives developers the choice to select whatever features from both worlds they need.
In this talk we take a deeper look at key-value access to MySQL and MySQL Cluster, auto-sharding and scalability of MySQL Cluster, mapping of schemaless key value access to a relational data model and the performance of NoSQL access to MySQL.
Replicate Oracle to Oracle, Oracle to MySQL, and Oracle to AnalyticsLinas Virbalas
Oracle is the most powerful DBMS in the world. However, Oracle's expensive and complex replication makes it difficult to build highly available applications or move data in real-time to data warehouses and popular databases like MySQL. In this webinar you will learn how Continuent Tungsten solves problems with Oracle replication at a fraction of the cost of other solutions and with less management overhead too – think "Oracle GoldenGate without the price tag!" We will demo constructing a highly available site using Oracle-to-Oracle replication. We will then show you how to replicate data in real time from Oracle to MySQL as well as load a data warehouse.
This document summarizes a presentation about new features and changes coming in MySQL 5.7. Key points include: MySQL 5.7 will include performance improvements, more robust transaction handling and memory instrumentation. However, some backwards incompatible changes will be needed to improve the architecture. The presentation outlines several proposed changes, such as making replication more durable by default and changing the default SQL mode to STRICT. It also discusses new features for InnoDB and the optimizer.
Whats new in Oracle Database 12c release 12.1.0.2Connor McDonald
This document provides an overview of new features in Oracle Database 12c Release 1 (12.1.0.2). It discusses Oracle Database In-Memory for accelerating analytics, improvements for developers like support for JSON and RESTful services, capabilities for accessing big data using SQL, enhancements to Oracle Multitenant for database consolidation, and other performance improvements. The document also briefly outlines features like Oracle Rapid Home Provisioning, Database Backup Logging Recovery Appliance, and Oracle Key Vault.
OUGLS 2016: Guided Tour On The MySQL Source CodeGeorgi Kodinov
We will go over the layout of the MySQL code base, roughly following the query execution path. We will also cover how to extend MySQL with both built-in and pluggable add-ons.
The document compares various database companies and their products. It provides details on TmaxSoft, including its employee headcount, main products which include databases and middleware, and key technologies. It then discusses Tibero database specifically and how it compares to Oracle, including features, licensing model, compatibility, and security. Examples are also provided showing capabilities of Tibero compared to Oracle.
This document discusses new features in the InnoDB storage engine in MySQL 8.0, including a single shared data dictionary, serialized dictionary information stored in tablespaces, and atomic DDL operations using a new DDL log table. It also describes improvements to ALTER TABLE operations with a new instant ADD COLUMN algorithm that does not require rebuilding tables.
Simplifying MySQL, Pre-FOSDEM MySQL Days, Brussels, January 30, 2020.Geir Høydalsvik
The document discusses the evolution of MySQL over the past 10 years. Key changes include refactoring code to separate processing phases, rewriting the optimizer, moving to UTF8 as the default character set, implementing a new iterator-based query executor, refactoring InnoDB, and transitioning to using services and components instead of plugins. It also summarizes how MySQL differed from the Drizzle approach in focusing on gradual, production-tested changes over rewriting everything from scratch.
Mysql User Camp : 20th June - Mysql New FeaturesTarique Saleem
This document discusses new features in MySQL 5.7 and NoSQL support in MySQL. Some key points:
- MySQL 5.7 includes improvements to InnoDB for better transactional performance and scalability, as well as enhancements to replication, security, and other areas.
- NoSQL support allows direct access to MySQL data via Memcached APIs for simpler and faster key-value access while maintaining ACID guarantees.
- Benchmarks show NoSQL inserts into MySQL can be up to 9x faster than SQL inserts, and MySQL 5.7 can achieve over 1 million queries per second.
Mysql User Camp : 20-June-14 : Mysql New features and NoSQL SupportMysql User Camp
This slide was presented at Mysql User Camp Event on 20-June-14 at Oracle bangalore. This presentation gives a good insight about New Features in Mysql 5.7 DMR 4 and Nosql Support in Mysql.
MySQL Shell/AdminAPI - MySQL Architectures Made Easy For All!Miguel Araújo
Talk given at MySQL Belgian Days 2024.
Covers all the MySQL Architectures supported to ensure business continuity with a focus on business requirements, tecnicalities, and features: InnoDB Cluster, InnoDB ClusterSet, InnoDB Cluster Read Replicas and InnoDB ReplicaSet.
A special focus is given on the AdminAPI of MySQL Shell, with its main features, recommendations, and the latest additions and features.
This document discusses Spirit, an online schema change utility for MySQL 8.0. It begins by covering the state of DDL operations in MySQL and how Spirit works to perform schema changes without blocking reads or writes. It then discusses optimizations Spirit uses and features like checkpointing. Finally, it outlines some feature requests to make more operations instant or inplace in MySQL to reduce the need for Spirit in many cases.
The document outlines 10 usability guidelines for MySQL:
1) All features should be possible through SQL for consistency and discoverability.
2) Features, configurations, and errors should be intuitively obvious and discoverable without reading manuals cover-to-cover.
3) Too many similar configuration options without clear use cases can be paralyzing; only add options if use cases are known.
4) New configuration options must allow the effect to be measured through observability.
5) Features should work consistently across contexts for orthogonality.
6) The system should be safe to script against and avoid duplicate processing.
7) Extend functionality to match common use cases.
8) Preserve the ability to
This document summarizes the author's first 90 days of experience with Vitess, an open source database proxy. It provides an overview of Vitess, including that it sits between applications and MySQL to provide routing, query consolidation, and other features. It also discusses Vitess terminology, questions about MySQL compatibility, consistency models, and other quirks and features. The document concludes with a discussion of the best use cases for Vitess and areas where it could be improved.
TiDB is a distributed, horizontally scalable SQL database that is compatible with MySQL. It separates processing and storage into independent scalable components - the TiDB SQL layer and the TiKV storage foundation. TiDB uses a multi-version concurrency control approach based on Google's Spanner/F1 databases. It has been used in large-scale production deployments containing over 30 TB of data per day. Benchmarks show it can scale linearly with additional nodes. While aiming to be compatible with MySQL features, it does not support some like stored procedures and triggers.
Introducing TiDB - Percona Live FrankfurtMorgan Tocker
TiDB is an open-source distributed SQL database developed by PingCAP that is compatible with MySQL. It provides horizontal scalability, high availability, and consistent distributed transactions. Mobike, which has 200 million users and 9 million bikes, uses TiDB to handle over 30 TB of data per day. While TiDB aims to be compatible with MySQL, some features like stored procedures work differently or are still in development.
TiDB Introduction - Boston MySQL Meetup GroupMorgan Tocker
This document provides an overview and summary of TiDB, an open-source distributed SQL database inspired by Google's Spanner and F1. The summary includes:
1. TiDB is a distributed SQL database that is compatible with MySQL and provides horizontal scalability, high availability, and strong consistency with a hybrid OLTP/OLAP architecture.
2. It consists of TiDB, TiKV, and PD components where TiDB is the frontend MySQL compatible database layer, TiKV is the distributed key-value storage layer, and PD is the placement driver for metadata management.
3. TiDB is being used by over 300 companies including Mobike for applications such as real-time analytics, high concurrency
TiDB Introduction - San Francisco MySQL MeetupMorgan Tocker
This document provides an overview and agenda for introducing TiDB, an open source distributed SQL database inspired by Google's Spanner and F1 projects. The summary includes:
- TiDB is a distributed SQL database that is compatible with MySQL and provides horizontal scalability, high availability, and strong consistency with its key components TiDB, TiKV, and PD.
- The agenda covers an introduction to PingCAP, the company behind TiDB, a technical walkthrough of the TiDB architecture, and a use case example with Mobike, one of TiDB's customers with over 200 million users.
- A live demo of running TiDB on Google Kubernetes Engine is also included on the agenda along with discussions of
This document provides an overview and summary of TiDB, an open-source distributed SQL database compatible with MySQL. It discusses TiDB's architecture which includes TiDB for the SQL layer, TiKV for storage, and PD for placement driving. TiDB provides features like horizontal scalability, distributed transactions, and high availability. Example use cases are also presented, like Mobike's use of TiDB for locking/unlocking bikes and real-time analytics of bike usage data across 200 cities in China.
The document is an introduction to the MySQL 8.0 optimizer guide. It includes a safe harbor statement noting that the guide outlines Oracle's general product direction but not commitments. The agenda lists 25 topics to be covered related to query optimization, diagnostic commands, examples from the "World Schema" sample database, and a companion website with more details.
This document discusses using MySQL in automated testing. It covers various tools that can be used to automate and manage database deployments as part of testing, including pt-online-schema-change, MySQL Sandbox, SYS, Outbrain Propagator, Liquibase, ORM migrations, and libeatmydata. It also discusses considerations for different MySQL versions, such as online DDL support being introduced in MySQL 5.6. The document aims to demonstrate that databases can and should be automated and treated as first-class citizens in testing environments.