are your really using disk partitions as InnoDB data files? If you use raw
disk partitions, then the operating system may put a limit on the number of
them, for example, 16.
But usually InnoDB data files will be just ordinary files of the file
system. The number of data files is restricted by the maximum parameter line
length in my.cnf, which is maybe 2048 bytes. Thus you can define hundreds of
InnoDB data files.
With very big databases it is probably easiest to use an operating system
which supports > 4 GB files, so that you can make your data files bigger
than 2 GB or 4 GB.
InnoDB reuses the space in its tablespace (tablespace = all the data files
concatenated). Thus space which is freed from one table is available for
other tables to use.
Order technical MySQL/InnoDB support at https://order.mysql.com/
See http://www.innodb.com for the online manual and latest news on InnoDB
Benjamin Arai wrote in message ...
>The size limitation is becauseof the operating system parameters. In
>order to use tables larger then 3 GB, use either Redhat 7.2 or Solaris 8.
>These operating systems allow file sizes greater then 2 GB. For the most
>part I achievedtables sizes using these operating system of greater the 50
>On Fri, 11 Jan 2002, Demirchyan Oganes-AOD098 wrote:
>> Hello everyone,
>> I guess I have the similar question, that has been brought up.
>> I have 36 InnoDB tables, and I have allocated two 2GB partitions for my
>> Provided I have very big hard drive, how many partitions at 2GB each
could I allocate? As many as my hard drive can handle?
>> I also have questions with regards, to a table size. In my case it will
be (4GB)/36 bytes per table? Is it distributed uniformly, or some tables
can grow bigger on the expense of the others (if some only have limited
data, and others keep having new data inserted into them).
>> Oganes Demirchyan
>> Motorola Life Science
>> 757 S.Raymond
>> Pasadena, CA 91105
>> Tel: 626-584-5900
>> email: Oganes.Demirchyan@stripped