<< previous page   --   table of contents   --   next page >>
| | | | | | | |
  • Return to Table of Contents
  • Table of Contents

    1. General Information
    2. MySQL Installation
    3. Tutorial Introduction
    4. Database Administration
    5. MySQL Optimisation
    6. MySQL Language Reference
    7. MySQL Table Types
    8. MySQL APIs
    9. Extending MySQL

    Chapter 7:  MySQL Table Types 507 innodb_data_file_path=ibdata:30M but  to  get  good  performance  it  is  best  that  you  specify  options  as  recommended.   See Section 7.5.2 [InnoDB start], page 507. InnoDB is distributed under the GNU GPL License Version 2 (of June 1991).  In the source distribution of MySQL, InnoDB appears as a subdirectory. 7.5.2  InnoDB Startup Options To  use  InnoDB  tables  in  MySQL-Max-3.23  you  MUST  specify  con guration  parameters in  the  [mysqld]  section  of  the  con guration   le  `my.cnf',  or  on  Windows  optionally  in `my.ini'. At the minimum, in 3.23 you must specify innodb_data_file_path where you specify the names and the sizes of data les.  If you do not mention innodb_data_home_dir in `my.cnf' the default is to create these les to the datadir of MySQL. If you specify innodb_data_ home_dir as an empty string, then you can give absolute paths to your data les in innodb_ data_file_path.  In MySQL-4.0 you do not need to specify even innodb_data_file_path: the default for it is to create an auto-extending 10 MB le `ibdata1' to the  datadir  of MySQL. (In MySQL-4.0.0 and 4.0.1 the data le is 64 MB and not auto-extending.) But to get good performance you MUST explicitly set the InnoDB parameters listed in the following examples. Starting from versions 3.23.50 and 4.0.2 InnoDB allows the last data le on the  innodb_ data_file_path  line  to  be  speci ed  as  auto-extending.   The  syntax  for  innodb_data_ file_path is then the following: pathtodatafile:sizespecification;pathtodatafile:sizespecification;... ...   ;pathtodatafile:sizespecification[:autoextend[:max:sizespecification]] If  you  specify  the  last  data le  with  the  autoextend  option,  InnoDB  will  extend  the  last data le if it runs out of free space in the tablespace.  The increment is 8 MB at a time.  An example: innodb_data_home_dir = innodb_data_file_path = /ibdata/ibdata1:100M:autoextend instructs  InnoDB  to  create  just  a  single  data le  whose  initial  size  is  100  MB  and  which is extended in 8 MB blocks when space runs out.  If the disk becomes full you may want to add another data le to another disk, for example.  Then you have to look the size of `ibdata1', round the size downward to the closest multiple of 1024 * 1024 bytes (= 1 MB), and specify the rounded size of `ibdata1' explicitly in innodb_data_file_path.  After that you can add another data le: innodb_data_home_dir = innodb_data_file_path = /ibdata/ibdata1:988M;/disk2/ibdata2:50M:autoextend Be cautious on lesystems where the maximum le-size is 2 GB! InnoDB is not aware of the OS maximum le-size.  On those lesystems you might want to specify the max size for the data le: innodb_data_home_dir = innodb_data_file_path = /ibdata/ibdata1:100M:autoextend:max:2000M
     

    Customer Support CentreMySQL Reference Manual

    Web Hosting Services
    UNIX WEB HOSTING
    MERCHANT ACCOUNTS
    DEDICATED SERVERS
    E-COMMERCE HOSTING
    SUPPORT & FAQ's
    TERMS OF USE
    Domain Services
    DOMAIN
    REGISTRATION
    MANAGE
    YOUR ACCOUNT
    SUPPORT & FAQ's
    TERMS OF USE
    Corporate Info
    ABOUT US
    OUR NETWORK
    CONTACT US
    SITE MAP
    Copyright © 2002 Dyntex Group, Inc. All Rights Reserved
  • Return to Table of Contents
  • Back to top

  • Web Hosting: Manuals & FAQ's

    1. Unix-Based Web Hosting
    2. Unix Dedicated Servers
    3. Windows Dedicated Servers
    4. CuteFTP User’s Guide
    5. CuteHTML User’s Guide
    6. WS_FTP Pro User's Guide
    7. Miva Order User's Guide
    8. Miva Merchant User's Guide