AFAIK, to move the data from one InnoDB file to one table per file, the only option is to dump and restore. (you may want to remove index, and foreign key checks before the restore, and put it back afterwards)
2005/8/23, Rafal Kedziorski <[EMAIL PROTECTED]>: > Hi, > > we have an J2EE application which ist using MySQL 4.0. There is an > bug, which was fixed in MySQL 4.1. We are using tracactions and > InnoDB is don't use query cache. Now we have to migrate our DB to > MySQL 4.1 for use this feature. In our actual installation we store > our data in one inndodb file. After migration we wan't use file per table. > > What is the best and fastest way to make migration? > > > Best Regards, > Rafal > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- Pooly Webzine Rock : http://www.w-fenec.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
