DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 

(mysql.info) myisamchk-other-options

Info Catalog (mysql.info) myisamchk-repair-options (mysql.info) myisamchk (mysql.info) myisamchk-memory
 
 8.2.4 Other `myisamchk' Options
 -------------------------------
 
 `myisamchk' supports the following options for actions other than table
 checks and repairs:
 
    * -analyze, -a
 
      Analyze the distribution of key values. This improves join
      performance by enabling the join optimizer to better choose the
      order in which to join the tables and which indexes it should use.
      To obtain information about the key distribution, use a `myisamchk
      --description --verbose TBL_NAME' command or the `SHOW INDEX FROM
      TBL_NAME' statement.
 
    * -block-search=[OFFSET], -b OFFSET
 
      Find the record that a block at the given offset belongs to.
 
    * -description, -d
 
      Print some descriptive information about the table.
 
    * -set-auto-increment[=VALUE], -A[VALUE]
 
      Force `AUTO_INCREMENT' numbering for new records to start at the
      given value (or higher, if there are existing records with
      `AUTO_INCREMENT' values this large). If VALUE is not specified,
      `AUTO_INCREMENT' numbers for new records begin with the largest
      value currently in the table, plus one.
 
    * -sort-index, -S
 
      Sort the index tree blocks in high-low order. This optimizes seeks
      and makes table scans that use indexes faster.
 
    * -sort-records=N, -R N
 
      Sort records according to a particular index. This makes your data
      much more localized and may speed up range-based `SELECT' and
      `ORDER BY' operations that use this index. (The first time you use
      this option to sort a table, it may be very slow.) To determine a
      table's index numbers, use `SHOW INDEX', which displays a table's
      indexes in the same order that `myisamchk' sees them.  Indexes are
      numbered beginning with 1.
 
      If keys are not packed (`PACK_KEYS=0)'), they have the same
      length, so when `myisamchk' sorts and moves records, it just
      overwrites record offsets in the index. If keys are packed
      (`PACK_KEYS=1'), `myisamchk' must unpack key blocks first, then
      re-create indexes and pack the key blocks again. (In this case,
      re-creating indexes is faster than updating offsets for each
      index.)
 
Info Catalog (mysql.info) myisamchk-repair-options (mysql.info) myisamchk (mysql.info) myisamchk-memory
automatically generated byinfo2html