Free mysql database dump software for mac

MySQL Database Server 5.1.35 is a versatile and innovative tool which is designed for enterprise organizations delivering business critical database applications. It gives corporate developers, DBAs and ISVs an array of new enterprise features to make more productive developing, deploying, and managing industrial strength applications. If you need a GUI for MySQL Database, you can download - NAVICAT (MySQL GUI). It supports to import Oracle, MS SQL, MS Access, Excel, CSV, XML or other formats to MySQL.

MySQL Database Server delivers new enterprise features, including: ACID Transactions to build reliable and secure business critical applications. Stored procedures to improve developer productivity. Triggers to enforce complex business rules at the database level. Views to ensure sensitive information is not compromised. Information schema to provide easy access to metadata. Distributed transactions (XA) to support complex transactions across multiple databases.

MySQL BackUp is small app in AppleScript Studio, it allows for quick backup of your mysql data (locally or not) without the terminal (MySQL BackUp is wrapper for the mysqldump command).

Netinfo Database Loader 1.1 is created to be a tiny yet effective Filemaker pro database which assists you to import information in your local or shared Netinfo databases. It works by reformating and dumping all the entries in "raw format" that is copied in the Clipboard. Create a plain Textedit file, paste the dump in it, save it as UTF-8, then go back to the database to finish importation with AppleScript and the Terminal.

It is particularly well suited to create entries to use with OpenLDAP and Open directory in Mac OS X Server 10.2 so that you can create a shared LDAP directory to be exploited from Address Book, Entourage, or any other LDAP client.

Find Database Tables 1.0 is the right solution if you have a bunch of MySQL tables in your database that you aren't sure if you use anymore while finding them can be tough and daunting and you're afraid to delete any because that one obscure script you wrote years ago may still use it. Simply log onto your database sever, select your database, select the folder that has your scripts, and let Find Database Tables do the searching for you!

Major Features:

1. Fast Searching
2. View the table data - make sure if you really want to delete the table or not
3. View the scripts where a table was found
4. Drop unwanted tables right from the application
5. Export the results to a CSV file that can be used in any spreadsheet application
6. Can view table data, scripts, and delete tables while the searching is going on

JumpBox for the MySQL Relational Database 1.1.11 is described as an easy to use, flexible and feature-rich databases which is used as an integral component in many JumpBoxes.

This JumpBox includes MySQL 5 along with PHPMyAdmin setup and ready to run. It's a great tool for developing database backed applications and can also be used along with other JumpBoxes if you need to move the database into a separate virtual machine.

Deploying an application as a JumpBox provides a dramatically-reduced path to getting started with the software. Aside from installation benefits it yields other advantages such as portability across computing environments and simplified ongoing maintenance of the application.

This JumpBox is free so there's no risk in trying it out. Download it today and experience for yourself a whole new way of working with server software.

Major Benefits:

1. Self-contained deployment means easy to move or delete - it won't scatter files all over your operating system.
2. New versions of the JumpBox contain updates to each component in the software stack so there's no patching web servers, application servers, databases, dependencies, etc.
3. A web-based administration console simplifies the management of your application including SSL certs, email relaying, SSH, backups and more.
4. Once you know how to install a JumpBox you can deploy any of 50+ other JumpBoxes and take advantage of a growing library of conveniently-packaged Open Source software.

MySQL Query Browser is a database querying tool that combines the simplicity of a Web-browser-like interface with powerful features like multiple result sets on tab sheets, query history, storing query "bookmarks", editing and comparing resultsets, SQL script debugging, and more.
MySQL Query Browser is the easiest visual tool for creating, executing, and optimizing SQL queries for your MySQL Database Server.
The MySQL Query Browser gives you a complete set of drag-and-drop tools to visually build, analyze and manage your queries.
Main features:
- Query Toolbar to easily create and execute queries and navigate query history
- Script Editor giving you control to manually create or edit SQL statements
- Results Window so you can also easily compare and work with multiple queries
- Object Browser enabling you to manage your databases, bookmarks, and history using a Web Browser like interface
- Database Explorer where you can select tables and fields to query, as well as create and delete tables
- Table Editor allows you easily create, modify and delete tables
- Inline Help giving you instant help access to selected objects, parameters, and functions.
Enhancements:
- This is a maintenance release of the production MySQL Query Browser for Mac OS X.

Requirements: Mac OS X 10.3 or later, MySQL 3.23.6 or newer (installed locally or on a remote server).

