Software companies looking to implement a self-service business intelligence solution may be using MySQL, one of the most useful open source databases, for their data. Certain issues seemed to have reduced MySQL’s usability in recent years, resulting in many users eagerly awaiting the newest release. The release of MySQL 8.0 seems to answer that need.
If you’re considering upgrading to the newest version of MySQL for your database needs, you probably have some questions about what this release features and how it can help you. Here are some of the new features that have been added to MySQL 8.0 that will help developers decide if this release is right for their data needs.
Improvements to SQL Roles
One of the new additions to MySQL is an improvement in how standard SQL roles operate. With the newest version of MySQL, you can now grant roles, create roles, drop roles and decide what roles should be used during a particular session. A new command ROLES_GRAPHML() returns a graphml document that shows the role subgraphs, increasing utility for your database operation.
Unlock the value of your SQL databases by seamlessly integrating Izenda’s embedded self-service business intelligence and analytics solutions, which reports directly against leading relational database systems, including MSSQL, Oracle, MySQL, and PostgreSQL.
A highly requested feature added in MySQL 8.0 is the ability to determine whether or not an index can be dropped. The inclusion of index toggling allows you to make an index invisible to see if it is still being queried by the system. While using index toggling, your index will still be maintained, even when invisible, providing you the option to make it visible again if you find it is still in use. Like most features in the recent MySQL release, index toggling works to improve utility and make developer tasks easier than ever before.
Transactional Data Dictionary
One of the biggest obstacles in previous versions of MySQL was the handling and storage of metadata. In older releases, metadata was stored in disks and database tables, which was messy, vulnerable to damage and hard to troubleshoot.
The newest update to MySQL seeks to address these important issues by upgrading the data dictionary. Instead of the mess that it used to be, the data dictionary is now stored in InnoDB tables, which is now the default storage option in MySQL. You can also now access the dictionary through a system-wide APO. These updates to the data dictionary will increase performance and improve the resiliency of your servers.
Previously the only way to get recursive CTEs in MySQL was to use a workaround like this one. Now the feature has been added directly into the MySQL 8.0. For more in-depth exploration of this feature, check out these blogs written by the author of the feature himself. They explore the implementation of Recursive and non-recursive CTEs in great detail.
SET PERSIST for Globals
Previous versions of MySQL, did not allow preservation of reconfigured globals and dynamics in the event of a server restart, often causing big headaches for users. Thanks to MySQL 8.0 you can now maintain your settings even after a restart. With a new set of commands, your reconfigured variables will be preserved, which is of particular use when you don’t have system file access.
Looking to add Business Intelligence to your Applications?
While we’ve touched on a few of the excellent features in the newest update of MySQL 8.0, the best idea is to go directly to the source. Izenda supports the use of MySQL as a data source for our embedded, self-service business intelligence and analytics solution.If you need to seamlessly integrate into your core application a BI solution that features ad hoc reporting for line of business, dashboards and visualizations, Izenda’s embedded analytics solution will meet and surpass your needs.