> The short answer: no.
>
> http://dev.mysql.com/doc/refman/4.1/en/innodb-configuration.html states:
> " The autoextend attribute and those following can be used only for the last
> data file in the innodb_data_file_path line. autoextend is available
> starting from MySQL 3.23.50 and 4.0.2. "
>
> You could use two methods to manage the increasing need for space in your
> situation:
>
> 1) Use fixed sizes and keep track of the free space.
> Use SHOW TABLE STATUS LIKE '<tablename>'; and use the `Comment` column which
> shows you something like "InnoDB free: 5278720 kB". If this number gets too
> low, modify your config file and add an extra datafile.
>
> 2) Use an autoextend file and make it fixed size if it gets too large.
> http://dev.mysql.com/doc/refman/4.1/en/adding-and-removing.html tells you
> that you can change an autoextend datafile to a fixed size file by getting
> the size, rounding it to the closest multiple of 1024 x 1024 bytes (1MB),
> changing the settings in the configuration file in such a way that the
> autoextend file is now fixed to the size you calculated and that you added a
> new autoextend file.
hmm i'm not entirely sure i fancy adding another data file on the fly -
Can you give me a brief run down about how you would go about this?
another option would be for me to create the 100gig as 2 25 gig files
from the off - Do you know how well these would compress? Do you know
what they are 'filled' with so when it comes to backup they will
compress down to virtually nothing?
thanks
