MySQL Workbench is a very good and free GUI tool provided by Oracle to manage MySQL administration and development tasks. Opening many MySQL connections (same or different instances, remote or local MySQL servers) at the same time is one of its main features. While it’s working fine to perform SQL statements on the different connections opened for multiple instances, but some people are asking if it is available as well to start and stop multiple MySQL instances using MySQL Workbench? if yes, how to configure it to perform such task? and also does that make any conflict with MyEnv tool - if it’s installed - or not?
Yes, MySQL Workbench could be configured to start and stop multiple MySQL instances (local or remote) and it does not make any conflict with MyEnv tool.
I just want to mention here that Galera 3.1 GA is now released but the online upgrade from MySQL 5.5 to 5.6 has some problems and a workaround should be made (Bug #1251137) to get this process done.
The output you just provided could be gotten by having your database’s tables backed up individually and then restore them the same way. For this purpose, the backup script should be something like:
No one can deny that one of the most important and daily tasks for DBAs is performing backup and restore operations, we’re not required to perform backup and restore operations only when we want to add new replication slave, when we want to implement disaster recovery procedures or when we want to prepare testing or staging server for the running production system, but even if we’re going to make any changes to the database schema in order to enhance the database performance, it’s recommended to have fresh backup copy before making any live changes, so if backup and restore operations cannot be handled smoothly, we’re going to face many troubles in our daily work. If we’re going to talk about backup and restore operations, Xtrabackup tool will be strongly appeared.
I don’t think that there’s such way in MySQL like MSSQL to track users modifications, but you can check the general log file (if it’s enabled) and search for all DCL statements related to the user in question.
In the general log file, MySQL records all commands received by the client along with the issuance timestamp.
I hope that helps..
Thanks Oli for the very helpful post, it really helped me to understand how to use and operate GLB, but I'd like to mention here that the option "-q" works only in Ubuntu, but in CentOS, it should be replaced by "-s" to be used as follows:
Codership announced from weeks ago introducing the Galera Cluster new release 3.0 having many bug fixes, performance enhancements plus the main purpose which is working with MySQL 5.6. In this article, I’ll go through the upgrade steps from Galera 2.x to the new release 3.0, but at the time of writing this article - as mentioned in the Codership release notes - THIS IS A BETA QUALITY RELEASE FOR TESTING PURPOSES. NOT RECOMMENDED FOR PRODUCTION YET.
