Cool, Thanks a ton. I think I will stick with mysqldump for a while until my tables get too large. Currently my backups only take a few seconds.
Regards, Jake Johnson [EMAIL PROTECTED] ------------------------------------------------------------------ Plutoid - http://www.plutoid.com - Shop Plutoid for the best prices on Rims, Car Audio, and Performance Parts. On Thu, 26 Jun 2003, Ware Adams wrote: > mysqldump creates text files containing insert statements that recreate a > table and repopulate it with data. They are somewhat portable across > database servers and human editable if necessary. They take up less space > than the original table because they do not contain indices (only the > statements that would create the indices). mysqldump is nice b/c it works > for both InnoDB and MyISAM > > mysqlhotcopy makes a copy of the actual data files in your database. It is > much faster than mysqldump, but the resulting backup is larger b/c it > contains indices (unless you use the option to turn them off). Recovery is > quicker as the tables exist in the backup directory in full MyISAM table > form. With mysqldump you need to actually execute the dump files which can > take a while for large tables. mysqlhotcopy does not work with InnoDB. > > --Ware Adams > > Jake Johnson wrote: > > >Is this better than using mysqldump? > > > >> > mysqlhotcopy does your locking for you. > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