MySQL is a very popular and open source SQL database provided by MySQL AB. MySQL AB is a commercial company that builds its business providing services around the MySQL database.
MySQL is the worlds most popular open source database software, with over 100 million copies of its software downloaded or distributed throughout its history.
With superior speed, reliability, and ease of use, MySQL has become the preferred choice of corporate IT Managers because it eliminates the major problems associated with downtime, maintenance, administration and support.
MySQL is a key part of LAMP (Linux, Apache, MySQL, PHP / Perl / Python), the fast growing open source enterprise software stack.
More and more companies are using LAMP as an alternative to expensive proprietary software stacks because of its lower cost and freedom from lock-in.

Enhancements
- Replication: Important Note: Binary logging with --binlog_format=ROW failed when a change to be logged included more than 251 columns. This issue was not known to occur with mixed-format or statement-based logging. (Bug#42977)
- Replication: Assigning an invalid directory for the --slave-load-tmpdir caused the replication slave to crash. (Bug#42861)
- Replication: The mysql.procs_priv system table was not replicated. (Bug#42217)
- Replication: An INSERT DELAYED into a TIMESTAMP column issued concurrently with a an insert on the same column not using DELAYED, but applied after the other insert, was logged using the same timestamp as generated by the other (non-DELAYED) insert. (Bug#41719)
- Replication: The MIXED binary logging format did not switch to row-based mode for statements containing the LOAD_FILE() function. (Bug#39701)
- Replication: When the server SQL mode included IGNORE_SPACE, statement-based replication of LOAD DATA INFILE ... INTO tbl_name failed because the statement was read incorrectly from the binary log; a trailing space was omitted, causing the statement to fail with a syntax error when run on the slave. (Bug#22504)
- An attempt by a user who did not have the SUPER privilege to kill a system thread could cause a server crash. (Bug#43748)
- On Windows, incorrectly specified link dependencies in CMakeLists.txt resulted in link errors for mysql_embedded, mysqltest_embedded, and mysql_client_test_embedded. (Bug#43715)
- mysql crashed if a request for the current database name returned an empty result, such as after the client has executed a preceding SET sql_select_limit=0 statement. (Bug#43254)
- If the value of the version_comment system variable was too long, the mysql client displayed a truncated startup message. (Bug#43153)
Queries of the following form returned an empty result:
- SELECT ... WHERE ... (col=col AND col=col) OR ... (false expression)
- The strings/CHARSET_INFO.txt file was not included in source distributions. (Bug#42937)
- A dangling pointer in mysys/my_error.c could lead to client crashes. (Bug#42675)
- Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak. (Bug#42502)
- With more than two arguments, LEAST(), GREATEST(), and CASE could unnecessarily return Illegal mix of collations errors. (Bug#41627)
- The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug#41486)
- In the help command output displayed by mysql, the description for the c (clear) command was misleading. (Bug#41268)
- The load_defaults(), my_search_option_files() and my_print_default_files() functions in the C client library were subject to a race condition in multi-threaded operation. (Bug#40552)
- If --basedir was specified, mysqld_safe did not use it when attempting to locate my_print_defaults. (Bug#39326)
- When MySQL was configured with the --with-max-indexes=128 option, mysqld crashed. (Bug#36751)
- Setting the join_buffer_size variable to its minimum value produced spurious warnings. (Bug#36446)
- The use of NAME_CONST() can result in a problem for CREATE TABLE ... SELECT statements when the source column expressions refer to local variables. Converting these references to NAME_CONST() expressions can result in column names that are different on the master and slave servers, or names that are too long to be legal column identifiers. A workaround is to supply aliases for columns that refer to local variables. Now a warning is issued in such cases that indicate possible problems. (Bug#35383)
- An attempt to check or repair an ARCHIVE table that had been subjected to a server crash returned a 144 internal error. The data appeared to be irrecoverable. (Bug#32880)
- The Time column for SHOW PROCESSLIST output and the value of the TIME column of the INFORMATION_SCHEMA.PROCESSLIST table now can have negative values. Previously, the column was unsigned and negative values were displayed incorrectly as large positive values. Negative values can occur if a thread alters the time into the future with SET TIMESTAMP = value or the thread is executing on a slave and processing events from a master that has its clock set ahead of the slave. (Bug#22047)
- Restoring a mysqldump dump file containing FEDERATED tables failed because the file contained the data for the table. Now only the table definition is dumped (because the data is located elsewhere). (Bug#21360)