Hello.
Among other suggestions think about such way.
If you MyISAM and InnoDB tables are used by different applications or
consistent state between them doesn't play big value, and the size
of MyISAM tables is low enough, you could perform the dump in two steps
listing the tables of the s
ucture.
Our table defintitions are relatively stable so we don't do it every
night. You could put it in the cron job to do it with the backup.
-Original Message-
From: Scott Plumlee [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 12:36 PM
To: mysql@lists.mysql.com
Subject: Re: Ba
>
> -Original Message-
> From: Scott Plumlee [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 17, 2005 10:21 AM
> To: mysql@lists.mysql.com
> Subject: Backup database with MyISAM and InnoDB tables together
>
> I'm not clear on best practice to use on a database
cuted
-Original Message-
From: Scott Plumlee [mailto:[EMAIL PROTECTED]
Sent: Friday, June 17, 2005 10:21 AM
To: mysql@lists.mysql.com
Subject: Backup database with MyISAM and InnoDB tables together
I'm not clear on best practice to use on a database containing both
MyISAM and InnoDB ta
I'm not clear on best practice to use on a database containing both
MyISAM and InnoDB tables. For the MyISAM tables, it seems better to use
mysqldump --opt, thus getting the --lock-tables option, but for the
InnoDB the --single-transaction is preferred. Since they are mutually
exclusive, is t
