A: The MySQL Enterprise Monitor is a web-based application that helps customers improve performance, reduce downtime, and tighten security of their MySQL servers by notifiying them about problems in their database applications before they occur. Learn More »
2. What are the features and related benefits of the MySQL Enterprise Monitor?
A: MySQL Enterprise Monitor provides real-time visibility into the performance and availability of all your MySQL databases. The MySQL Query Analyzer lets you accurately pinpoint SQL code that is the root cause of a slow down. Rich graphs that drill down into detailed query information provide significantly better visibility into database performance issues. For the complete features and benefits, visit the MySQL Enterprise Monitor Features and Benefits page.
3. What are the immediate benefits of implementing the MySQL Enterprise Monitor?
A: The MySQL Enterprise Monitor allows developers and DBAs to start monitoring MySQL within 10 minutes with zero configuration and no agents required. Developers and DBAs get immediate real-time visibility into the performance and availability of their MySQL Servers and their supporting assets. MySQL Enterprise Monitor highlights problem servers and critical events that need attention.
Further, the MySQL Enterprise Monitor includes the MySQL Query Analyzer, which helps you find and tune your most expensive queries across all of your development, QA and production servers in minutes versus hours or even days using other methods.
4. What are the long-term benefits of the MySQL Enterprise Monitor?
A: Over time, the task of managing MySQL servers becomes exponentially more complicated, especially as the load of users, connections, application queries, and objects on each MySQL server increases. The MySQL Enterprise Monitor continually monitors the dynamic security, performance, replication and schema relevant metrics of all MySQL servers, so as the number of MySQL servers continues to grow, DBAs are kept up to date on potential problems and proactive measures that can be implemented to ensure each server continues to operate at the highest levels of security, performance and reliability. The MySQL Enterprise Monitor also uses historical data to provide detailed trend analysis, allowing for predictive alerts and outlier detection.
5. How is the MySQL Enterprise Monitor installed and deployed?
A: The Enterprise Monitor is a web application that can manage MySQL within the confines of the corporate firewall or public cloud.
6. How is the Enterprise Monitor web application architected?
A: The Enterprise Monitor web application is comprised of 3 components:
Service Manager: The Service Manager manages and stores the data collections that come in from each MySQL Server. It analyzes these collections using MySQL provided best practice Advisors to determine the health, security, availability and performance of each of the monitored MySQL Servers. The Service Manager also provides the content for the Enterprise Dashboard which serves as the client user interface for the web application.
Repository: A MySQL database that is used to store data collections and application-level configuration data.
Service Agent (optional): An agent that is installed on each of the monitored hosts to collect OS and host metrics
7. What are the MySQL and OS Metric Graphs?
A: The MySQL Enteprise Monitor graphs allow DBAs to monitor and correlate over 600 variables, including these metrics:
Users can mouse over and highlight specific regions of any Monitor graph to launch the MySQL Query Analyzer which provides a context-sensitive, filtered view of the queries that were running during the selected time.
8. What makes MySQL Enterprise Monitor unique?
A: Of the products on the market that monitor MySQL, SQL code and OS specific metrics, the MySQL Enterprise Monitor is the only solution that is built and supported by the engineers at MySQL. Unlike other solutions that report on raw MySQL and OS level metrics, the MySQL Enterprise Monitor is designed to optimize the use of MySQL by proactively monitoring MySQL instances and providing notifications and MySQL expert advice on corrective measures DBAs can take before problems occur. The MySQL Query analyzer also offers unmatched performance monitoring and tuning capabilities far beyond what other MySQL Slow Query Log based tools can provide.
9. What versions of MySQL are supported by the MySQL Enterprise Monitor?
A: The MySQL Enterprise Monitor can be used to monitor MySQL versions 5.1, 5.5, & 5.6 and MySQL Cluster 7.1, 7.2, & 7.3.
10. What operating system platforms are supported by the MySQL Enterprise Monitor?
A: The Enterprise Monitor Service Manager is fully supported on most current versions of Linux, Windows, Solaris, FreeBSD and Mac OS X. For the complete list of MySQL Enterprise supported operating systems and CPUs, visit the Supported Platforms page.
11. What are the MySQL Enterprise Advisors?
A: The MySQL Enterprise Advisors are a set of best practice guidelines to ensure optimal use of your MySQL instances, and their supporting assets. Advisors monitor all MySQL servers and report on database application problems before they occur. Each Advisor provides a detailed overview of the problem it is designed to identify, advices on how to correct the problem, specifies commands to implement the recommended fix and links to additional resources for additional research into the issue at hand.
A: The MySQL Query Analyzer allows DBAs, developers and system administrators to improve application performance by collecting, monitoring, and analyzing queries executed on their MySQL servers. Learn More »
13. How is the MySQL Query Analyzer installed and enabled?
A: The MySQL Query Analyzer works "out of the box" using MySQL 5.6 Performance Schema.
14. What overhead can I expect when the MySQL Query Analyzer is installed and enabled?
A: MySQL Performance Schema has, on average, an overhead of about 5%.
15. Can I leave the MySQL Query Analyzer enabled at all times?
A: Thanks to Performance Schema in MySQL 5.6, most customers can now leave the Query Analyzer enabled at all times, even on busy production systems.
16. What are the main features and benefits of the MySQL Query Analyzer?
17. What are the typical use cases of the MySQL Query Analyzer?
A: The typical use cases for developers, DBAs and system administrators are:
Developers – Monitor and tune application queries during development before they are promoted to production.
DBAs and System Administrators – Identify problem SQL code as it runs in production and advise development teams on how to tune.
18. What makes the MySQL Query Analyzer unique?
A: Other products (free, open source and commercial) that provide MySQL query monitoring are dependent on the MySQL Slow Query Log being enabled and available for sampling. While this provides some time savings over the DBA collecting and parsing the log directly, the Slow Query Log provides a very limited set of statistics, and it lacks any historical context. Query Analyzer provides every available metric relating to the query performance, and the new QRTi feature provides a single metric that allows you to easily identify those queries that are most problematic.
The MySQL Query Analyzer collects queries and execution statistics with no dependence on the SQL Query Log, it captures all SQL statements sent to the MySQL server and provides an aggregated view into the most expensive queries in number of executions and total execution time.
The MySQL Query Analyzer is also integrated with the MySQL Enterprise Monitor graphs, so you can mouse over and highlight specific time slices in any graph to launch a context-sensitive, filtered Query Analyzer view that shows you the queries that were running at the selected time on the selected instance(s) of MySQL.. This helps you quickly find the queries that may be causing spikes in your key system resources.
First, InnoDB tables are backed up. During that phase, reads and writes to the database are possible.
In the second phase, reads to MyISAM tables are possible but writes are blocked.
30. Can we use MySQL Enterprise Backup tool to backup only InnoDB tables and ignore MyISAM tables?
A. Yes, by using the ibbackup command only.
31. During recovery can I see the transaction state?
A. Yes the binlog position is saved internally and written out in the ibbackup --apply-log step during recovery.
32. Is the binlog saved in a file with the rest of the backup set?
A. It is stored in the internal backup status tables.
33. How much storage for backups can be saved using MySQL Enterprise Backup compression?
A. For a generic alphanumeric database, 70%-90% compression is typical.
34. Can MySQL Enterprise Backup prompt for a password instead of reading it from the command line?
A. Yes. If the --password option does not have an argument, mysqlbackup will prompt for the password.
35. Does MySQL Enterprise Backup backup views?
36. Can MySQL Enterprise Backup be integrated with 3rd party media managers?
You can do a file sweep of the backup files using 3rd party media managers. Streaming is not supported in the current release.
37. What operating systems and platforms does MySQL Enterprise Backup support?
A. MySQL Enterprise Backup supports the same platforms as supported by the latest MySQL database. For the complete list of MySQL Enterprise supported operating systems and CPUs, visit the Supported Platforms page.
38. Is MySQL Enterprise Backup open source software?
A: No. MySQL Enterprise Backup is available only as a part of the commercial MySQL Enterprise Edition. To purchase licenses for MySQL Enterprise Edition, please contact the MySQL Sales Team.
39. How can I try MySQL Enterprise Backup?
A. MySQL Enterprise Backup is included in the MySQL Enterprise Edition Trial. Try now »
40. How can I buy MySQL Enterprise Backup?
A. MySQL Enterprise Backup is included with the MySQL Enterprise Edition. Learn more »