MySQL

Splitting up Unweildy Database Dumps/Exports

Submitted by ethan on

I recently found myself in possession of a huge (~1.5GB) MySQL dump that I needed to restore after a system reinstall. When a text file gets this large, it is very difficult to edit or even view, as text editors simply can't handle the size. Fortunately, I figured out a simple way of separating the single file into separate databases that could be viewed or imported individually. It works because a typical database dump first creates the database, then the tables, then inserts the data into those tables. It does this sequentially, for one database at a time.

Troubleshooting MySQL Dumps and Imports

Submitted by stevem on

The various versions of MySQL are more or less compatible with one another, but problems arise pretty regularly, especially when it comes to moving between versions of MySQL. Here are some notes about common MySQL dumping and importing issues, particularly those relevant to Back-End, Drupal, and CiviCRM.

Reserved words

Subscribe to MySQL