Symlinking works fine but keep in mind an important gotcha: if you ever do a table rebuild, mysql completely ignores your symlink and overwrites it with the file (which may even fill up your disk).
Have you noticed these table options (from http://dev.mysql.com/doc/mysql/en/create-table.html)? | DATA DIRECTORY = 'absolute path to directory' | INDEX DIRECTORY = 'absolute path to directory' Having the data and index files on seperate drives can certainly speed up IO. I know these options work for MyISAM, but am not sure about InnoDB. Atle - Flying Crocodile Inc, Unix Systems Administrator On Wed, 14 Sep 2005, Chris Kantarjiev wrote: > I'd like to spread the disk arm load across multiple drives. At > the moment, we mostly use MyISAM tables, but we are also > experimenting with InnoDB. > > What's the 'best practice' for doing this? There's no obvious > configuration that lets me designate one directory for index > and another for data - am I meant to do this with symlinks? > How can I do anything like that with InnoDB, which appears > to put everything in one massive file? > > Thanks. > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
