I've been searching for automatic solution to repair and analyze, optimize and check mysql databases all-in-one with a click, with ability to keep reports, and can be scheduled in task scheduler, I've found a lot of solution but all for Linux, and all command line based..
my need is to have small windows solution for this, server is windows server 2012 and using mysql that have several live databases needs automatic maintenance each while
Automatic backup batch for windows is available, but for maintenance and the above mentioned commands, couldn't find anything related to windows
anybody faced this and can help?
thanks in advanced
Related
[I posted the query below to the Database Admin StackExchange site but was put on hold due to being off-topic, which came as a wee surprise. I hope that it's not OT for StackOverflow. ]
My (medium-sized) organisation uses the excellent MySQL Workbench 6.1 Community for DB management. Workbench used to have a scheduled backup tool built in, IIRC, but no longer - you have to buy the Enterprise Edition for this.
So I've a quick question: what cheap/Open Source utilities are available to plugin in Workbench to configure and run scheduled backups of selected or all DB? By 'backup', I mean a nightly SQL dump of N DBs. There is a thread at Automatic backup MySQL Workbench but that references fairly heavy-duty tools. Another thread on here refers to an outdated Workbench version.
We can use a batch file (it's a Windoze server) to schedule backups, but for futureproofing and for the sake of my successor(s) it would be nice to have an easy-to-use GUI tool. Any recommendations?
There's no free tool or plugin for MySQL Workbench to schedule backups. However with MySQL Enterprise Backup (in short MEB) you can do that, including management from within MySQL Workbench. MEB is however a commercial solution for MySQL.
In a development environment, where Ubuntu 14.04 installed and updated to Kubuntu 14.04 is used the operating system. MySQL installed and used with Netbeans and JPA using eclipselink. I noted that some tables are dropped without my knowledge and then I created users with no drop or delete privileges. When I log with mysql command, I can not delete tables. But tables are still get dropped intermittently ? What can be the cause? I am really worried as a very similar environment is used in production and a loss of a table can lead severe consequences.
Table just don't magically disappear.
If I was you, I'd start by getting the list of users having the rights to do the delete/drop table.
Ask them if anyone is working on the DDL.
If no one seems to be "guilty", then what about to check what logging possibilities are provided by your DBMS, and to what extent could you log drop operations.
Is there an easy way to configure scheduled mysql dumps without scripting?
My setup is Windows Server with MySQL 5.6
I've never done it since I rarely use windows in development.
But maybe you can use this one. This one is windows based.
http://sourceforge.net/projects/mysqlbutool/
I've been working with Mysql Gui tools (for 5.0) at work for nearly 2 years and have accumulated about 100 stored connections.
We're now upgrading to use Mysql Workbench 5.3 Community Edition and i'm looking for a way to import, convert or any other way to make my stored connections available in Workbench.
I've looked around for ways to do this but found very little, even no topics or threads on how to go about this.
Only thing i've found is someone stating that the xml used to store the connections for both apps is completely different and non-trivial to convert by hand.
Does anyone know of a tool, plugin or method to get the stored connections from the gui tools into Workbench?
By Gui tools i mean the seperate programs Query Browser, Administrator and System tray monitor.
Our Java server application logs data to a SQL database, which may or may not be on the same machine. Currently we use MS SQL Server, and we're now porting to MySQL. A user configures database backup parameters on our app server, e.g. time of day to run a backup, and the app server executes SQL Server's BACKUP DATABASE command at the appropriate time, via a sproc. It does incremental backups daily and full backups weekly.
MySQL lacks an equivalent feature to tell the database from a client connection to back itself up. Options we're considering are:
Create a UDF to shell out to mysqldump (or copy database files), which can be called from our app server via a sproc. Essentially we'd be implementing a version of BACKUP DATABASE for MySQL.
Create a service to run on the MySQL box that can get the backup settings from the app server and run mysqldump (or file copy) locally.
Create a backup sproc to mimic mysqldump, e.g. SHOW CREATE TABLES and SELECT INTO OUTFILE for each table.
Setting up a cron job, Perl script, third-party app or other tricks that'd work great in a data center aren't preferred; this is a shrink-wrap package that needs to be pretty robust and hands off.
Database sizes can range from roughly 10MB to 10GB.
I'm aware of the binary logs for the incremental piece. I figure the general solution will probably apply to them as well, if we decide to use them.
This is all on Windows 2003 32-bit or 2008R2 64-bit, MySQL 5.1.
The UDF option seems the best to me. The UDF Repository (http://www.mysqludf.org/) has mysqludf_sys, which may be all we need, but I thought I'd ask for opinions since after extensive googling it doesn't seem like others have reached the same conclusion, or maybe our needs are just out of the ordinary. Our app is the only thing in MySQL, so I'm not worried about other users having access to our UDF.
Any solutions I'm overlooking? Any experience with using UDFs in such a way?
Thanks,
Eric
For this an other reasons we decided to collocate our application with the database, so this problem became moot.