database

Powered by Drupal
By rprice , 10 March 2016

This module provides database backup and export functionality. Thanks to the PHP version of mysqldump. This module is similar to Backup and Migrate without all the bells and whistles. Features Supports sqlite, mysql, pgsql and dblib Supports compression gzip and bzip2 Tracks local export history Supports a large option set as found in mysqldump Allows backups to be exported locally or downloaded directly Supports stored procedures Include and exclude tables on export

By rprice , 10 March 2016

This module provides database backup and export functionality. Thanks to the PHP version of mysqldump. This module is similar to Backup and Migrate without all the bells and whistles. Features Supports sqlite, mysql, pgsql and dblib Supports compression gzip and bzip2 Tracks local export history Supports a large option set as found in mysqldump Allows backups to be exported locally or downloaded directly Supports stored procedures Include and exclude tables on export

By rprice , 6 January 2016

This module provides database backup and export functionality. Thanks to the PHP version of mysqldump. This module is similar to Backup and Migrate without all the bells and whistles. Features Supports sqlite, mysql, pgsql and dblib Supports compression gzip and bzip2 Tracks local export history Supports a large option set as found in mysqldump Allows backups to be exported locally or downloaded directly Supports stored procedures Include and exclude tables on export

By rprice , 6 January 2016

This module provides database backup and export functionality. Thanks to the PHP version of mysqldump. This module is similar to Backup and Migrate without all the bells and whistles. Features Supports sqlite, mysql, pgsql and dblib Supports compression gzip and bzip2 Tracks local export history Supports a large option set as found in mysqldump Allows backups to be exported locally or downloaded directly Supports stored procedures Include and exclude tables on export

By rprice , 6 September 2012

However, as we grew, scaling our existing features to accomodate more traffic turned out to be much less of an issue than adding new features.

In particular, making schema changes or adding indexes to a database with more than 10 - 20 million rows completely locks the database for hours at a time. Removing old indexes takes just as much time, and not removing them hurts performance because the database will continue to read and write to those unused blocks on every INSERT, pushing important blocks out of memory.

By rprice , 7 June 2012

Use the Computed Field module to create yet another field stored in the database, combining the two (or more) fields you want to search, then expose a filter for that field instead of both of the individual fields. (I don't like this because it duplicates content/storage, and involves an extra module to do so).