Hi, Can anybody help with this ?
Regards, Marvin -----Original Message----- From: Marvin Wright Sent: 22 July 2005 10:46 To: Heikki Tuuri; mysql@lists.mysql.com Subject: RE: Correct way to use innodb_file_per_table? Hi Heikki, I've followed your instructions here and its all worked fine. Now I currently have a 200Gb shared innodb table space which is sitting almost empty now all databases have there own table spaces. I want to reduce this amount but ot sure what is the best way to do it. I know I can not just remove some of the ibdata files so I'd like your advice on what I should do. You recommend to dump tables before changing then re-import them back. But if all databases are in there own tablespace I should need to do this dump should I ? I want to reduce it to about 10gb, that should be enough for all its temporary storage and logs. Any advice on the best way to do this would be great. Thanks Marvin. -----Original Message----- From: Heikki Tuuri [mailto:[EMAIL PROTECTED] Sent: 04 March 2005 13:53 To: Mike Debnam; mysql@lists.mysql.com Subject: Re: Correct way to use innodb_file_per_table? Mike, ----- Alkuperäinen viesti ----- Lähettäjä: "Mike Debnam" <[EMAIL PROTECTED]> Vastaanottaja: <mysql@lists.mysql.com> Kopio: <[EMAIL PROTECTED]> Lähetetty: Friday, March 04, 2005 2:49 PM Aihe: Re: Correct way to use innodb_file_per_table? > Heikki, > >> the best way would be to symlink whole database directories under the >> datadir. Then also an ALTER TABLE keeps the new .ibd file on the >> drive you intended it to be on. If you symlink a single .ibd file, >> then an ALTER will create the new .ibd file as not symlinked. >> >> As an example, let us say you have three databases: 'database1', >> 'database2', and 'test'. You may shut down mysqld, copy all the >> contents of >> /datadir/database2 to drive 2, and then symlink the directory >> /datadir/database2 to drive 2. >> > > > Hmm, ok. I have just one decent size database though. I want to split > the tables in that database between disks. I haven't turned on > innodb_file_per_table yet I'm trying to plan it out first, so I don't > know the file layout yet. If my data directory is /var/db/mysql and my > InnoDB data file is /var/db/mysql/ibdata1 then the table files will be > created under /var/db/mysql/MyDatabase/MyTable1.ibd, > /var/db/mysql/MyDatabase/MyTable2.ibd, etc it sounds like. > > Is there a way to split those table files? So I could have something > like /data/disk1/MyTable1.ibd, /data/disk2/MyTable2.ibd? you can move the .ibd file where you want, and put a symlink in place. But remember that an ALTER will recreate the table to its original database dir, because ALTER does not know about symlinks. > Thanks for your help. > > Mike Best regards, Heikki Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL Network from http://www.mysql.com/network/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
