InnoDB is multiversioned. You can start a transaction, dump all your tables
inside a single transaction using SELECT INTO OUTFILE and you get a snapshot
of your database at a precise point of time. Because of multiversioning,
your tables are not locked during the dump.
I am also writing a (non-free) hot incremental binary backup program for
InnoDB which will be even faster than SELECT INTO OUTFILE. It will run in
From: Boaz Yahav <[EMAIL PROTECTED]>
To: Heikki Tuuri <[EMAIL PROTECTED]>
Cc: Manuel Lemos <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
Date: Sunday, January 13, 2002 10:45 PM
Subject: RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
>It's not just that...
>For example, when I want to backup the MySQL server (and we are talking
>of a few GB of data) the server is practically dead while making the
>dump. MSSQL Server 2000 (for example) does that in the background and
>you can keep working...
>From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
>Sent: Sunday, January 13, 2002 10:42 PM
>To: Boaz Yahav
>Subject: RE: [PHP-DB] Re: Moving from MySQL to MSSQL Server 2000
>If you are not happy with MyISAM's lack of transactions or row level
>or crash recovery, you could try InnoDB type tables in MySQL.
>You can use MySQL's master -> slave replication to get failover
>InnoDB - transactions, row level locking, and foreign key support for
>See http://www.innodb.com, download MySQL-Max from http://www.mysql.com
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]