database

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

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

MarkLogic is optimized for structured and unstructured data—allowing you to store, manage, query and search across JSON, XML, RDF, geospatial data, text, and large binaries. This means faster time to value and an improved ability to handle change.

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.

is there any way to use drupal's database wrapper to create a brand new connection which can be permanently set to the new database without having to do this switching back-and-forth nonsense? surely we can handle connections to multiple databases concurrently.