File: administrator.html

package info (click to toggle)
mysql-gui-tools 5.0r14%2BopenSUSE-2.1
links: PTS, VCS
area: main
in suites: squeeze
size: 116,956 kB
ctags: 48,715
sloc: sql: 341,918; pascal: 276,698; ansic: 91,020; cpp: 90,451; objc: 33,236; sh: 29,481; yacc: 10,756; xml: 10,589; java: 10,079; php: 2,806; python: 2,092; makefile: 1,783; perl: 4
file content (3517 lines) | stat: -rw-r--r-- 214,494 bytes
parent folder | download | duplicates (2)
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>
  MySQL Administrator
 </title><link rel="stylesheet" href="html.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.65.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="book" lang="en"><div class="titlepage"><div><div><h1 class="title"><a name="mysql-administrator"></a>
   MySQL Administrator
  </h1></div><div><p class="copyright">Copyright  2004 MySQL AB</p></div><div><div class="legalnotice"><p>
    This manual is NOT distributed under a GPL style license. Use of the
    manual is subject to the following terms:

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      Conversion to other formats is allowed, but the actual content may
      not be altered or edited in any way.
     </p></li><li><p>
      You may create a printed copy for your own personal use.
     </p></li><li><p>
      For all other uses, such as selling printed copies or using (parts
      of) the manual in another publication, prior written agreement
      from MySQL AB is required.
     </p></li></ul></div><p>

    Please email docs@mysql.com for more information or if you are
    interested in doing a translation.
   </p></div></div></div><div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#mysql-administrator-introduction">1. 
   Introduction to MySQL Administrator
  </a></span></dt><dt><span class="chapter"><a href="#mysql-administrator-installation">2. 
   Installing MySQL Administrator
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-installation-introduction">2.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-installation-windows">2.2. 
    Installing Under Windows
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-installation-linux">2.3. 
    Installing Under Linux
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-starting">3. 
   Starting MySQL Administrator
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-starting-introduction">3.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-starting-connection">3.2. 
    Connection Dialog
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-starting-configure-service">3.3. 
    Configure-service Mode
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-main-window">4. 
   Main Window
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-main-window-introduction">4.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-sidebar">4.2. 
    Sidebar
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-working-area">4.3. 
    Working Area
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-menus">4.4. 
    Menus
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-administrator-menus-file">4.4.1. 
     File
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-edit">4.4.2. 
     Edit
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-view">4.4.3. 
     View
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-tools">4.4.4. 
     Tools
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-help">4.4.5. 
     Help
    </a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-server-information">5. 
   Server Information
  </a></span></dt><dt><span class="chapter"><a href="#mysql-administrator-service-control">6. 
   Service Control
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-service-control-introduction">6.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-service-control-start-stop-service">6.2. 
    Start/Stop Service
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-service-control-configure-service">6.3. 
    Configure Service
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-startup-variables">7. 
   Startup Variables
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-startup-variables-introduction">7.1. 
    Introduction
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-server-connections">8. 
   Server Connections
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-server-connections-introduction">8.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-connections-threads">8.2. 
    Threads
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-connections-user-connections">8.3. 
    User Connections
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-user-administration">9. 
   User Administration
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-user-administration-introduction">9.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-user-accounts">9.2. 
    User Accounts
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-user-information">9.3. 
    User Information
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-global-privileges">9.4. 
    Global Privileges
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-schema-privileges">9.5. 
    Schema Privileges
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-table-column-privileges">9.6. 
    Table Column Privileges
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-health">10. 
   Health
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-health-introduction">10.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-connection-health">10.2. 
    Connection Health
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-memory-health">10.3. 
    Memory Health
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-creating-graphs">10.4. 
    Creating Custom Health Graphs
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-status-variables">10.5. 
    Status Variables
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-system-variables">10.6. 
    System Variables
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-server-logs">11. 
   Server Logs
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-server-logs-introduction">11.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-logs-error-log">11.2. 
    Error Log
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-logs-slow-log">11.3. 
    Slow Log
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-logs-general-log">11.4. 
    General Log
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-backup">12. 
   Backup
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-backup-introduction">12.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-backup-backup-project">12.2. 
    Backup Project
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-backup-advanced-options">12.3. 
    Advanced Options
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-administrator-backup-advanced-options-execution-method">12.3.1. 
     Backup Execution Method
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-backup-advanced-options-output-options">12.3.2. 
     Output File Options
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#mysql-administrator-backup-schedule">12.4. 
    Schedule
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-restore">13. 
   Restore
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-restore-introduction">13.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-restore-general">13.2. 
    General
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-restore-restore-content">13.3. 
    Restore Content
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-replication-status">14. 
   Replication Status
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-replication-introduction">14.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-replication-status-configure">14.2. 
    Configuring Replication Servers
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-replication-status-using">14.3. 
    Using the Replication Status Section
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-administrator-catalogs">15. 
   Catalogs
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-administrator-catalogs-introduction">15.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-catalogs-schema-tables">15.2. 
    Schema Tables
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-administrator-catalogs-schema-tables-table-status">15.2.1. 
     Table Status
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-catalogs-schema-tables-row-status">15.2.2. 
     Row Status
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#mysql-administrator-catalogs-indexes">15.3. 
    Schema Indexes
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#gui-table-editor">16. 
   The MySQL Table Editor
  </a></span></dt><dd><dl><dt><span class="sect1"><a href="#gui-table-editor-introduction">16.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#gui-table-editor-main-window">16.2. 
    The Main Editor Window
   </a></span></dt><dt><span class="sect1"><a href="#gui-table-editor-columns-and-indices">16.3. 
    The Columns And Indices Tab
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#gui-table-editor-columns-and-indices-column-editor">16.3.1. 
     The Column Editor
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-columns-and-indices-detail">16.3.2. 
     The Detail Area
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#gui-table-editor-Table-Options">16.4. 
    The Table Options Tab
   </a></span></dt><dt><span class="sect1"><a href="#gui-table-editor-advanced-options">16.5. 
    The Advanced Options Tab
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-various">16.5.1. 
     The Various Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-row-options">16.5.2. 
     The Row Options Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-storage-options">16.5.3. 
     The Storage Options Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-merge-options">16.5.4. 
     The Merge Table Options Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-raid-options">16.5.5. 
     The Table RAID Settings Section
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#gui-table-editor-changes">16.6. 
    Applying Your Changes
   </a></span></dt></dl></dd><dt><span class="chapter"><a href="#mysql-gui-options">17. 
 Options Dialog
</a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-gui-options-introduction">17.1. 
  Introduction
 </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-general-options">17.2. 
  General Options
 </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-connections">17.3. 
  Connections
 </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-editors">17.4. Editors</a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-administrator">17.5. 
    Administrator
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-gui-options-administrator-user-administration">17.5.1. User Administration</a></span></dt><dt><span class="sect2"><a href="#mysql-gui-options-administrator-health-graphs">17.5.2. Health Graphs</a></span></dt><dt><span class="sect2"><a href="#mysql-gui-options-administrator-backup">17.5.3. Backup</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#mysql-administrator-appendix-tray-monitor">A. 
   The MySQL System Tray Monitor
  </a></span></dt><dt><span class="appendix"><a href="#mysql-gui-install-source">B. Installing From Source</a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-gui-install-source-introduction">B.1. Introduction</a></span></dt><dt><span class="sect1"><a href="#mysql-gui-install-source-download">B.2. Downloading The Source Code</a></span></dt><dt><span class="sect1"><a href="#mysql-gui-install-source-windows">B.3. 
    Building from Source under Windows
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-gui-install-source-windows-prerequisites">B.3.1. 
     Prerequisites
    </a></span></dt><dt><span class="sect2"><a href="#mysql-gui-install-source-windows-compiling">B.3.2. 
     Compiling and Building
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#mysql-gui-install-source-linux">B.4. 
    Building from Source under Linux
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-gui-install-source-linux-prerequisites">B.4.1. 
     Prerequisites
    </a></span></dt><dt><span class="sect2"><a href="#mysql-gui-install-source-linux-compiling">B.4.2. 
     Compiling and Building
    </a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#mysql-gui-appendix-troubleshooting">C. 
  Troubleshooting Application Errors
 </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-gui-appendix-troubleshooting-connection-errors">C.1. 
   Troubleshooting Connection Errors
  </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-appendix-troubleshooting-display-problems">C.2. 
   Troubleshooting Display Problems
  </a></span></dt></dl></dd><dt><span class="appendix"><a href="#mysql-gui-appendix-store-connections">D. 
  How Connections Are Stored
 </a></span></dt><dt><span class="appendix"><a href="#mysql-gui-appendix-xml-files">E. 
  XML Files Common to the MySQL GUI Applications
 </a></span></dt><dt><span class="appendix"><a href="#mysql-administrator-appendix-xml-files">F. 
   XML Files Used by MySQL Administrator
  </a></span></dt><dt><span class="appendix"><a href="#mysql-gui-appendix-notes-for-translators">G. 
  Notes for Translators
 </a></span></dt><dt><span class="appendix"><a href="#mysql-gui-appendix-third-party-software">H. 
  Third-party Software Used by the MySQL GUI Tools
 </a></span></dt><dd><dl><dt><span class="sect1"><a href="#mysql-gui-appendix-third-party-software-pcre">H.1. 
   PCRE Library
  </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-appendix-third-party-software-png">H.2. 
   PNG Support
  </a></span></dt></dl></dd></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>3.1. <a href="#id4674481">
     Connection dialog
    </a></dt><dt>3.2. <a href="#id4674708">
     Switching to configure-service mode
    </a></dt><dt>3.3. <a href="#id4674735">
     Configure-service mode
    </a></dt><dt>4.1. <a href="#id4737909">
     MySQL Administrator main window
    </a></dt><dt>4.2. <a href="#id4738119">
     Marked area between sidebar and working area
    </a></dt><dt>9.1. <a href="#id4740653">
     User accounts
    </a></dt><dt>9.2. <a href="#id4740913">
     User Information tab
    </a></dt><dt>10.1. <a href="#id4741892">
     The Graph Settings dialog
    </a></dt><dt>11.1. <a href="#id4742349">
     Displaying entries from the middle of the General Log
    </a></dt><dt>13.1. <a href="#id4743562">
     The Restore Content tab
    </a></dt><dt>14.1. <a href="#id4743725">
     The Replication Status section
    </a></dt><dt>16.1. <a href="#id4745006">
     The MySQL Table Editor
    </a></dt><dt>16.2. <a href="#id4745116">
      The column editor
     </a></dt><dt>16.3. <a href="#id4745229">
       The index editor
      </a></dt><dt>16.4. <a href="#id4745882">
     The Confirm Table Edit dialog
    </a></dt><dt>17.1. <a href="#id4747119">
    Options dialog
   </a></dt><dt>17.2. <a href="#id4747450">
   Options dialog: Connections
  </a></dt><dt>A.1. <a href="#id4749125">
    The MySQL System Tray Monitor
   </a></dt><dt>C.1. <a href="#id4751562">
    Error message dialog
   </a></dt></dl></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-introduction"></a>Chapter1.
   Introduction to MySQL Administrator
  </h2></div></div><div></div></div><p>
   MySQL Administrator is a program for performing administrative
   operations, such as configuring your MySQL server, monitoring its
   status and performance, starting and stopping it, managing users and
   connections, performing backups, and a number of other administrative
   tasks.
  </p><p>
   You can perform most of those tasks using a command line interface
   such as that provided by
   <a href="http://dev.mysql.com/doc/en/mysqladmin" target="_top"><span><b class="command">mysqladmin</b></span>
   </a> or
   <a href="http://dev.mysql.com/doc/en/mysql" target="_top"><span><b class="command">mysql</b></span></a>,
   but MySQL Administrator is advantageous in the following respects:

   </p><div class="itemizedlist"><ul type="disc"><li><p>
     Its graphical user interface makes it more intuitive to use.
    </p></li><li><p>
     It provides a better overview of the settings that are crucial for
     the performance, reliability, and security of your MySQL servers.
    </p></li><li><p>
     It displays performance indicators graphically, thus making it
     easier to determine and tune server settings.
    </p></li></ul></div><p>
  </p><p>
   MySQL Administrator is designed to work with MySQL servers versions 4.0
   and higher.
  </p><p>
   MySQL Administrator is to a large extent the result of feedback MySQL AB
   has received from many users over a period of several years. However,
   if you find it's lacking some feature important to you, or if you
   discover a bug, please use our
   <a href="http://bugs.mysql.com" target="_top">MySQL Bug System</a> to
   request features or report problems.
  </p></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-installation"></a>Chapter2.
   Installing MySQL Administrator
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-installation-introduction">2.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-installation-windows">2.2. 
    Installing Under Windows
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-installation-linux">2.3. 
    Installing Under Linux
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-installation-introduction"></a>2.1.
    Introduction
   </h2></div></div><div></div></div><p>
    MySQL Administrator runs on Windows and Linux. You can find MySQL
    Administrator for the operating system of your choice on the
    <a href="http://dev.mysql.com/downloads/administrator/" target="_top">MySQL
    Downloads</a> page.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-installation-windows"></a>2.2.
    Installing Under Windows
   </h2></div></div><div></div></div><p>
    MySQL Administrator runs on 32-bit Windows NT based operating systems,
    including Windows NT, 2000, XP, and 2003.
   </p><p>
    MySQL Administrator is installed through the use of a Windows Installer
    (<tt class="literal">.msi</tt>) installation package, which can be used to
    install the MySQL Administrator on all Windows operating systems. The
    MSI package in contained within a ZIP archive named
    <tt class="literal">mysql-administrator-<i class="replaceable"><tt>version</tt></i>-win-noinstall.zip</tt>,
    where <i class="replaceable"><tt>version</tt></i> indicates the
    MySQL Administrator version. Download the ZIP file, extract it and
    change into the directory you extracted it into.
   </p><p>
    The Windows Installer engine was updated with the release of Windows
    XP; those using an older version can reference
    <a href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;292539" target="_top">this
    Microsoft Knowledge Base article</a> for information on
    upgrading to the latest version.
   </p><p>
    To install MySQL Administrator, right-click on the MSI file and select
    <span class="guimenu">Install</span>. The installation will begin
    automatically after the installer prompts you for your installation
    preferences. During installation, you can choose if you want the
    installer to place a shortcut in the <tt class="literal">Start</tt> menu,
    and/or an icon on the desktop.
   </p><p>
    If you are having problems running the installer, you can download a
    ZIP file without an installer as an alternative. That file is called
    <tt class="literal">mysql-administrator-<i class="replaceable"><tt>version</tt></i>-win-noinstall.zip</tt>.
    Using a ZIP program, unpack it to a directory of your choice. You
    may want to create shortcuts to
    <tt class="literal">MySQLAdministrator.exe</tt> for your desktop or quick
    launch bar.
   </p><p>
    Unless you choose otherwise, MySQL Administrator is installed in
    <tt class="literal">c:\<i class="replaceable"><tt>%PROGRAMFILES%</tt></i>\MySQL\GUITools\MySQL Administrator\MySQLAdministrator.exe</tt>,
    where <i class="replaceable"><tt>%PROGRAMFILES%</tt></i> is the default
    directory for programs on your machine. For example, this directory
    might be <tt class="literal">c:\Program Files</tt> or
    <tt class="literal">c:\programme</tt>.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-installation-linux"></a>2.3.
    Installing Under Linux
   </h2></div></div><div></div></div><p>
    MySQL Administrator runs on Linux machines that have a graphical desktop
    installed. It is designed to run under the Gnome desktop, but you
    may also use other desktops, such as KDE, as long as GTK2 is
    installed. It has been tested on Linux kernel versions 2.4 and 2.6,
    but it should also run on other versions, and even on a number of
    Unix-like operating systems.
   </p><p>
    To install MySQL Administrator, first download the installation tarball.
    The tarball file is called
    <tt class="literal">mysql-administrator-<i class="replaceable"><tt>version</tt></i>-linux.tar.gz</tt>,
    where <i class="replaceable"><tt>version</tt></i> indicates the
    MySQL Administrator version (for example 1.0.12).
   </p><p>
    To see all files in the tarball, run this command:

</p><pre class="programlisting">
    
    shell&gt; tar -tzf  mysql-administrator-<i class="replaceable"><tt>version</tt></i>-linux.tar.gz
   </pre><p>
   </p><p>
    To install MySQL Administrator, run this command:

</p><pre class="programlisting">
    
    shell&gt; tar --directory=/opt -xzvf mysql-administrator-<i class="replaceable"><tt>version</tt></i>-linux.tar.gz
   </pre><p>
   </p><p>
    This installs the application binary in
    <tt class="literal">/opt/mysql-administrator/bin</tt>. Change into that
    directory and run <tt class="literal">mysql-administrator</tt> to start
    the application.
   </p><p>
    Distribution-specific packages will be available at some point.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-starting"></a>Chapter3.
   Starting MySQL Administrator
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-starting-introduction">3.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-starting-connection">3.2. 
    Connection Dialog
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-starting-configure-service">3.3. 
    Configure-service Mode
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-starting-introduction"></a>3.1.
    Introduction
   </h2></div></div><div></div></div><p>
    The way you start MySQL Administrator depends on the operating system
    you are using:

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      On Windows, start MySQL Administrator by double-clicking its desktop
      icon, or by selecting its item from the <tt class="literal">Start</tt>
      menu. Alternatively, you can open a DOS window and start it from
      the command line:

</p><pre class="programlisting">
      c:\&gt; c:\<i class="replaceable"><tt>program 
directory</tt></i>\MySQL\GUITools\MySQLAdministrator.exe
     </pre><p>

      <i class="replaceable"><tt>program directory</tt></i> is the default
      directory for programs on your machine, for example
      <tt class="literal">c:\program files</tt> or
      <tt class="literal">c:\programme</tt>. If your path contains spaces, you
      should enclose the command within quote characters. For example:

</p><pre class="programlisting">
      c:\&gt; "c:\program files\mysql\bin\MySQLAdministrator.exe"
     </pre><p>
     </p></li><li><p>
      On Linux desktops, start MySQL Administrator by changing directory
      into <tt class="literal">/opt/mysql-administrator/bin</tt>, and then
      running <tt class="literal">mysql-administrator</tt>.
     </p></li></ul></div><p>
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-starting-connection"></a>3.2.
    Connection Dialog
   </h2></div></div><div></div></div><p>
    Once MySQL Administrator has been started, it displays a connection
    dialog. You have to specify the MySQL server to which you would like
    to connect, the credentials needed for authorization on that server,
    and which machine that server runs on (and which port it listens
    to). You may also specify a number of other options, if required.
   </p><p>
    As an alternative to connecting to a running MySQL server, you can
    run MySQL Administrator in
    <a href="#mysql-administrator-starting-configure-service" title="3.3.
    Configure-service Mode
   ">configure
    -service mode</a>.
   </p><div class="figure"><a name="id4674481"></a><p class="title"><b>Figure3.1.
     Connection dialog
    </b></p><div><img src="images/connection.png" alt="Connection dialog"></div></div><p>
    Note that MySQL Administrator will not work with MySQL servers prior to
    version 4.0. If you try to connect to an older server, an error
    message will appear, telling you that this is not possible.
   </p><p>
    If the server connection is successfully established, all of the
    values filled in the fields of the connection dialog will be saved
    for future connections (see the section that describes
    <a href="#mysql-gui-appendix-store-connections" title="AppendixD.
  How Connections Are Stored
 ">how
    MySQL Administrator stores connection information</a>). The
    <tt class="literal">Password</tt> field, however, will always be empty:
    For security reasons, the password is not stored along with the
    other options, unless you explicitly specify otherwise in the
    <a href="#mysql-gui-options-general-options" title="17.2.
  General Options
 ">Gen eral
    Options section of the Options dialog</a>.
   </p><p>
    You can change any of the values in the connection profiles just by
    overwriting the existing values with new ones. Similarly, if you
    select another connection profile, you can change any of its values.
    When you click the <span class="guibutton">OK</span> button after changing a
    profile's values, the changes are stored permanently if a successful
    connection to the MySQL server is established. However, the
    preferred method for changing a profile is to click the
    <span class="guibutton">...</span> button next to the
    <span class="guilabel">Connection</span> drop-down box. That brings up an
    <tt class="literal">Options</tt> dialog window that has a
    <tt class="literal">Connections</tt> section for modifying connection
    profiles. You can find the values you can set in the Connection
    dialog window in the description of the
    <tt class="literal">Connections</tt> section of the
    <tt class="literal">Options</tt> dialog (see
    <a href="#mysql-gui-options-connections" title="17.3.
  Connections
 ">Options
    dialog</a>).
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-starting-configure-service"></a>3.3.
    Configure-service Mode
   </h2></div></div><div></div></div><p>
    Normally, you will use MySQL Administrator to connect to a running MySQL
    server. This is done by starting the program and specifying in the
    <a href="#mysql-administrator-starting-connection" title="3.2.
    Connection Dialog
   ">Connection</a>
    dialog which server to connect to.
   </p><p>
    Alternatively, you can run MySQL Administrator in configure-service
    mode. This is useful in the following cases:

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      When you want to start a MySQL server from within MySQL
      Administrator. Obviously, you cannot connect to a server that is
      not running, so you will have to use the configure-service mode to
      start that server. Note that, at the moment, you can only start
      servers on the same machine where MySQL Administrator is running (that
      is on the local host).
     </p></li><li><p>
      When you have
      <a href="http://dev.mysql.com/doc/en/multiple-servers" target="_top">multiple
      servers</a> running on your machine. On Windows, MySQL
      Administrator only allows you to configure the Windows service
      that is listed first in the Windows services management when
      running in normal mode. This means that if you have more than one
      Windows service, you can only configure the first one of those, no
      matter which server you have connected to. If you want to
      configure a service other than the first service, you will have to
      run MySQL Administrator in configure-service mode.
     </p></li></ul></div><p>
   </p><p>
    To start MySQL Administrator in configure-service mode, hold down the
    <span><b class="keycap">CTRL</b></span> key in the
    <a href="#mysql-administrator-starting-connection" title="3.2.
    Connection Dialog
   ">Connection</a>
    dialog. The <span class="guibutton">Cancel</span> button will toggle to
    <span class="guibutton">Skip</span> when that key is pressed.
   </p><div class="figure"><a name="id4674708"></a><p class="title"><b>Figure3.2.
     Switching to configure-service mode
    </b></p><div><img src="images/configure-service-mode-connection.png" alt="Switching to configure-service mode"></div></div><p>
    Clicking on the <span class="guibutton">Skip</span> button will skip the
    normal mode, thus starting MySQL Administrator in configure-service
    mode.
   </p><div class="figure"><a name="id4674735"></a><p class="title"><b>Figure3.3.
     Configure-service mode
    </b></p><div><img src="images/configure-service-mode-window.png" alt="Configure-service mode"></div></div><p>
    Under <tt class="literal">Installed Services</tt> in the
    <a href="#mysql-administrator-sidebar" title="4.2.
    Sidebar
   ">sidebar</a>,
    you can select the service that you wish to configure, or the server
    that you want to stop or start. In configure-service mode, as
    opposed to normal mode, there is only a subset of the sections in
    the sidebar avaiable:

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      The
      <a href="#mysql-administrator-service-control" title="Chapter6.
   Service Control
  ">Service
      Control</a> section allows you to start and stop a MySQL
      server, and to configure the Windows service managing that server.
     </p></li><li><p>
      The
      <a href="#mysql-administrator-startup-variables" title="Chapter7.
   Startup Variables
  ">Startup
      Variables</a> section allows you to set variables for server
      startup.
     </p></li></ul></div><p>

    Both of those sections are described in detail below.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-main-window"></a>Chapter4.
   Main Window
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-main-window-introduction">4.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-sidebar">4.2. 
    Sidebar
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-working-area">4.3. 
    Working Area
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-menus">4.4. 
    Menus
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-administrator-menus-file">4.4.1. 
     File
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-edit">4.4.2. 
     Edit
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-view">4.4.3. 
     View
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-tools">4.4.4. 
     Tools
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-menus-help">4.4.5. 
     Help
    </a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-main-window-introduction"></a>4.1.
    Introduction
   </h2></div></div><div></div></div><p>
    After you have successfully connected to your MySQL server, the main
    window of MySQL Administrator appears (see figure). The main window
    contains a sidebar, a working area, and menus with submenus.
   </p><i><span class="remark">
    [SH] Mike: Need new graphics from Mike (with annotations!)
   </span></i><div class="figure"><a name="id4737909"></a><p class="title"><b>Figure4.1.
     MySQL Administrator main window
    </b></p><div><img src="images/mainwindow.png" alt="MySQL Administrator main window"></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-sidebar"></a>4.2.
    Sidebar
   </h2></div></div><div></div></div><p>
    The sidebar consists of the following sections:

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      <a href="#mysql-administrator-server-information" title="Chapter5.
   Server Information
  ">Server
      Information</a>: Information about the MySQL server you are
      connected to, about MySQL Administrator and the machine that it runs
      on, and about your connection.
     </p></li><li><p>
      <a href="#mysql-administrator-service-control" title="Chapter6.
   Service Control
  ">Service
      Control</a>: Start and stop the MySQL server. On Windows, you
      can also configure the MySQL service.
     </p></li><li><p>
      <a href="#mysql-administrator-startup-variables" title="Chapter7.
   Startup Variables
  ">Startup
      Variables</a>: Configure the startup variables for the MySQL
      server.
     </p></li><li><p>
      <a href="#mysql-administrator-server-connections" title="Chapter8.
   Server Connections
  ">Server
      Connections</a>: View or kill current connections to the MySQL
      server (also called threads).
     </p></li><li><p>
      <a href="#mysql-administrator-user-administration" title="Chapter9.
   User Administration
  ">User
      Administration</a>: Administer existing users, add new users,
      and delete existing users.
     </p></li><li><p>
      <a href="#mysql-administrator-health" title="Chapter10.
   Health
  ">Health</a>:
      Graphical displays of a number of usage or hitrate values that
      affect server performance, and a hierarchical view of system and
      status variables.
     </p></li><li><p>
      <a href="#mysql-administrator-server-logs" title="Chapter11.
   Server Logs
  ">Server
      Logs</a>: View log file entries.
     </p></li><li><p>
      <a href="#mysql-administrator-backup" title="Chapter12.
   Backup
  ">Backup</a>: Plan
      and administer backup projects, select the databases to be backed
      up, and start the backup process.
     </p></li><li><p>
      <a href="#mysql-administrator-restore" title="Chapter13.
   Restore
  ">Restore</a>:
      Restore databases from existing backups.
     </p></li><li><p>
      <a href="#mysql-administrator-replication-status" title="Chapter14.
   Replication Status
  ">Replication
      Status</a>: View information about replication master and slave
      servers.
     </p></li><li><p>
      <a href="#mysql-administrator-catalogs" title="Chapter15.
   Catalogs
  ">Catalogs</a>:
      View information about databases, tables, columns, indexes, and
      rows; optimize tables.
     </p></li></ul></div><p>

    The following sections describe each of these in detail.
   </p><p>
    You can change the width of the sidebar in the main window by
    dragging the separator between sidebar and working area. To hide the
    sidebar completely, click on the marked area in the separator
    (located in the vertical center of it). To make the sidebar visible
    again, double-click the marked area (which then forms the left
    margin of the main window).
   </p><div class="figure"><a name="id4738119"></a><p class="title"><b>Figure4.2.
     Marked area between sidebar and working area
    </b></p><div><img src="images/marked-area.png" alt="Marked area between sidebar and working area"></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-working-area"></a>4.3.
    Working Area
   </h2></div></div><div></div></div><p>
    While the
    <a href="#mysql-administrator-sidebar" title="4.2.
    Sidebar
   ">sidebar</a>
    allows you to select the sections, the working area displays
    information, or fields, that pertain to the selected section. For
    some sections, the working area is split into two or more tabs.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-menus"></a>4.4.
    Menus
   </h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-menus-file"></a>4.4.1.
     File
    </h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-file-new-instance-connection"></a>4.4.1.1.
      New Instance Connection ...
     </h4></div></div><div></div></div><p>
      Opens the
      <a href="#mysql-administrator-starting-connection" title="3.2.
    Connection Dialog
   ">Connection
      dialog</a>, allowing you to open another connection to a MySQL
      server. You may open an arbitrary number of connections. MySQL
      Administrator opens a new main window for each successfully
      established connection. Connections may be to the same or
      different servers. Multiple connections may be opened using the
      same profile or different profiles.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-file-manage-connections"></a>4.4.1.2.
      Manage Connections ...
     </h4></div></div><div></div></div><p>
      Opens the <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options
      dialog</a>, with the
      <a href="#mysql-gui-options-connections" title="17.3.
  Connections
 ">Con
      nections section</a> preselected.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-file-save-current-connection"></a>4.4.1.3.
      Save current Connection ...
     </h4></div></div><div></div></div><p>
      Opens the <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options
      dialog</a>, with the
      <a href="#mysql-gui-options-connections" title="17.3.
  Connections
 ">Con
      nections section</a> preselected. Furthermore, a new connection
      profile labeled <tt class="literal">New Connection</tt> is created,
      which is also preselected. The fields are filled with the values
      of the most recent connection. You can edit the values and save
      the settings in the new profile. You may also want to rename the
      profile from <tt class="literal">New Connection</tt> to something more
      appropriate. If you click the <span class="guibutton">Close</span> button
      without saving your changes with the <span class="guibutton">Apply
      Changes</span> button, you will be prompted as to whether you
      want to save or discard your changes.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-file-close"></a>4.4.1.4.
      Close
     </h4></div></div><div></div></div><p>
      Closes the MySQL Administrator window and terminates the connection to
      the MySQL server that had been established in that window. If you
      have opened more than one instance (program window, or process) of
      MySQL Administrator, this command will not close the other windows.
     </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-menus-edit"></a>4.4.2.
     Edit
    </h3></div></div><div></div></div><p>
     The <span class="guimenu">Cut</span>, <span class="guimenu">Copy</span>, and
     <span class="guimenu">Paste</span> commands allow you to cut, copy, or paste
     selected text in the
     <a href="#mysql-administrator-working-area" title="4.3.
    Working Area
   ">working
     area</a>.
    </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-edit-options"></a>4.4.2.1.
      Options
     </h4></div></div><div></div></div><p>
      Opens the <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options
      dialog</a> window.
     </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-menus-view"></a>4.4.3.
     View
    </h3></div></div><div></div></div><p>
     The <span class="guimenu">View</span> menu selects sections from the
     <a href="#mysql-administrator-sidebar" title="4.2.
    Sidebar
   ">sidebar</a>.
     Selecting an item from this menu is the same as clicking the
     section with the same name from the sidebar.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-menus-tools"></a>4.4.4.
     Tools
    </h3></div></div><div></div></div><p>
     The <span class="guimenu">Tools</span> menu starts other programs.
    </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-tools-mysql-command-line-client"></a>4.4.4.1.
      MySQL Command Line Client
     </h4></div></div><div></div></div><p>
      This menu item is available only if MySQL Administrator finds the
      executable of the MySQL command-line client. At the moment, it
      will look up locations like <tt class="literal">c:\mysql\bin</tt>,
      <tt class="literal">d:\mysql\bin</tt>, and
      <tt class="literal">c:\<i class="replaceable"><tt>program
      directory</tt></i>\mysql\bin</tt> to find
      <tt class="literal">mysql.exe</tt>. If it is found, you can start the
      command-line client with this command. MySQL Administrator will use
      the credentials provided in the
      <a href="#mysql-administrator-starting-connection" title="3.2.
    Connection Dialog
   ">Connection
      dialog</a> to start a server connection using the command-line
      client.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-tools-windows-command-line"></a>4.4.4.2.
      Windows Command Line
     </h4></div></div><div></div></div><p>
      Opens a DOS window.
     </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-menus-help"></a>4.4.5.
     Help
    </h3></div></div><div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-help-online-help"></a>4.4.5.1.
      Online Help
     </h4></div></div><div></div></div><p>
      Opens a window displaying the MySQL Administrator section of the MySQL
      reference manual.

      <i><span class="remark">
       [SH] Mike: Should be "Help" only to make clear it will not load
       the MySQL online manual from www.mysql.com/doc/
      </span></i>
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-help-report-bug"></a>4.4.5.2.
      Report Bug to MySQL
     </h4></div></div><div></div></div><p>
      Opens a connection to the MySQL bug reporting system in your web
      browser.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-help-mysql-website"></a>4.4.5.3.
      Launch MySQL Website
     </h4></div></div><div></div></div><p>
      Opens a connection to the MySQL web site in your web browser.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-administrator-menus-help-about"></a>4.4.5.4.
      About ...
     </h4></div></div><div></div></div><p>
      Displays information about MySQL Administrator.
     </p></div></div></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-server-information"></a>Chapter5.
   Server Information
  </h2></div></div><div></div></div><p>
   Provides basic information about connection, server, and client.
  </p><div class="itemizedlist"><ul type="disc"><li><p>
    Connected to MySQL Server Instance

    <i><span class="remark">
     [SH] Mike: The label name is gruesome (why not just "Connection"?).
    </span></i>
   </p><p>
    Information about the parameters used to connect to the MySQL
    server.

    </p><div class="itemizedlist"><ul type="circle"><li><p>
      <tt class="literal">User</tt>: Username used for the current connection
      to the MySQL server.
     </p></li><li><p>
      <tt class="literal">Host</tt>: The hostname of the machine where the
      MySQL server runs. This is either identical to the name listed in
      <tt class="literal">Network Name</tt>, or it is
      <tt class="literal">localhost</tt>. The former indicates that you are
      connecting to a server that either runs on a remote machine, or
      that you have specified a hostname different from
      <tt class="literal">localhost</tt> when connecting. The latter indicates
      that the MySQL server runs on the same machine where MySQL
      Administrator runs.
     </p></li><li><p>
      <tt class="literal">Port</tt>: The port used for the connection to the
      MySQL server.
     </p></li></ul></div><p>
   </p></li><li><p>
    Server Information
   </p><p>
    Information about the MySQL server and the host where it is running.

    </p><div class="itemizedlist"><ul type="circle"><li><p>
      <tt class="literal">MySQL Version</tt>: The version of the MySQL server.
     </p></li><li><p>
      <tt class="literal">Network Name</tt>: The hostname of the machine where
      the MySQL server runs.
     </p></li><li><p>
      <i><span class="remark">
       [PD] "IP" is ambiguous because there are IP numbers and IP
       addresses.
      </span></i>

      <tt class="literal">IP</tt>: The IP number of the host where the MySQL
      server runs.
     </p></li></ul></div><p>
   </p></li><li><p>
    Client Information
   </p><p>
    Information about MySQL Administrator and the client host on which it is
    running.

    </p><div class="itemizedlist"><ul type="circle"><li><p>
      <tt class="literal">Version</tt>: The version of MySQL Administrator, and
      the version number of the MySQL client/server protocol.
     </p></li><li><p>
      <tt class="literal">Network name</tt>: The name of the host where MySQL
      Administrator runs.
     </p></li><li><p>
      <tt class="literal">IP</tt>: The IP number of the host where MySQL
      Administrator runs.
     </p></li><li><p>
      <tt class="literal">Operating System</tt>: Information about the
      operating system on which MySQL Administrator runs.
     </p></li><li><p>
      <tt class="literal">Hardware</tt>: Information about the hardware on
      which MySQL Administrator runs.
     </p></li></ul></div><p>
   </p></li></ul></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-service-control"></a>Chapter6.
   Service Control
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-service-control-introduction">6.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-service-control-start-stop-service">6.2. 
    Start/Stop Service
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-service-control-configure-service">6.3. 
    Configure Service
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-service-control-introduction"></a>6.1.
    Introduction
   </h2></div></div><div></div></div><p>
    This section allows you to start and stop the MySQL server you have
    connected to. At the moment, this is only possible if the server is
    running on the same machine where MySQL Administrator runs. In future
    releases, MySQL servers will have an Instance Manager that allows
    you to also start and stop MySQL servers on remote machines. Also,
    you can start and stop the server only if a service has been
    configured. If the server runs as a stand-alone application, the
    Service Control section is not available.
   </p><p>
    The Configure Service tab is available only for MySQL servers that
    run under Windows.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-service-control-start-stop-service"></a>6.2.
    Start/Stop Service
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Start/Stop Service</tt> tab displays the status of
    the MySQL service. This service starts and stops the MySQL server.
    Under <tt class="literal">Service Status</tt>, a text message indicates
    whether or not the service has been started. If the service is
    running, the button label is <span class="guibutton">Stop Server</span>
    button. Click it to stop the server. If the service is stopped, the
    button label is <span class="guibutton">Start Server</span>. Click it to
    start the service.
   </p><p>
    Under <tt class="literal">Log Messages</tt>, you will find messages that
    the MySQL server produces when it starts or stops. Messages produced
    by the server during startup look something like this:

</p><pre class="programlisting">
    Trying to start the server ...
    040119 18:33:41  InnoDB: Started
    MySql: ready for connections.
    Version: '4.0.16-max-nt-log'  socket: ''  port: 3306
    Server was started.
   </pre><p>

    When the server stops, it produces messages such as these:

</p><pre class="programlisting">
    Trying to stop the server ...
    040119 18:31:45  MySql: Normal shutdown
    040119 18:31:46  MySql: Forcing close of thread 11  user: 
'superuser'
    040119 18:31:46  MySql: Forcing close of thread 8  user: 'superuser'
    ...
    Server was stopped.
   </pre><p>

    The details and format of the messages might vary depending on the
    version of the MySQL server you are using and its configuration.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-service-control-configure-service"></a>6.3.
    Configure Service
   </h2></div></div><div></div></div><p>
    This tab allows configuration of the Windows service that starts and
    stops the MySQL server, as well as setting some options for the
    server itself. This tab is specific to MySQL servers running under
    operating systems of the Windows NT family, including Windows NT,
    Windows 2000, and Windows XP; it is not available for servers
    running under a different operating system. Obviously, you need to
    have a Windows service installed before you can configure it. The
    <a href="http://dev.mysql.com/doc/en/nt-start" target="_top">Starting
    MySQL as a Windows Service</a> section describes how to set up a
    Windows service.
   </p><p>
    Note that if you have more than one MySQL server running as a
    Windows service, you should run MySQL Administrator in
    <a href="#mysql-administrator-starting-configure-service" title="3.3.
    Configure-service Mode
   ">configure
    -service mode</a> to administer these services. In normal mode,
    you can only administer the Windows service listed first in the
    Windows service manager, no matter which server you are connected
    to.
   </p><p>
    Note that the settings in the <span class="guilabel">Server Features</span>
    group take effect only after restarting the MySQL server.
   </p><p>
    The following settings are available:

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      Service Settings

      </p><div class="itemizedlist"><ul type="circle"><li><p>
        <tt class="literal">Launch MySQL server automatically</tt>: If
        checked, the Windows service starts the MySQL server
        automatically on operating system startup.
       </p></li><li><p>
        <tt class="literal">Display Name</tt>: The display name of the Windows
        service (not the service name!) as it will appear in the Windows
        services manager when displaying the properties of that service.
       </p></li><li><p>
        <tt class="literal">Service Description</tt>: The description of the
        Windows service as it will appear in the Windows services
        manager.
       </p></li></ul></div><p>
     </p></li><li><p>
      Option File

      </p><div class="itemizedlist"><ul type="circle"><li><p>
        <tt class="literal">Config Filename</tt>:

        <i><span class="remark">
         [SH] Mike: "Config" is ugly. Suggestion: Filename
        </span></i>



        <i><span class="remark">
         [PD] Right. Don't use truncated words like Config in labels.
         Should either be written out, or, if that's too long, try to
         pick a different term.
        </span></i>

        You can enter the pathname of the server option file. MySQL will
        enter that information in the Windows registry, and the Windows
        service starting the MySQL server will use that file, rather
        than the default file (<tt class="literal">c:\<i class="replaceable"><tt>windows
        installation directory</tt></i>\my.ini</tt>).
        <span class="emphasis"><em>Note that this is available for MySQL servers as of
        version 4.0.3 only.</em></span> Details about the server option
        files can be found in the
        <a href="http://dev.mysql.com/doc/en/windows-prepare-environment" target="_top">Preparing
        the Windows MySQL Environment</a> section.

        <i><span class="remark">
         [PD] If this file is passed to the server as the
         --defaults-option (which I suspect is the case), the server
         will read only the [mysqld] option group in the file.
        </span></i>
       </p></li><li><p>
        <tt class="literal">Section Name</tt>:

        <i><span class="remark">
         [SH] FILL IN
        </span></i>

        Setting a value other than <tt class="literal">mysqld</tt> is most
        useful when running multiple servers; see
        <a href="http://dev.mysql.com/doc/en/multiple-windows-servers" target="_top">Running
        Multiple Servers on Windows</a>.

        <i><span class="remark">
         [SH] This is likely to change; need to document the changed
         behaviour.
        </span></i>
       </p></li></ul></div><p>
     </p></li><li><p>
      Server Features
     </p><p>
      <span class="emphasis"><em>Note that all server features will only take effect
      after the MySQL server has been restarted.</em></span>

      </p><div class="itemizedlist"><ul type="circle"><li><p>
        <tt class="literal">Support for InnoDB</tt>: If checked, the MySQL
        server is started with support for InnoDB tables. If unchecked,
        it doesn't start the InnoDB storage engine; this saves memory,
        but InnoDB tables cannot be used. If this checkbox is unchecked
        and greyed out, it means that your MySQL server isn't compiled
        with support for InnoDB tables. (This is, for example, true for
        some versions that run under a commercial license.) You can find
        more information on InnoDB tables in the
        <a href="http://dev.mysql.com/doc/en/table-types" target="_top">MySQL Table
        Types</a> section.
       </p><p>
        <span class="emphasis"><em>Be careful when disabling this option! If any
        databases on the MySQL server contain InnoDB tables, disabling
        this option makes those tables inaccessible.</em></span>
       </p></li><li><p>
        <tt class="literal">Support for BDB</tt>: If checked, the MySQL server
        is started with support for BDB tables. If unchecked, it doesn't
        start the BDB storage engine; this saves memory, but BDB tables
        cannot be used. If this checkbox is unchecked and greyed out, it
        means that your MySQL server isn't compiled with support for BDB
        tables. (This is, for example, true for non-max versions.) You
        can find more information on BDB tables in the
        <a href="http://dev.mysql.com/doc/en/table-types" target="_top">MySQL
        Table Types</a> section.
       </p><p>
        <span class="emphasis"><em>Be careful when disabling this option! If any
        databases on the MySQL server contain BDB tables, disabling this
        option makes those tables inaccessible.</em></span>
       </p></li><li><p>
        <tt class="literal">Named Pipes</tt>: On operating systems of the
        Windows NT family, including Windows NT, Windows 2000, and
        Windows XP, you may use named pipes to connect to a MySQL server
        running on the local machine, rather than connecting via TCP/IP.
        If this option is checked, named pipe connections are allowed.
        Note that named pipes are slower than TCP/IP in many Windows
        configurations. See the
        <a href="http://dev.mysql.com/doc/en/windows-select-server" target="_top">Selecting
        a Windows Server</a> section for details.
       </p></li><li><p>
        <tt class="literal">Debug Information (slow)</tt>: If checked, the
        MySQL server is started with an option that allows for easier
        debugging of problems. Using this option slows down the server
        significantly, so it is recommended only for debugging purposes.
        If the MySQL server has not been compiled with debugging
        support, this option is greyed out. See the
        <a href="http://dev.mysql.com/doc/en/command-line-options" target="_top"><span><b class="command">mysqld</b></span>
        Command-line Options</a> section for details.
       </p></li><li><p>
        <tt class="literal">Path to Binary</tt>: Contains the pathname of the
        MySQL server binary file as it is listed in the Windows service
        manager (for example
        <tt class="literal">c:\mysql\bin\mysqld-max-nt</tt>). Note that the
        the Windows service manager does not display the
        <tt class="literal">.exe</tt> extension.
       </p></li></ul></div><p>
     </p></li></ul></div><p>
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-startup-variables"></a>Chapter7.
   Startup Variables
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-startup-variables-introduction">7.1. 
    Introduction
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-startup-variables-introduction"></a>7.1.
    Introduction
   </h2></div></div><div></div></div><p>
    This section allows you to set variables that the MySQL server reads
    on startup. These variables are stored in the option file of the
    server. On Windows, the option file is called
    <tt class="literal">my.ini</tt>, and it is located in the Windows
    installation directory (for example,
    <tt class="literal">C:\WinNT\my.ini</tt>). Note that it can alternatively
    be stored in <tt class="literal">C:\</tt>, in which case it is named
    <tt class="literal">my.cnf</tt>. Also note that there can be more than one
    option file. On operating systems other than Windows, the option
    file is called <tt class="literal">my.cnf</tt>, regardless where it
    resides. On Windows, MySQL Administrator allows you to store the option
    file in any location you specify. You can find more information on
    the MySQL option files in the
    <a href="http://dev.mysql.com/doc/en/option-files" target="_top">Option
    Files</a> section.
   </p><p>
    <span class="emphasis"><em>Note that the server reads variables stored in the option
    files only at server startup. After changing an option file, you
    must restart the server for the changes to take effect. You can do
    this using the <span class="guibutton">Stop Server</span> and
    <span class="guibutton">Start Server</span> buttons in the
    <a href="#mysql-administrator-service-control-start-stop-service" title="6.2.
    Start/Stop Service
   ">Service
    Control</a> section.</em></span>
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-server-connections"></a>Chapter8.
   Server Connections
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-server-connections-introduction">8.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-connections-threads">8.2. 
    Threads
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-connections-user-connections">8.3. 
    User Connections
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-server-connections-introduction"></a>8.1.
    Introduction
   </h2></div></div><div></div></div><p>
    This section allows you to view and manage the current connections
    to the server (also called threads). If you have the
    <tt class="literal">PROCESS</tt> privilege, you can see all threads. If
    you have the <tt class="literal">SUPER</tt> privilege, you can also
    terminate threads other than your own. (Note that the
    <tt class="literal">SUPER</tt> privilege is available for MySQL servers as
    of version 4.0.3 only.) Otherwise, you can see your own threads
    only. You can find more information about threads in the
    <a href="http://dev.mysql.com/doc/en/show-processlist" target="_top"><tt class="literal">SHOW
    PROCESSLIST</tt></a> section. For more information on the
    <tt class="literal">PROCESS</tt> and the <tt class="literal">SUPER</tt>
    privilege (and other available privileges as well), see
    <a href="http://dev.mysql.com/doc/en/privileges-provided" target="_top">Privileges
    Provided by MySQL</a>.
   </p><p>
    Note that you will see an additional thread for the user under which
    you are connected when you have clicked the
    <a href="#mysql-administrator-health" title="Chapter10.
   Health
  ">Health</a>
    section within your current MySQL Administrator session. The values
    displayed in that section are retrieved from the MySQL server via a
    separate connection.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-server-connections-threads"></a>8.2.
    Threads
   </h2></div></div><div></div></div><p>
    This tab allows you to view all connections to the server (threads).
    Initially, those are sorted by their <tt class="literal">PID</tt> (MySQL
    process identification number), but you can change that order by
    clicking on the appropriate headings (<tt class="literal">User</tt>,
    <tt class="literal">Host</tt>, etc.).

    <i><span class="remark">
     [SH] This is not implemented yet.
    </span></i>

    You can select a thread by clicking on it. You can select more than
    one thread using mouse or keyboard.
   </p><p>
    To reload the process list from the server, press the
    <span class="guibutton">Refresh</span> button.
   </p><p>
    If you have selected one or more threads, you can terminate them by
    clicking the <span class="guibutton">Kill Thread</span> button, or by
    right-clicking on that thread. Remember that you need the
    <tt class="literal">PROCESS</tt> privilege to see threads other than your
    own, and the <tt class="literal">SUPER</tt> privilege to kill threads
    other than your own. Furthermore, note that MySQL Administrator imposes
    a restriction that prevents you from terminating your own threads.
    On Windows, using the <span class="guibutton">Kill Thread</span> button on
    your own threads does not have an effect; on Linux, that button is
    disabled when selecting your own threads.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-server-connections-user-connections"></a>8.3.
    User Connections
   </h2></div></div><div></div></div><p>
    This tab displays all connections to the server (threads), but in a
    different way than the
    <a href="#mysql-administrator-server-connections-threads" title="8.2.
    Threads
   ">Threads</a>
    tab does: You will rather see users, not individual threads in the
    first place. The number of connections a user has currently
    established to the MySQL server is listed under
    <tt class="literal">Num.</tt>. Right-clicking on a username and selecting
    <span class="guimenu">Show User Info</span> will also display the
    <tt class="literal">Full Name</tt> and the <tt class="literal">Description</tt>,
    as specified in the <tt class="literal">User Information</tt> tab of the
    <a href="#mysql-administrator-user-administration-user-information" title="9.3.
    User Information
   ">User
    Administration</a> section. Initially, users are sorted by their
    MySQL <tt class="literal">Username</tt>, but you can change that order by
    clicking on the appropriate headings (<tt class="literal">Num.</tt>,
    <tt class="literal">Full Name</tt>, or <tt class="literal">Description</tt>).

    <i><span class="remark">
     [SH] Not implemented yet.
    </span></i>

    Clicking on a username will display the individual threads of that
    user in the lower box of that tab, ordered by
    <tt class="literal">PID</tt>. Likewise, you can change that order by
    clicking on the appropriate headings.

    <i><span class="remark">
     [SH] Not implemented yet.
    </span></i>
   </p><p>
    Clicking on a user will enable the <span class="guibutton">Kill User</span>
    button, which allows you to terminate all threads of that user with
    a single click. That command is also available by right-clicking on
    the username. Clicking on an individual thread in the lower box will
    enable the <span class="guibutton">Kill Thread</span> button, which is used
    to terminate a connection. That command is available by
    right-clicking on a thread, too.
   </p><p>
    To reload the user list from the server, press the
    <span class="guibutton">Refresh</span> button.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-user-administration"></a>Chapter9.
   User Administration
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-user-administration-introduction">9.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-user-accounts">9.2. 
    User Accounts
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-user-information">9.3. 
    User Information
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-global-privileges">9.4. 
    Global Privileges
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-schema-privileges">9.5. 
    Schema Privileges
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-user-administration-table-column-privileges">9.6. 
    Table Column Privileges
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-user-administration-introduction"></a>9.1.
    Introduction
   </h2></div></div><div></div></div><p>
    This section allows you to administer existing users, add new users,
    and delete existing users. For more information on the MySQL user
    account management and privilege system, see the
    <a href="http://dev.mysql.com/doc/en/user-account-management" target="_top">MySQL
    User Account Management</a> section.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-user-administration-user-accounts"></a>9.2.
    User Accounts
   </h2></div></div><div></div></div><p>
    Existing users are listed in the lower left area of the
    <a href="#mysql-administrator-sidebar" title="4.2.
    Sidebar
   ">sidebar</a>. If
    there are many user accounts on your MySQL server, the field with
    the magnifying-glass icon may be handy for filtering the users you
    are looking for. Typing in <tt class="literal">t</tt> or
    <tt class="literal">T</tt>, for example, will set the filter to users
    whose names begin with a <tt class="literal">t</tt>. The filter works in a
    case-insensitive fashion.
   </p><p>
    If you are an experienced MySQL user, you will notice that users are
    not listed the typical MySQL way
    (<tt class="literal"><i class="replaceable"><tt>user</tt></i>@<i class="replaceable"><tt>host
    </tt></i></tt>), but rather with their usernames only. If
    double-clicking on a username does not show subcategories for that
    user, this means that the user's privileges are not restricted to a
    specific host, or hosts. If there are subcategories, the user's
    privileges are restricted to a specific host, or set of hosts. You
    may assign various (and different) sets of privileges, depending on
    the host from which the user connects to the MySQL server. That
    concept is described in detail in the
    <a href="http://dev.mysql.com/doc/en/connection-access" target="_top">Access
    Control, Stage 1: Connection Verification</a> section.
   </p><p>
    <span class="emphasis"><em>Note that MySQL Administrator has a different concept of what
    a <tt class="literal">user</tt> is than MySQL has. In MySQL, a user is
    always identified by a
    <tt class="literal">username</tt>/<tt class="literal">host</tt> combination.
    This means that, for example, <tt class="literal">'brian'@'%'</tt> may be
    a user completely different from
    <tt class="literal">'brian'@'localhost'</tt>. The former might be
    <tt class="literal">Brian Miller</tt>, while the latter might be
    <tt class="literal">Brian Schultz</tt>. That distinction does not hold
    true for MySQL Administrator: User <tt class="literal">brian</tt> is always a
    particular user, no matter from which host he connects to the MySQL
    server. That said, <tt class="literal">'brian'@'%'</tt> may still have
    privileges different from
    <tt class="literal">'brian'@'localhost'</tt>.</em></span>
   </p><div class="figure"><a name="id4740653"></a><p class="title"><b>Figure9.1.
     User accounts
    </b></p><div><img src="images/user-accounts.png" alt="User accounts"></div></div><p>
    For example, you might have a user called
    <tt class="literal">superuser</tt>. If double-clicking on that username
    shows two subcategories, <tt class="literal">localhost</tt> and
    <tt class="literal">athena</tt>, this means that the user has a specific
    set of privileges if he/she connects from
    <tt class="literal">localhost</tt>, and a (probably different) set of
    privileges if he/she connects from <tt class="literal">athena</tt>.
   </p><p>
    Right-clicking on a username, or on one of the subcategories a user
    might have, provides access to the following commands:

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      <tt class="literal">Add a new User</tt>: Selecting this command adds a
      new user with the default name <tt class="literal">New User</tt> to the
      user list. You will have to fill in at least a username in the
      <tt class="literal">MySQL User</tt> field of the
      <a href="#mysql-administrator-user-administration-user-information" title="9.3.
    User Information
   ">User
      Information</a> tab, which, after applying this change, will
      also rename that user in the user accounts list.
     </p></li><li><p>
      <tt class="literal">Add a Host from which the User can connect</tt>:

      <i><span class="remark">
       [SH] Mike: Remove "a" -&gt; Add Host.
      </span></i>

      Allows you to specify a host from which the user can connect. This
      command is unavailable if you right-click on a subcategory.
     </p></li><li><p>
      <tt class="literal">Remove Host from which the User can connect</tt>:
      Allows you to remove a host from which the user can connect. This
      command is unavailable unless you right-click on a subcategory.
     </p></li><li><p>
      <tt class="literal">Clone User</tt>: Makes a copy of the selected user,
      including all subcategories. The new user is called <tt class="literal">New
      User</tt> until you specify another name in the
      <tt class="literal">MySQL User</tt> field of the
      <a href="#mysql-administrator-user-administration-user-information" title="9.3.
    User Information
   ">User
      Information</a> tab. With that command, you can therefore
      create a user with identical privileges.

      <i><span class="remark">
       [SH] Not yet implemented.
      </span></i>
     </p></li><li><p>
      <tt class="literal">Delete User</tt>: Allows you to delete the selected
      user. You will be prompted to confirm that you really want to
      delete that user.
     </p></li><li><p>
      <tt class="literal">Refresh User List</tt>: Rereads the user list from
      the MySQL server. This is helpful when other users (on other
      connections) are editing user accounts. Note that selecting that
      command will collapse all subcategories.
     </p></li></ul></div><p>
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-user-administration-user-information"></a>9.3.
    User Information
   </h2></div></div><div></div></div><p>
    The fields in this tab are unavailable unless you either click on a
    username in the
    <a href="#mysql-administrator-user-administration-user-accounts" title="9.2.
    User Accounts
   ">Us
    er Accounts</a> area of the
    <a href="#mysql-administrator-sidebar" title="4.2.
    Sidebar
   ">sidebar</a>, or
    create a new user in that sidebar or using the <span class="guibutton">New
    User</span> button on this tab. In the former case, the fields
    are filled with the information stored for that user, in the latter
    case, all fields are empty.
   </p><p>
    Note that all fields will be stored only when you click the
    <span class="guibutton">Apply Changes</span> button. If you don't want to
    save your changes, click the <span class="guibutton">Discard Changes</span>
    button.
   </p><div class="figure"><a name="id4740913"></a><p class="title"><b>Figure9.2.
     User Information tab
    </b></p><div><img src="images/user-information.png" alt="User Information tab"></div></div><p>
    The values you enter in the fields of this tab are stored on the
    MySQL server. The fields in the <span class="guilabel">Login
    Information</span> group of this tab are stored in the
    <tt class="literal">user</tt> table of the <tt class="literal">mysql</tt>
    database, while the fields in the <span class="guilabel">Additional
    Information</span> group are stored in the
    <tt class="literal">user-info</tt> table of the <tt class="literal">mysql</tt>
    database. The latter table is created the first time you add a new
    user, or change an existing user. Its contents may look like this:

</p><pre class="programlisting">
    mysql&gt; SELECT * FROM mysql.user-info \G
           *************************** 1. row ************
                          User: superuser
                     Full-name: Stefan Hinz
                   Description: MySQL Documentation Team
                         Email: stefan@mysql.com
           Contact-information: Phone: +49 30 123456789
                                Fax: +49 30 987654321
                                ICQ: 123456789
                          Icon:
   </pre><p>

    </p><div class="itemizedlist"><ul type="disc"><li><p>
      Login Information

      </p><div class="itemizedlist"><ul type="circle"><li><p>
        <tt class="literal">MySQL User</tt>: Username that is specified when
        connecting to the MySQL server. Note that this username has
        nothing to do with usernames you might use elsewhere on your
        operating system. It is recommendable not to use special
        characters or spaces for that username.
       </p></li><li><p>
        <tt class="literal">Password</tt>: Password that is specified when
        connecting to the MySQL server. Note that this password has
        nothing to do with passwords you might use elsewhere on your
        operating system. It is recommendable not to use special
        characters or spaces for that password. It is, however,
        recommendable to use non-trivial passwords. A very trivial
        password might be <tt class="literal">abcde</tt>, while a non-trivial
        password might be <tt class="literal">lEtusMak3iThartdoGesz</tt>. Note
        that it is not mandatory to specify a password, although it is
        highly recommendable to do so.
       </p></li><li><p>
        <tt class="literal">Confirm Password</tt>: Fill in the password once
        again to make sure you do not accidentally introduce a typo.
       </p></li></ul></div><p>
     </p></li><li><p>
      Additional Information
     </p><p>
      All information specified here is optional.

      </p><div class="itemizedlist"><ul type="circle"><li><p>
        <tt class="literal">Full Name</tt>: As opposed to the username in
        <tt class="literal">MySQL User</tt>, the full name may contain any
        characters, including spaces.
       </p></li><li><p>
        <tt class="literal">Description</tt>: Additional description of user.
       </p></li><li><p>
        <tt class="literal">Email</tt>: Email address of user.
       </p></li><li><p>
        <tt class="literal">Contact Information</tt>: More contact
        information, like postal address, or messenger information.

        <i><span class="remark">
         [SH] Mike: messager -&gt; messenger
        </span></i>
       </p></li><li><p>
        <tt class="literal">Icon</tt>: Rather than using the default icon, you
        may select a different icon by pressing the <span class="guibutton">Load from
        Disk</span> button. You can either use one of the buttons
        that are shipped with MySQL Administrator

        <i><span class="remark">
         [SH] Mike: In which directory?
        </span></i>

        , or use an icon of your own. In the latter case, be aware that
        the icon has to be exactly 48 by 48 pixels in size, and its file
        format has to be <tt class="literal">PNG</tt> (portable network
        graphics).
       </p></li></ul></div><p>
     </p></li></ul></div><p>
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-user-administration-global-privileges"></a>9.4.
    Global Privileges
   </h2></div></div><div></div></div><p>
    This tab is available only if the <tt class="literal">Show Global
    Privileges</tt> checkbox in the
    <a href="#mysql-gui-options-administrator" title="17.5.
    Administrator
   ">Admin
    istrator section of the Options dialog</a> has been checked.
   </p><p>
    Under <span class="guilabel">Assigned Privileges</span>, you find the global
    privileges assigned to the selected user. For more information about
    those privileges, see the
    <a href="http://dev.mysql.com/doc/en/privileges-provided" target="_top">Privileges
    Provided by MySQL</a> section. <span class="emphasis"><em>Global</em></span> means
    that those privileges apply to the MySQL server in general (like the
    <tt class="literal">Shutdown</tt> privilege), or to all databases on the
    server (like the <tt class="literal">SELECT</tt> privilege).
   </p><p>
    Privileges not assigned to the user are listed under
    <span class="guilabel">Available Privileges</span>. You can remove privileges
    by selecting them in the left box, and then clicking the <span class="guibutton">
    &gt; </span> button. Removed privileges will appear in the
    <span class="guilabel">Available Privileges</span> box. You can assign
    privileges by selecting them in the <span class="guilabel">Available
    Privileges</span> box, and then clicking the <span class="guibutton"> &lt;
    </span> button.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-user-administration-schema-privileges"></a>9.5.
    Schema Privileges
   </h2></div></div><div></div></div><p>
    This tab allows you to grant privileges on a schema level. In MySQL,
    a schema is the same as a database. To grant privileges for a
    specific database, click on the database name in the left box. (You
    cannot select more than one database at a time.)
   </p><p>
    Privileges not assigned to the user are listed under
    <span class="guilabel">Available Privileges</span>. You can remove privileges
    by selecting them in the left box, and then clicking the <span class="guibutton">
    &gt; </span> button. Removed privileges will appear in the
    <span class="guilabel">Available Privileges</span> box. You can assign
    privileges by selecting them in the <span class="guilabel">Available
    Privileges</span> box, and then clicking the <span class="guibutton"> &lt;
    </span> button.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-user-administration-table-column-privileges"></a>9.6.
    Table Column Privileges
   </h2></div></div><div></div></div><p>
    This tab is available only if the <tt class="literal">Show Table/Column
    Privileges</tt> checkbox in the
    <a href="#mysql-gui-options-administrator" title="17.5.
    Administrator
   ">Admin
    istrator section of the Options dialog</a> has been checked. It
    allows you to grant privileges on a table level or on a column
    level.
   </p><p>
    To access the tables, double-click on the schema (database) name
    containing that table. You will not see and cannot grant privileges
    on a schema level in this tab; if you want to do that, use the
    <a href="#mysql-administrator-user-administration-global-privileges" title="9.4.
    Global Privileges
   ">Global
    Privileges</a> tab instead. Also, you cannot select more than one
    table at a time.
   </p><p>
    If you want to grant privileges on a column level, double-click on
    the table name; this will give you access to its columns. You cannot
    select more than one column at a time.
   </p><p>
    Privileges not assigned to the user are listed under
    <span class="guilabel">Available Privileges</span>. You can remove privileges
    by selecting them in the left box, and then clicking the <span class="guibutton">
    &gt; </span> button. Removed privileges will appear in the
    <span class="guilabel">Available Privileges</span> box. You can assign
    privileges by selecting them in the <span class="guilabel">Available
    Privileges</span> box, and then clicking the <span class="guibutton"> &lt;
    </span> button.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-health"></a>Chapter10.
   Health
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-health-introduction">10.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-connection-health">10.2. 
    Connection Health
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-memory-health">10.3. 
    Memory Health
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-creating-graphs">10.4. 
    Creating Custom Health Graphs
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-status-variables">10.5. 
    Status Variables
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-health-system-variables">10.6. 
    System Variables
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-health-introduction"></a>10.1.
    Introduction
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Health</tt> section of MySQL Administrator allows you
    to graphically monitor the real-time status of your MySQL server. A
    selection of pre-made status graphs are available, and you can
    easily create your own status graphs and organize them into custom
    pages and groups.
   </p><p>
    The default graphs provide graphical information about the MySQL
    server's current performance, load, and memory usage. Additional
    pages list all server variables, divided into pages for status
    variables and system variables. Note that clicking on the status
    pages will open an additional connection to the MySQL server, which
    you can see when viewing threads and users in the
    <a href="#mysql-administrator-server-connections" title="Chapter8.
   Server Connections
  ">Server
    Connections</a> section.
   </p><p>
    We'll begin by covering the different pre-made status graphs, and
    then describe how to create your own status graphs yourself. Finally
    we'll describe the pages in the <tt class="literal">Health</tt> section
    dedicated to the various status and system variables.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-health-connection-health"></a>10.2.
    Connection Health
   </h2></div></div><div></div></div><p>
    This tab provides information about connections to the MySQL server.
    The following three pre-made graphs are displayed:
   </p><div class="itemizedlist"><ul type="disc"><li><p>
     <tt class="literal">Connection Usage</tt>: Displays a percentage of the
     maximum number of simultaneous clients allowed (<tt class="literal">threads
     connected</tt> / <tt class="literal">max_connections</tt>). If this
     value gets close to 100%, it could indicate that you should
     increase the value of max_connections, which you can do in the
     <a href="#mysql-administrator-startup-variables" title="Chapter7.
   Startup Variables
  ">Startup
     Variables</a> section. The maximum number of connections since
     MySQL Administrator was loaded is also shown. For more information on
     server connections, see the
     <a href="http://dev.mysql.com/doc/en/show-variables" target="_top"><tt class="literal">SHOW
     VARIABLES</tt></a> and
     <a href="http://dev.mysql.com/doc/en/too-many-connections" target="_top"><tt class="literal">Too
     many connections</tt> Error</a> sections of the reference
     manual.
    </p></li><li><p>
     <tt class="literal">Traffic</tt>: This is a representation of the
     <tt class="literal">bytes_sent</tt> status variable. This does not
     represent total bytes sent since server startup, but instead
     represents the current number of bytes sent (the
     <tt class="literal">bytes_sent</tt> variable is a cumulative total). The
     initial maximum value of the graph is 102400, this maximum value
     will be automatically increased as needed.
    </p></li><li><p>
     <tt class="literal">Number of SQL Queries</tt>: This is a representation
     os the <tt class="literal">com_select</tt> status variable. This does not
     represent total queries since server startup, but instead
     represents the current number of queries (the
     <tt class="literal">com_select</tt> variable is a cumulative total). The
     initial maximum value of the graph is 10, this maximum value will
     be automatically increased as needed.
    </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-health-memory-health"></a>10.3.
    Memory Health
   </h2></div></div><div></div></div><p>
    This tab provides information about memory caches that affect the
    performance of the MySQL server. For each cache, there is a display
    that shows the current hitrate or usage of the cache, and a display
    that shows the hitrate or usage for the last few minutes.
   </p><div class="itemizedlist"><ul type="disc"><li><p>
     <tt class="literal">Query Cache Hitrate</tt>: When in use, the query
     cache of the MySQL server stores the text of a
     <tt class="literal">SELECT</tt> query together with the corresponding
     result that was sent to the client. If an identical query is later
     received, the server will retrieve the results from the query cache
     rather than parsing and executing the same query again. The hitrate
     indicates the ratio of queries that were cached and queries that
     were not cached. The higher the hitrate, the better the performance
     of the server regarding <tt class="literal">SELECT</tt> queries. See the
     <a href="http://dev.mysql.com/doc/en/query-cache" target="_top">MySQL Query
     Cache</a> section for details.
    </p></li><li><p>
     <tt class="literal">Key Efficiency</tt>: The horizontal bar graph
     indicates how much of the allocated key buffer is in use. If a
     fairly large percentage of the key buffer is in use you may wish to
     increase the <tt class="literal">key_cache_size</tt> setting in the
     <a href="#mysql-administrator-startup-variables" title="Chapter7.
   Startup Variables
  ">Startup
     Variables</a> section. The line graph is an indication of the
     number of <tt class="literal">key_read_requests</tt> that resulted in
     actual <tt class="literal">key_reads</tt>. The higher the hitrate the
     more effective your key buffer is. A low hitrate can indicate that
     you need to increate the size of your keycache.
    </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-health-creating-graphs"></a>10.4.
    Creating Custom Health Graphs
   </h2></div></div><div></div></div><p>
    While the pre-made status graphs can provide you with informatin of
    the current state of your MySQL server, there may be additionally
    information that you wish to visually track. The MySQL Administrator
    <tt class="literal">Health</tt> section allows you to add additional tabs
    and graphs to track any information that is contained within the
    <a href="#mysql-administrator-health-status-variables" title="10.5.
    Status Variables
   ">Status
    Variables</a>.
   </p><p>
    The first step in creating custom health graphs is to create a new
    page in the <tt class="literal">Health</tt> section to store your graphs.
    To create a new page right-click anywhere in the working area and
    choose the <span class="guimenu">Add a Page</span> option. You will be
    prompted for a page name and description and a new page will be
    created.
   </p><p>
    Once you have created a new page, you will need to create a group.
    All graphs are located within groups. For example, the <tt class="literal">Key
    buffer usage</tt> and <tt class="literal">Key buffer hitrate</tt>
    graphs are both located within a group titled <tt class="literal">Key
    Efficiency</tt>. To create a group, right-click within your
    newly created page and choose the <span class="guimenu">Add a Group</span>
    option.
   </p><p>
    to create a custom graph, right-click within a group and choose the
    <span class="guimenu">Add a graph</span> option. The following dialog will
    appear:
   </p><div class="figure"><a name="id4741892"></a><p class="title"><b>Figure10.1.
     The Graph Settings dialog
    </b></p><div><img src="images/graph-settings.png" alt="The Graph Settings dialog"></div></div><p>
    Choose a caption that describes what you will be graphing, and then
    choose your graph type. The caption is optional and will only be
    displayed if the The <span class="guilabel">Display Caption</span> box is
    checked. After choosing a caption you will need to choose a graph
    type. The <tt class="literal">Line-Graph</tt> is appropriate for showing
    trends over time, while the <tt class="literal">Bar-Graph</tt> option will
    be more appropriate for showing percentage information.
   </p><p>
    The data on your graph is set using the <tt class="literal">Value
    Formula</tt>. You can create a formula using any of the
    variables available in the
    <a href="#mysql-administrator-health-status-variables" title="10.5.
    Status Variables
   ">Status
    Variables</a> and
    <a href="#mysql-administrator-health-system-variables" title="10.6.
    System Variables
   ">System
    Variables</a> tabs. To use the value of a variable, wrap the
    variable name in square brackets (i.e.
    <tt class="literal">[com_select]</tt>), if you want the relative value of
    the variable prepend the square brackets with a <tt class="literal">^</tt>
    character.
   </p><p>
    For example, if we wanted to graph the percentage of temporary
    tables that were created on disk we could use the following formula:
   </p><pre class="programlisting">
  [created_tmp_disk_tables] / [created_tmp_tables]
  </pre><p>
    If we wanted to track the number of temporary tables created on a
    continious basis, we could use the following as our formula:
   </p><pre class="programlisting">
  ^[created_tmp_tables]
  </pre><p>
    After creating your formula, select the <tt class="literal">Value
    Unit</tt> that best represents your data. You can choose from
    <tt class="literal">Percentage</tt>, <tt class="literal">Count</tt>,
    <tt class="literal">Byte</tt>, and <tt class="literal">Seconds</tt>. In our
    examples we would have used <tt class="literal">Percentage</tt> for the
    first example, and <tt class="literal">Count</tt> for the second. You can
    also assign a caption to the value.
   </p><p>
    Once your formula is assigned you should configure the <tt class="literal">Max.
    Value</tt> and <tt class="literal">Min. Value</tt> for the graph, so
    that your data is spread evenly across your graph. You can set
    arbitrary values based on your estimates of how large the values
    will grow, and check the <span class="guimenu">Autoextend Max. Value</span>
    option to allow MySQL Administrator to automatically increase the
    <tt class="literal">Max Value</tt> setting automatically to prevent your
    data from extending off of your graph.
   </p><p>
    You can also set the <tt class="literal">Max. Value</tt> option by way of
    a formula assigned in the <span class="guilabel">Max Formular</span> field.
    The same syntax applies in this field as applies in the
    <span class="guilabel">Value Formula</span> field. For example, if you were
    creating a bar graph tracking the number of temporary disk tables
    created, you could use <tt class="literal">[created_tmp_disk_tables]</tt>
    as the <span class="guilabel">Value Formula</span> and
    <tt class="literal">[created_tmp_tables]</tt> as the <span class="guilabel">Max.
    Formular</span>.
   </p><i><span class="remark">
    [MH] Max FormulaR? Lets get this fixed.
   </span></i></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-health-status-variables"></a>10.5.
    Status Variables
   </h2></div></div><div></div></div><p>
    This tab provides information about the status variables of the
    MySQL server. In the left box of the working area, you find
    categories and subcategories. Double-click on a category name to
    expand or collapse its subcategories.
   </p><p>
    For each category, and each subcategory, the status variables are
    listed in the right box of the working area, together with their
    values, and with a short explanation. The status variables are
    described in detail in the
    <a href="http://dev.mysql.com/doc/en/show-status" target="_top"><tt class="literal">SHOW
    STATUS</tt></a> section of the reference manual.
   </p><p>
    Use the <span class="guibutton">Refresh</span> button to make
    MySQL Administrator retrieve the variables and their values once again.
   </p><p>
    Right-clicking in the right box allows you to copy variables to the
    clipboard.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-health-system-variables"></a>10.6.
    System Variables
   </h2></div></div><div></div></div><p>
    This tab provides information about the system variables of the
    MySQL server. In the left box of the working area, you can find
    categories and subcategories. Double-click on a category name to
    expand or collapse its subcategories.
   </p><p>
    For each category, and each subcategory, the system variables are
    listed in the right box of the working area, together with their
    values, and with a short explanation. The system variables are
    described in detail in the
    <a href="http://dev.mysql.com/doc/en/show-variables" target="_top"><tt class="literal">SHOW
    VARIABLES</tt></a> section of the reference manual.
   </p><p>
    System variables that can be set at runtime are marked as editable,
    that is they are prefixed with an icon different from the variables
    that cannot be set at runtime. Double-clicking on editable variables
    will open a dialog where you can specify another value for the
    variable. The changes you make will take effect as soon as you click
    the <span class="guibutton">OK</span> button in that dialog. Click
    <span class="guibutton">Abort</span> if you want to keep the current value.
    Changes made in this manner will only persist until the server is
    restarted, after which the server will revert to it's startup
    settings. In MySQL Administrator, system variables are set on a global
    level only. Note that you need appropriate privileges to change
    variables globally. You can find more information on global
    variables in the
    <a href="http://dev.mysql.com/doc/en/set-option" target="_top"><tt class="literal">SET</tt>
    Syntax</a> section.
   </p><p>
    Use the <span class="guibutton">Refresh</span> button to make MySQL
    Administrator retrieve the variables and their values once again.
   </p><p>
    Right-clicking in the right box allows you to copy variables to the
    clipboard.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-server-logs"></a>Chapter11.
   Server Logs
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-server-logs-introduction">11.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-logs-error-log">11.2. 
    Error Log
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-logs-slow-log">11.3. 
    Slow Log
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-server-logs-general-log">11.4. 
    General Log
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-server-logs-introduction"></a>11.1.
    Introduction
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Server Logs</tt> section provides easy access to
    the various log files generated by the MySQL server. You can access
    the server's error log, slow query log, and general log using this
    section.
   </p><p>
    This section has one tab for each of the log files, and each tab is
    split into two boxes. Above the boxes, there is a bar which allows
    you to navigate through larger log files by breaking the log file
    into individual pages. Clicking in the bar will display the
    individual pages. The light blue area represents the portion of the
    log file you are currently viewing.
   </p><div class="figure"><a name="id4742349"></a><p class="title"><b>Figure11.1.
     Displaying entries from the middle of the General Log
    </b></p><div><img src="images/server-logs-general-log.png" alt="Displaying entries from the middle of the General Log"></div></div><p>
    You can only view log files that are stored on the machine where
    MySQL Administrator is running, you cannot view log files on a remote
    machine.
   </p><p>
    Also note that some tabs may be disabled. If a tab is disabled it
    indicates that the log file in question has not been enabled on the
    MySQL server. You can enable the various log files in the
    <a href="#mysql-administrator-startup-variables" title="Chapter7.
   Startup Variables
  ">Startup
    Variables</a> section.
   </p><p>
    The left box (labeled <tt class="literal">Events of page
    <i class="replaceable"><tt>x</tt></i> /
    <i class="replaceable"><tt>y</tt></i></tt>) displays the major events
    that have occured on the current page of the log file. The right box
    (labeled <tt class="literal">Page Content</tt>) displays the detailed
    lines of the log file. By clicking on an event in the left box, the
    first detailed entry of the event will be highlighted in the right
    box.
   </p><p>
    In addition to the log file tabs, the <tt class="literal">Server Logs</tt>
    section has four action buttons for managing log information:
   </p><div class="itemizedlist"><ul type="disc"><li><p>
     <span class="guibutton">Open Other File</span> will allow you to open a log
     file other than the currently active log file. This can be useful
     in situations where you rotate your log files as it allows you to
     open log files that have been rotated out of active use.
    </p></li><li><p>
     <span class="guibutton">Search</span> opens a dialog where you can specify
     a search term to look for in the log file. If it's found, it will
     be marked as selected in the right box. This command is also
     available by right-clicking in the right box and choosing the
     <span class="guimenu">Search ...</span> option.
    </p></li><li><p>
     <span class="guibutton">Save Log Page</span> opens a dialog that allows you
     to specify the path and file name where the current page of the log
     file should be stored. By default, MySQL Administrator suggests
     <tt class="literal">ErrorLog.txt</tt>, <tt class="literal">SlowLog.txt</tt>, or
     <tt class="literal">GeneralLog.txt</tt> as a filename. Note that
     executing this command does not affect the actual log file in any
     way; it just creates a copy of the <span class="emphasis"><em>current</em></span> log
     file contents that you may store for documenting or analyzing. This
     command is also available by right-clicking in the right box and
     choosing the <span class="guimenu">Save log Page ...</span> option.
    </p></li><li><p>
     <span class="guibutton">Refresh</span> will reload the log files.
    </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-server-logs-error-log"></a>11.2.
    Error Log
   </h2></div></div><div></div></div><p>
    Displays the MySQL server's error log. The error log file contains
    information indicating when the MySQL server was started and stopped
    and also any critical errors found when running. For more
    information about that log file, see
    <a href="http://dev.mysql.com/doc/en/error-log" target="_top">The Error
    Log</a>.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-server-logs-slow-log"></a>11.3.
    Slow Log
   </h2></div></div><div></div></div><p>
    Displays the MySQL server's slow query log. If enabled (which you
    can do in the
    <a href="#mysql-administrator-startup-variables" title="Chapter7.
   Startup Variables
  ">Startup
    Variables</a> section), the MySQL server writes a log file
    containing all SQL commands that took more than a specific number of
    seconds to execute. (That number can be configured by the
    <tt class="literal">long-query-time</tt> variable; its default value is 10
    seconds.) The time to get the initial table locks are not counted as
    execution time. For more information about that log file, see
    <a href="http://dev.mysql.com/doc/en/slow-query-log" target="_top">The Slow
    Query Log</a>.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-server-logs-general-log"></a>11.4.
    General Log
   </h2></div></div><div></div></div><p>
    Displays the MySQL server's general query log. This log can be very
    useful when you suspect an error in a client and want to know
    exactly what the MySQL server thought the client sent to it. For
    more information about that log file, see
    <a href="http://dev.mysql.com/doc/en/query-log" target="_top">The General Query
    Log</a>.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-backup"></a>Chapter12.
   Backup
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-backup-introduction">12.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-backup-backup-project">12.2. 
    Backup Project
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-backup-advanced-options">12.3. 
    Advanced Options
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-administrator-backup-advanced-options-execution-method">12.3.1. 
     Backup Execution Method
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-backup-advanced-options-output-options">12.3.2. 
     Output File Options
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#mysql-administrator-backup-schedule">12.4. 
    Schedule
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-backup-introduction"></a>12.1.
    Introduction
   </h2></div></div><div></div></div><p>
    This section allows you to create backup projects, and to perform
    backups. This section will produce backup files that are plaintext
    and composed of multiple SQL statements that can be executed to
    restore your database, similar to the output generated by the
    <tt class="literal">mysqldump</tt> utility. For more information on
    <tt class="literal">mysqldump</tt>, see the
    <a href="http://dev.mysql.com/doc/en/mysqldump" target="_top"><tt class="literal">mysqldump
    </tt> section</a> of the reference manual.
   </p><p>
    Existing backup projects are listed in the lower left area of the
    <a href="#mysql-administrator-sidebar" title="4.2.
    Sidebar
   ">sidebar</a>. If there
    are many backup projects, the field with the magnifying-glass icon
    can be used to filter the projects you are looking for. Typing in
    <tt class="literal">t</tt> or <tt class="literal">T</tt>, for example, will set
    the filter to projects whose names begin with a
    <tt class="literal">t</tt>. The filter works in a case-insensitive
    fashion.
   </p><p>
    You can update the list of backup projects by right-clicking on a
    project and choosing the <span class="guimenu">Refresh Backup Projects</span>
    option from the drop-down menu. You can delete a backup project by
    right-clicking on the project and choosing the <span class="guimenu">Delete
    Backup Project(s)</span> option from the drop-down menu.
   </p><p>
    If you are not working from a previously saved backup project, click
    the <span class="guibutton">New Project</span> button to create a new backup
    project. You cannot begin configuring a backup operation without
    either loading an existing project or creating a new project.
   </p><p>
    Once you have configured your backup project, you can click the
    <span class="guibutton">Save Project</span> button to save your project for
    future use. To start your backup, click the <span class="guibutton">Execute
    Backup Now</span> button. You will be prompted for a path and
    filename for the backup file, after which the backup operation will
    begin.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-backup-backup-project"></a>12.2.
    Backup Project
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Backup Project</tt> tab allows you to set the name
    of your backup project and also determine what data will be backed
    up.
   </p><p>
    You can name your project by filling out a name in the
    <span class="guilabel">Project Name</span> field. If you have enabled the
    <tt class="literal">Add Date/Time to Backup Files</tt> option in the
    <tt class="literal">Administrator Options</tt> dialogue, then the date and
    time of the backup will be appended to the project name
    automatically. See

    <a href="#mysql-gui-options-administrator-backup" title="17.5.3.Backup">Section17.5.3, &#8220;Backup&#8221;</a>

    for more information on setting this option.
   </p><p>
    Specify a name that clearly denotes the project, such as
    <tt class="literal">Full Backup</tt> or <tt class="literal">World Only</tt>. The
    project name may contain arbitrary characters, including spaces.
   </p><p>
    To choose the databases and tables that will be backed up, select
    the database from the schemata list and click the
    <span class="guibutton">&gt;</span> button. Once the database is in the
    <tt class="literal">Backup Content</tt> list, you can un-check specific
    tables that you do not wish to back up.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-backup-advanced-options"></a>12.3.
    Advanced Options
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Advanced Options</tt> tab allows you to configure
    advanced options that affect the way the backup operation behaves.
    These include concurrency controls, backup type, and output
    formatting.
   </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-backup-advanced-options-execution-method"></a>12.3.1.
     Backup Execution Method
    </h3></div></div><div></div></div><p>
     The <tt class="literal">Backup Execution Method</tt> affects concurrency
     within the backup itself.
    </p><p>
     <tt class="literal">Lock all tables</tt> will cause all tables within the
     backup to be locked simultaneously to prevent writing. This will
     prevent users from writing to the tables during the backup
     operation and will ensure that the tables are in a consistent
     state. This option is recommended for MyISAM tables.
    </p><p>
     <tt class="literal">Single transaction</tt> will begin a transaction
     before reading from the tables. Because of the InnoDB versioning
     system this will allow all tables to be read in a consistent state.
     This method is recommended when backing up InnoDB tables.
    </p><p>
     <tt class="literal">Normal Backup</tt> will lock each table individually
     when performing the backup. While this can have less impact on the
     actions of users during the backup operation, these is a potential
     for tables to be backed up in an inconsistent state in relation to
     one another. This method is not recommended unless the risk on
     inconsistency in minimal.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-backup-advanced-options-output-options"></a>12.3.2.
     Output File Options
    </h3></div></div><div></div></div><p>
     The <tt class="literal">Output File Options</tt> control the formatting
     of the backup file. At present there is only one <tt class="literal">Backup
     Type</tt> available, the <tt class="literal">SQL Files</tt> format,
     which outputs a file similar to trhe output of the
     <tt class="literal">mysqldump</tt> utility.
    </p><p>
     <tt class="literal">No CREATEs</tt> will supress <tt class="literal">CREATE
     DATABASE</tt> statements. This can be useful if you need to
     restore the data to a different database than it was backed up
     from.
    </p><p>
     <tt class="literal">No EXTENDED INSERTS</tt> will supress the default
     behavior of combining multiple inserts into a single statement (for
     example <tt class="literal">INSERT INTO test VALUES ('1',Some
     data',2234),('2','Some More Data',23444)</tt>). While the
     <tt class="literal">EXTENDED INSERT</tt> syntax is more efficient both in
     terms of storage and execution, it is not compatible with most
     RDBMSes.
    </p><p>
     <tt class="literal">Complete INSERTs</tt> will produce full
     <tt class="literal">INSERT</tt> statements that include a column list
     (i.e. <tt class="literal">INSERT INTO tablename(columnA, columnB)
     VALUES(valueA, valueB)</tt>). Without this option the column
     list will be omitted.
    </p><p>
     <tt class="literal">Comment</tt>

     <i><span class="remark">
      [MH] FILL IN!
     </span></i>
    </p><p>
     <tt class="literal">Don't write full path</tt>

     <i><span class="remark">
      [MH] FILL IN
     </span></i>
    </p><p>
     <tt class="literal">ANSI Quotes</tt> will cause all table and database
     names to be quoted with ANSI style double quotes instead of
     back-ticks.
    </p><p>
     <tt class="literal">Disable keys</tt> will add an <tt class="literal">ALTER TABLE
     ... DISABLE KEYS</tt> statement to the backup file before the
     <tt class="literal">INSERT</tt> statements that populate the tables. This
     allows for faster recovery by loading all data before rebuilding
     the index information.
    </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-backup-schedule"></a>12.4.
    Schedule
   </h2></div></div><div></div></div><p>
    Backup operations can be scheduled to be executed on a regular basis
    using the <tt class="literal">Schedule</tt> tab. Backup operations can be
    scheduled to execute on a daily, weekly, or monthly basis.
   </p><p>
    The enable scheduling for your backup project, check the
    <span class="guilabel">Schedule this backup project</span> checkbox. You wil
    need to choose a target directory for the backup files to be placed
    and choose a name for the backup files. You can browse for a target
    directory by clicking the <span class="guibutton">...</span> button.
   </p><p>
    If you have enabled the <tt class="literal">Add Date/Time to Backup
    Files</tt> option in the <tt class="literal">Administrator
    Options</tt> dialogue, then the date and time of the backup
    will be appended to the file name automatically. See

    <a href="#mysql-gui-options-administrator-backup" title="17.5.3.Backup">Section17.5.3, &#8220;Backup&#8221;</a>

    for more information on setting this option.
   </p><p>
    Once you have decided on a file name and target directory, you can
    set the regularity of the backup operation. Regardless of you choice
    of daily, weekly, or monthly backups, you can set the time that the
    backup will occur by settiong the <tt class="literal">Time</tt> option.
    Set the backup time in a 24 hour format (i.e. 23:30).
   </p><p>
    When you select the <tt class="literal">Execute Backup Weekly</tt> option,
    a set of check boxes representing the days of the week will be
    displayed. Check the boxes corresponding to the days on you want to
    perform the backup.
   </p><p>
    When you select the <tt class="literal">Execute backup monthly</tt>
    option, a list of dates will appear, allowing you to choose which
    day of the month you want to perform the backup.
   </p><p>
    Click the <span class="guibutton">Save Project</span> button to save your
    preferences. After your project is saved it will be executed at the
    next scheduled interval. To run the backup operation immediatly
    click the <span class="guibutton">Execute Backup Now</span> button.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-restore"></a>Chapter13.
   Restore
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-restore-introduction">13.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-restore-general">13.2. 
    General
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-restore-restore-content">13.3. 
    Restore Content
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-restore-introduction"></a>13.1.
    Introduction
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Restore</tt> section helps with disaster recover
    by allowing you to restore backup files created with
    <tt class="literal">mysqldump</tt> or with the <tt class="literal">Backup</tt>
    section of MySQL Administrator. See

    <a href="#mysql-administrator-backup" title="Chapter12.
   Backup
  ">Chapter12, <i>
   Backup
  </i></a>

    for more information on creating backups with MySQL Administrator.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-restore-general"></a>13.2.
    General
   </h2></div></div><div></div></div><p>
    In this tab, you specify which backup file should be used for the
    restore procedure, along with information such as the backup file
    character set and format, and the target location for restored
    tables.
   </p><p>
    To set any options on this tab, you must first open a backup file by
    clicking the <span class="guibutton">Open Backup File</span> button at the
    bottom of the section. When all options are set, you can click the
    <span class="guibutton">Start Restore</span> button to begin the restore
    process.
   </p><p>
    The following options are available:
   </p><div class="itemizedlist"><ul type="disc"><li><p>
     <tt class="literal">File to restore</tt>: Specify path and filename of
     the backup file. You can browse for that file by clicking the
     <span class="guibutton">Open Backup File</span> button.
    </p></li><li><p>
     <tt class="literal">Target Schema</tt>: You can choose the
     <tt class="literal">Original Schema</tt> option to have all tables
     restored into their original databases. You can also choose the
     <tt class="literal">New Schema...</tt> option to restore all tables into
     a new database. Finally you can choose from one of the existing
     databases in the drop-down list to force all tables to be restored
     to that database.
    </p></li><li><p>
     <tt class="literal">Backup Type</tt>: At the moment, the only available
     option is <tt class="literal">SQL Files</tt>. Those are backup files
     containing SQL statements such as those produced by
     <tt class="literal">mysqldump</tt>.
    </p></li><li><p>
     <tt class="literal">Force - Continue even if we get an sql error</tt>:

     <i><span class="remark">
      [MH] LETS GET THIS REPLACED, BAD LABEL
     </span></i>

     This will cause a restore operation to continue executing even if
     errors are encountered during the restore operation.
    </p></li><li><p>
     <tt class="literal">Create database(s) if they don't exist</tt>: If a
     database is referenced in the backup file that does not exist, the
     database will automatically be created if this option is checked.
    </p></li><li><p>
     <tt class="literal">File Charset</tt>: Backup files created with
     MySQL Administrator are encoded in the <tt class="literal">utf8</tt>
     character set. Backup files created with other tools such as
     <tt class="literal">winmysqladmin</tt> may be encoded with other
     character sets. Before a backup file can be successfully imported
     you will need to specify its character set.
    </p><p>
     If you do not know the character set of your backup file, click the
     <span class="guibutton">Auto-Detect Character Set</span> button to have
     MySQL Administrator attempt to determine it automatically.
    </p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-restore-restore-content"></a>13.3.
    Restore Content
   </h2></div></div><div></div></div><p>
    If you do not wish to restore all the databases or tables listed
    within your backup file, you can use the <tt class="literal">Restore
    Content</tt> tab to limit which databases and tables are
    restored.
   </p><p>
    After clicking the <span class="guibutton">Analyze Backup File
    Content</span> button, a list of all databases and tables
    contained within the backup file will be displayed.
   </p><div class="figure"><a name="id4743562"></a><p class="title"><b>Figure13.1.
     The Restore Content tab
    </b></p><div><img src="images/restore-content.png" alt="The Restore Content tab"></div></div><p>
    To prevent a database or table from being restored, un-check the box
    next to the object's name.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-replication-status"></a>Chapter14.
   Replication Status
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-replication-introduction">14.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-replication-status-configure">14.2. 
    Configuring Replication Servers
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-replication-status-using">14.3. 
    Using the Replication Status Section
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-replication-introduction"></a>14.1.
    Introduction
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Replication Status</tt> sections give you a visual
    overview of your MySQL replication master and slaves. You can tell
    which slave machines are connected to the master and which ones are
    offline through the server status icons beside each machine.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-replication-status-configure"></a>14.2.
    Configuring Replication Servers
   </h2></div></div><div></div></div><p>
    To use the <tt class="literal">Replication Status</tt> section you must be
    connected to the server that acts as the master in your replication
    scheme. Your MySQL servers must be version 4 or higher to use this
    functionality.
   </p><p>
    For a slave server to show in the <tt class="literal">Replication
    Status</tt> screen, it must register itself with the master
    server. To have a slave server register itself with the master, set
    the <tt class="literal">report-host</tt> option in your server
    configuration (my.cnf/my.ini) file. See
    <a href="http://dev.mysql.com/doc/mysql/en/Replication_Options.html" target="_top">http://dev.mysql.com/doc/mysql/en/Replication_Options.html</a>
    for more information.
   </p><p>
    You can also set the value in the <tt class="literal">Replication</tt> tab
    of the <tt class="literal">Startup Variables</tt> section of
    MySQL Administrator.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-replication-status-using"></a>14.3.
    Using the Replication Status Section
   </h2></div></div><div></div></div><p>
    Once your servers are configured, they will appear in the
    <tt class="literal">Replication Status</tt> section, as seen in the
    following figure:
   </p><div class="figure"><a name="id4743725"></a><p class="title"><b>Figure14.1.
     The Replication Status section
    </b></p><div><img src="images/replication.png" alt="The Replication Status section"></div></div><p>
    All servers are listed in the main area of the <tt class="literal">Replication
    Status</tt> section, along with their server ID, Port, and
    current status.
   </p><p>
    New servers that are not currently being monitored will have an
    exclamation mark as their status symbol, and will be listed as a
    <tt class="literal">New Instance</tt> in the <tt class="literal">Status</tt>
    section of their entry.
   </p><p>
    Servers that are currently being monitored and are online will have
    a green status icon and will be listed as
    <tt class="literal">Available</tt> in the <tt class="literal">Status</tt>
    section of their entry.
   </p><p>
    Servers that are currently not in contact with the master server
    will have a red status icon and will be listed as <tt class="literal">Not
    Available</tt>.
   </p><p>
    There will be a slight delay between a slave machine going offline
    and having its status updated to allow for an adequate timeout in
    the communications between master and slave.
   </p><p>
    To start monitoring a new server that is not currently being
    monitored, click the <span class="guibutton">Add Instance to Monitoring
    List</span> button. To stop monitoring a server that is
    currently being monitored, click the <span class="guibutton">Remove Instance from
    monitoring List</span> button.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-catalogs"></a>Chapter15.
   Catalogs
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-administrator-catalogs-introduction">15.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#mysql-administrator-catalogs-schema-tables">15.2. 
    Schema Tables
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-administrator-catalogs-schema-tables-table-status">15.2.1. 
     Table Status
    </a></span></dt><dt><span class="sect2"><a href="#mysql-administrator-catalogs-schema-tables-row-status">15.2.2. 
     Row Status
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#mysql-administrator-catalogs-indexes">15.3. 
    Schema Indexes
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-catalogs-introduction"></a>15.1.
    Introduction
   </h2></div></div><div></div></div><p>
    This section allows you to view catalogs, schemata, tables and their
    properties, and to perform a number of operations on tables.
    Existing catalogs and schemata are listed in the lower left area of
    the <a href="#mysql-administrator-sidebar" title="4.2.
    Sidebar
   ">sidebar</a>. If
    there are many schemata on your MySQL server, the field with the
    magnifying-glass icon may be handy for filtering the schemata you
    are looking for. Typing in <tt class="literal">t</tt> or
    <tt class="literal">T</tt>, for example, will set the filter to schemata
    whose names begin with a <tt class="literal">t</tt>. The filter works in a
    case-insensitive fashion.
   </p><p>
    Select the database that you wish to view. Right-click on any
    database and choose the <span class="guimenu">Refresh Schemata List</span>
    option to refresh the database list. Clicking on a database will
    cause the <tt class="literal">Schema Tables</tt> and <tt class="literal">Schema
    Indices</tt> tabs to be populated with the tables and indexes
    of the selected database.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-catalogs-schema-tables"></a>15.2.
    Schema Tables
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Schema Tables</tt> tab lists the different tables
    in the selected database, along with the rowcount, data length, and
    index length for those tables. For MyISAM tables, you also find the
    date and time when the table was last modified, under
    <tt class="literal">Update Time</tt>. You can update the list of tables by
    pressing the <span class="guibutton">Refresh</span> button.
   </p><p>
    The tables are ordered by table name initially, but you may change
    that sorting by clicking on the appropriate headings
    (<tt class="literal">Type</tt>, <tt class="literal">Row Format</tt>, etc.).
   </p><p>
    To drop a table, right-click on the table and choose the
    <span class="guimenu">Drop Table</span> option from the pop-up menu. To create
    a table you can either click the <span class="guibutton">Create Table</span>
    button at the bottom of the window, or right-click on a table and
    choose the <span class="guimenu">Create Table</span> option from the pop-up
    menu.
   </p><p>
    To edit a table's columns and indexes, right-click on the desired
    table and choose the <span class="guimenu">Edit Table</span> option from the
    pop-up menu. This will launch the MySQL Table Editor, which you can
    use to modify the table. See

    <a href="#gui-table-editor" title="Chapter16.
   The MySQL Table Editor
  ">Chapter16, <i>
   The MySQL Table Editor
  </i></a>

    .
   </p><p>
    To edit a table's actual data, right-click on the table and choose
    the <span class="guimenu">Edit Table Data</span> option. This will launch the
    MySQL Query Browser and load the table's data into the result area
    of the MySQL Query Browser.
   </p><p>
    You may select more than one table at a time in order to perform
    operations on multiple tables. For the selected tables, you can
    perform the following operations by either clicking the
    <span class="guibutton">Maintenance</span> button at the bottom of the table
    list or by right-clicking on one of the selected tables and choosing
    one of the following options from the <span class="guimenu">Maintenance</span>
    sub-menu of the pop-up menu:
   </p><div class="itemizedlist"><ul type="disc"><li><p>
     <tt class="literal">Optimize Table</tt>: This corresponds to the
     <tt class="literal">OPTIMIZE TABLE</tt> SQL command and should be used if
     you have deleted a large part of a table or if you have made many
     changes to a table with variable-length rows (tables that have
     <tt class="literal">VARCHAR</tt>, <tt class="literal">BLOB</tt>, or
     <tt class="literal">TEXT</tt> columns). Deleted records are maintained in
     a linked list and subsequent <tt class="literal">INSERT</tt> operations
     reuse old record positions. You can use this command to reclaim the
     unused space and to defragment the datafile. Note that table
     optimization works for MyISAM and BDB tables only. For more
     information see the
     <a href="http://dev.mysql.com/doc/en/optimize-table" target="_top">OPTIMIZE
     TABLE section</a> of the reference manual.
    </p></li><li><p>
     <tt class="literal">Check Table</tt>: This corresponds to the
     <tt class="literal">CHECK TABLE</tt> SQL command and is used to diagnose
     table problems. For more information see the
     <a href="http://dev.mysql.com/doc/en/check-table" target="_top">CHECK TABLE
     section</a> of the reference manual.
    </p></li><li><p>
     <tt class="literal">Repair Table</tt>: This corresponds to the
     <tt class="literal">REPAIR TABLE</tt> SQL command and should be used in
     case of table problems. Note that this command works for MyISAM
     tables only. For more information see the
     <a href="http://dev.mysql.com/doc/en/repair-table" target="_top">REPAIR TABLE
     section</a> of the reference manual.
    </p></li></ul></div><p>
    Clicking on a table name will display its properties in the details
    area when the details area is active. To display the details area,
    click the <span class="guibutton">Details &gt;&gt;</span> button.
   </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-catalogs-schema-tables-table-status"></a>15.2.1.
     Table Status
    </h3></div></div><div></div></div><p>
     In this tab, you find detailed information about the selected
     table. This information could also be retrieved by issuing a
     <tt class="literal">SHOW TABLE STATUS LIKE 'tbl'</tt> SQL command. For
     more information see the
     <a href="http://dev.mysql.com/doc/en/show-table-status" target="_top">SHOW
     TABLE STATUS section</a> of the reference manual.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-administrator-catalogs-schema-tables-row-status"></a>15.2.2.
     Row Status
    </h3></div></div><div></div></div><p>
     In this tab, you find detailed information about the rows of the
     selected table. This information could also be retrieved by issuing
     a <tt class="literal">SHOW TABLE STATUS LIKE 'tbl'</tt> SQL command. For
     more information see the
     <a href="http://dev.mysql.com/doc/en/show-table-status" target="_top">SHOW
     TABLE STATUS section</a> of the reference manual.
    </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-administrator-catalogs-indexes"></a>15.3.
    Schema Indexes
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Schema Indices</tt> tab lists the indexes of the
    selected database. Besides the index names and the table the index
    belongs to, you can also see the index type, whether values are
    unique, and whether NULL values are allowed. You can also get this
    information by issuing a <tt class="literal">SHOW INDEX</tt> SQL command
    in a command-line client (see the
    <a href="http://dev.mysql.com/doc/en/show-database-info" target="_top">Retrieving
    Information about Database, Tables, Columns, and Indexes</a>
    section of the reference manual). For more information about
    indexes, see the
    <a href="http://dev.mysql.com/doc/en/indexes" target="_top">Column
    Indexes</a> section of the reference manual.
   </p><p>
    To see the columns that form a given index, double-click on the
    index.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="gui-table-editor"></a>Chapter16.
   The MySQL Table Editor
  </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#gui-table-editor-introduction">16.1. 
    Introduction
   </a></span></dt><dt><span class="sect1"><a href="#gui-table-editor-main-window">16.2. 
    The Main Editor Window
   </a></span></dt><dt><span class="sect1"><a href="#gui-table-editor-columns-and-indices">16.3. 
    The Columns And Indices Tab
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#gui-table-editor-columns-and-indices-column-editor">16.3.1. 
     The Column Editor
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-columns-and-indices-detail">16.3.2. 
     The Detail Area
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#gui-table-editor-Table-Options">16.4. 
    The Table Options Tab
   </a></span></dt><dt><span class="sect1"><a href="#gui-table-editor-advanced-options">16.5. 
    The Advanced Options Tab
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-various">16.5.1. 
     The Various Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-row-options">16.5.2. 
     The Row Options Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-storage-options">16.5.3. 
     The Storage Options Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-merge-options">16.5.4. 
     The Merge Table Options Section
    </a></span></dt><dt><span class="sect2"><a href="#gui-table-editor-advanced-options-raid-options">16.5.5. 
     The Table RAID Settings Section
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#gui-table-editor-changes">16.6. 
    Applying Your Changes
   </a></span></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gui-table-editor-introduction"></a>16.1.
    Introduction
   </h2></div></div><div></div></div><p>
    The MySQL Table Editor is a component of both the MySQL Query Browser and
    MySQL Administrator, and allows for the visual creation and modification
    of tables.
   </p><p>
    The MySQL Table Editor can be accessed from the MySQL Query Browser by
    right-clicking on a table within the database browser and choosing
    the <span class="guimenu">Edit Table</span> option, or by right-clicking on a
    database within the database browser and choosing the
    <span class="guimenu">Create New Table</span> option.
   </p><p>
    The MySQL Table Editor can be accessed from MySQL Administrator through the
    <span class="guimenu">Catalogs</span> screen. Once you have selected a
    database, right-click on a table and choose the <span class="guimenu">Edit
    Table</span> option from the drop-down menu. You can also select
    a table and click the <span class="guibutton">Edit Table</span> button to
    access the MySQL Table Editor.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gui-table-editor-main-window"></a>16.2.
    The Main Editor Window
   </h2></div></div><div></div></div><p>
    The MySQL Table Editor consists of a work space divided into three tabs,
    some general information prompts, and three action buttons.
   </p><p>
    Regardless of the tab you have active, you can always edit the table
    name, the database it belongs to, and the table comment.
   </p><div class="figure"><a name="id4745006"></a><p class="title"><b>Figure16.1.
     The MySQL Table Editor
    </b></p><div><img src="images/tableeditor.png" alt="The MySQL Table Editor"></div></div><p>
    The tabbed area is divided into three sections:
   </p><div class="itemizedlist"><ul type="disc"><li><p>
     <span class="emphasis"><em>Columns and Indices:</em></span> Use the Columns and
     Indices tab to create and modify the table's column and index
     information. You can also create FOREIGN KEY relationships using
     this tab.
    </p></li><li><p>
     <span class="emphasis"><em>Table Options:</em></span>Use the Table Options tab to
     choose the storage engine used by the table and the table's default
     character set.
    </p></li><li><p>
     <span class="emphasis"><em>Advanced Options:</em></span> Use the Advanced Options tab
     to configure advanced options such as per-table storage directory,
     MERGE and RAID table options, and table/row length options.
    </p></li></ul></div><p>
    Each of these areas are discussed in further detail in the
    following sections.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gui-table-editor-columns-and-indices"></a>16.3.
    The Columns And Indices Tab
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Columns and Indices</tt> tab can be used to
    display and edit all column and index information for your table.
    Using this tab, you can add, drop, and alter columns and indexes.
   </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gui-table-editor-columns-and-indices-column-editor"></a>16.3.1.
     The Column Editor
    </h3></div></div><div></div></div><p>
     You can use the column editor to change the name, data type, default
     value, and other properties of your table's columns.
    </p><div class="figure"><a name="id4745116"></a><p class="title"><b>Figure16.2.
      The column editor
     </b></p><div><img src="images/columneditor.png" alt="The column editor"></div></div><p>
     To change the name, data type, default value, or comment of a
     column, double-click on the value you wish to change. The value becomes editable and you can the complete your changes by
     pressing the <span><b class="keycap">Enter</b></span> key.
    </p><p>
     To modify the flags on a column (<tt class="literal">UNSIGNED</tt>,
     <tt class="literal">BINARY</tt>, <tt class="literal">ASCII</tt>, and so on) check
     and uncheck the boxes corresponding to the flag you wish to change.
    </p><p>
     To the left of the column name is an icon that indicates whether
     the column is a member of the primary key. If the icon is a small
     key, that column belongs to the primary key, otherwise the icon is a blue
     diamond. To add or remove a column from the
     primary key, you can click on the icon.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gui-table-editor-columns-and-indices-detail"></a>16.3.2.
     The Detail Area
    </h3></div></div><div></div></div><p>
     The detail area of the <tt class="literal">Columns and Indices</tt> tab
     is divided into three tabs and is used for modifying the index,
     foreign key, and miscellaneous information regarding your columns.
    </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="gui-table-editor-columns-and-indices-detail-indices"></a>16.3.2.1.
      The Indices Tab
     </h4></div></div><div></div></div><p>
      The <tt class="literal">Indices</tt> tab holds all index information for
      your table. You can add, drop, and modify indexes using the
      indices tab, in combination with the column editor.
     </p><div class="figure"><a name="id4745229"></a><p class="title"><b>Figure16.3.
       The index editor
      </b></p><div><img src="images/indexeditor.png" alt="The index editor"></div></div><p>
      To add an index, click the <span class="guibutton">+</span> (plus) button
      below the index list. You will be prompted for an index name and
      then the new index is created. To drop an index, select the index
      and click the <span class="guibutton">-</span> (minus) button to drop the
      index from the index list.
     </p><p>
      Use the <span class="guilabel">Index Name</span> and <span class="guilabel">Index
      Kind</span> dialogs to modify the name and type
      (<tt class="literal">UNIQUE</tt>, <tt class="literal">FULLTEXT</tt>, and so on) of
      the index.
     </p><p>
      To add columns to an index, either click and drag the column to
      the <span class="guilabel">Index Columns</span> box or select the column
      you wish to add and click the <span class="guibutton">+</span> (plus)
      button to the right of the <span class="guilabel">Index Columns</span> box.
      You can remove a column from the index by selecting the column and
      clicking the <span class="guibutton">-</span> (minus) button to drop the
      column from the index.
     </p><p>
      To change an index to only refer to a column prefix (such as with
      the CHAR and VARCHAR string data types), select the index column
      you wish to prefix in the <span class="guilabel">Index Columns</span> box
      and then click the arrow icon to the right of the <span class="guilabel">Index
      Columns</span> box. Select the <span class="guimenu">Set Index Column
      Length</span> option from the drop-down menu that appears. You
      can set the desired prefix length in the dialog that appears.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="gui-table-editor-columns-and-indices-detail-foreign-keys"></a>16.3.2.2.
      The Foreign Keys Tab
     </h4></div></div><div></div></div><p>
      The <tt class="literal">Foreign Keys</tt> tab is divided into two
      sections, one with a list of foreign keys and one with various
      dialogs for foreign key settings.
     </p><p>
      To add a foreign key, click the <span class="guibutton">+</span> (plus)
      button below the foreign key list. You will be prompted to name
      the new foreign key, and it is then be added to the list.
     </p><p>
      To drop a foreign key, select the foreign key and click the
      <span class="guibutton">-</span> (minus) button below the foreign key
      list. The foreign key is then dropped from the foreign key list.
     </p><p>
      You can modify the name of the foreign key, its <tt class="literal">ON
      DELETE</tt>, and its <tt class="literal">ON UPDATE</tt> actions using
      the dialogs provided in the <span class="guilabel">Foreign Key
      Settings</span> section of the tab.
     </p><p>
      To establish a foreign key relationship, choose a table from the
      <span class="guilabel">Ref. Table</span> drop-down list. The columns that
      can be referenced as foreign keys are listed in the area
      below, and you can drag a column from the column editor to the
      <span class="guilabel">Column</span> section to the left of the column you
      wish to reference.
     </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="gui-table-editor-columns-and-indices-detail-column-details"></a>16.3.2.3.
      The Column Details Tab
     </h4></div></div><div></div></div><p>
      The <tt class="literal">Column Details</tt> tab provides an interface
      for setting the parameters of a column without using the table
      interface of the column editor.
     </p><p>
      All settings that are available in the
      <a href="#gui-table-editor-columns-and-indices-column-editor" title="16.3.1.
     The Column Editor
    ">Column
      Editor</a> are also available in the Column Details tab, and in
      addition you can also configure the column character set and
      column default collation from the Column Details tab.
     </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gui-table-editor-Table-Options"></a>16.4.
    The Table Options Tab
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Table Options</tt> tab allows you to change the
    storage engine and character set of your table. The potential
    storage engines are listed, along with a brief summary of each
    storage engine's features and strengths.
   </p><p>
    To change the storage engine for your table, click on the radio
    button next to the desired storage engine.
   </p><p>
    To change the default character set or collation of your table,
    choose a new option from the drop-down list of available character
    sets.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gui-table-editor-advanced-options"></a>16.5.
    The Advanced Options Tab
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Advanced Options</tt> tab is used to configure
    table options that would be considered outside the standard set of
    options that most users designate when creating and modifying
    tables.
   </p><p>
    The <tt class="literal">Advanced Options</tt> tab is divided into several
    sub-sections, each of which is described in the upcoming
    sections of this manual.
   </p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gui-table-editor-advanced-options-various"></a>16.5.1.
     The Various Section
    </h3></div></div><div></div></div><p>
     The <tt class="literal">Various</tt> section of the <tt class="literal">Advanced
     Options</tt> tab contains options for you to set the
     <tt class="literal">PACK KEYS</tt> behavior, the table password, the
     initial <tt class="literal">AUTO_INCREMENT</tt> value, and the delayed
     key update behavior.
    </p><p>
     The <tt class="literal">AUTO_INCREMENT</tt> and delayed key update
     behaviors apply only to MyISAM tables.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gui-table-editor-advanced-options-row-options"></a>16.5.2.
     The Row Options Section
    </h3></div></div><div></div></div><p>
     The <tt class="literal">Row Options</tt> section can be used to configure
     options such as the row format, checksum use, and the row size
     parameters needed for large tables.
    </p><p>
     To set the row format, choose the desired row format from the
     drop-down list. See
     <a href="http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html" target="_top">http://dev.mysql.com/doc/mysql/en/MyISAM_table_formats.html</a>
     for more information on the different row formats that are
     available. This option only applies to MyISAM tables.
    </p><p>
     When you expect a table to be particularly large, use the
     <span class="guilabel">Avg Row Length</span>, <span class="guilabel">Min Rows</span>,
     and <span class="guilabel">Max Rows</span> options to enable the MySQL
     server to better accommodate your data. See
     <a href="http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html" target="_top">http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html</a>
     for more information on how to use these options.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gui-table-editor-advanced-options-storage-options"></a>16.5.3.
     The Storage Options Section
    </h3></div></div><div></div></div><p>
     The <tt class="literal">Storage Options</tt> section is used to configure
     a custom path to the table storage and data files. This option can
     help improve data integrity and server performance by locating
     different tables on different hard-drives.
    </p><p>
     This option is only available for MyISAM tables and is not
     available for servers running under the Windows operating system.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gui-table-editor-advanced-options-merge-options"></a>16.5.4.
     The Merge Table Options Section
    </h3></div></div><div></div></div><p>
     The <tt class="literal">Merge Table</tt> Options section is used to
     configure MERGE tables in MyISAM. To create a MERGE table, select
     MERGE as your storage engine in the
     <a href="#gui-table-editor-Table-Options" title="16.4.
    The Table Options Tab
   ">Table Options
     Tab</a> and then specify the tables you wish to MERGE in the
     <span class="guilabel">Union Tables</span> dialog.
    </p><p>
     You can also specify the action the server should take when users
     attempt to perform INSERT statements on the merge table. See
     <a href="http://dev.mysql.com/doc/mysql/en/MERGE.html" target="_top">http://dev.mysql.com/doc/mysql/en/MERGE.html
     for more information on MERGE tables.</a>
   </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="gui-table-editor-advanced-options-raid-options"></a>16.5.5.
     The Table RAID Settings Section
    </h3></div></div><div></div></div><p>
     The <tt class="literal">Table RAID Settings</tt> section allows you to
     configure RAID support for MyISAM tables. RAID allows MyISAM table
     data files to grow larger than the 2GB/4GB size limit imposed by some
     operating systems.
    </p><p>
     For more information on using RAID support with MyISAM, see
     <a href="http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html" target="_top">http://dev.mysql.com/doc/mysql/en/CREATE_TABLE.html</a>
   </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="gui-table-editor-changes"></a>16.6.
    Applying Your Changes
   </h2></div></div><div></div></div><p>
    The changes you make with the MySQL Table Editor are not immediately
    applied but are instead queued to be applied in batches after you
    have made all your edits.
   </p><p>
    To apply the changes you have made, click the <span class="guibutton">Apply
    Changes</span> button. The <tt class="literal">Confirm Table
    Edit</tt> dialog will appear.
   </p><div class="figure"><a name="id4745882"></a><p class="title"><b>Figure16.4.
     The Confirm Table Edit dialog
    </b></p><div><img src="images/confirmchanges.png" alt="The Confirm Table Edit dialog"></div></div><p>
    You can click the <span class="guibutton">Execute</span> button to confirm
    the changes and have them applied, or click the
    <span class="guibutton">Cancel</span> button to discard the changes. You can
    also click the <span class="guibutton">Discard Changes</span> button in the
    main MySQL Table Editor window to discard all changes you have made.
   </p><p>
    You can also copy the proposed changes to the clipboard for further
    editing by highlighting the ALTER TABLE or CREATE TABLE statement,
    right-clicking and choosing <span class="guimenu">Copy</span> from the
    drop-down menu.
   </p></div></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-gui-options"></a>Chapter17.
 Options Dialog
</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-gui-options-introduction">17.1. 
  Introduction
 </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-general-options">17.2. 
  General Options
 </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-connections">17.3. 
  Connections
 </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-editors">17.4. Editors</a></span></dt><dt><span class="sect1"><a href="#mysql-gui-options-administrator">17.5. 
    Administrator
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-gui-options-administrator-user-administration">17.5.1. User Administration</a></span></dt><dt><span class="sect2"><a href="#mysql-gui-options-administrator-health-graphs">17.5.2. Health Graphs</a></span></dt><dt><span class="sect2"><a href="#mysql-gui-options-administrator-backup">17.5.3. Backup</a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-options-introduction"></a>17.1.
  Introduction
 </h2></div></div><div></div></div><p>
  The <tt class="literal">Options</tt> dialog allows you to configure
  connection profiles, general program settings, and more. You can open
  the <tt class="literal">Options</tt> dialog window using one of the
  following methods:

  </p><div class="itemizedlist"><ul type="disc"><li><p>
    In the connection dialog window, click the
    <span class="guibutton">...</span> button.
   </p></li><li><p>
    In the main application window select <span class="guimenu">Options ...</span>
    from the <span class="guimenu">Tools</span> menu.
   </p></li></ul></div><p>

  </p><div class="figure"><a name="id4747119"></a><p class="title"><b>Figure17.1.
    Options dialog
   </b></p><div><img src="images/options.png" alt="Options dialog"></div></div><p>

  In the sidebar of that dialog, you can select the section you wish to
  configure. There are three action buttons in the lower right
  corner of the window:

  </p><div class="itemizedlist"><ul type="disc"><li><p>
    <span class="guibutton">Apply Changes</span> applies and saves changes.
   </p></li><li><p>
    <span class="guibutton">Discard Changes</span> discards any changes you have
    made.
   </p></li><li><p>
    <span class="guibutton">Close</span> closes the <tt class="literal">Options</tt>
    dialog window. If you have not applied or discarded your changes, you will be prompted to do so.
   </p></li></ul></div><p>
 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-options-general-options"></a>17.2.
  General Options
 </h2></div></div><div></div></div><p>
  The <tt class="literal">General Options</tt> section allows you to specify a
  number of settings that are valid for all graphical MySQL applications. At the time of writing, MySQL Administrator and MySQL Query Browser are the only programs in the MySQL
  GUI suite, but other programs will follow soon.</p><div class="itemizedlist"><ul type="disc"><li><p>
    <tt class="literal">Store Window Positions</tt>: When an application is
    started the next time, its recent window positions will be reused.
   </p></li><li><p>
    <tt class="literal">Show Tip of Day</tt>: If checked, a pop-up window with
    the tip of the day appears at program startup.
   </p></li><li><p>
    <tt class="literal">Store Passwords</tt>: If checked, passwords are stored
    in the user's connection profile. In this case, you can
    select the password storage method:
   </p><p>
    <tt class="literal">Plaintext</tt> means they are stored without
    encryption; this can be insecure. <tt class="literal">Obscured</tt> means
    they are encrypted using a weak algorithm. This encryption method,
    however, is operating system independent. Selecting <tt class="literal">OS Specific</tt> will use the default encryption method provided by your operating system. The default option is <tt class="literal">Plaintext</tt>.
   </p></li><li><p>
    <tt class="literal">Language</tt>: Select the interface language. The
    default is <tt class="literal">English</tt>.
   </p></li><li><p>
    <tt class="literal">Default Font</tt>: The font used for all aplication text.</p></li><li><p>
    <tt class="literal">Data Font</tt>: The font used for all query and table data displayed.
   </p></li><li><p>
    <tt class="literal">Code Font</tt>: The font used for all queries entered by the user..
   </p></li><li><p>
<tt class="literal">Ignorelist</tt>: Whenever you check the <tt class="literal">Do Not Show This Message Again</tt> option on error and message prompts, they are added to this list. If you would like a particular message to be shown again, click the <span class="guibutton">Remove</span> button after selecting the message from the list.</p></li></ul></div><p>You may change the font and
    font size  of any of the application fonts by clicking the <span class="guibutton">Choose ...</span> button to the right of the font.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-options-connections"></a>17.3.
  Connections
 </h2></div></div><div></div></div><p>
  The <tt class="literal">Connections</tt> section allows you to create,
  edit, and delete connection profiles. The center box displays a list
  of currently available profiles, together with a history of
  connections that were made without being stored in a profile. You can
  collapse or expand both the <tt class="literal">Connections</tt> and
  <tt class="literal">History</tt> trees by double-clicking them.
 </p><p>
  Connections are automatically added to the <tt class="literal">History</tt> tree whenever you establish a connection to a MySQL server without using one of the profiles stored under the <tt class="literal">Connections</tt> tree. They
  do not appear in the drop-down box of the
  <tt class="literal">Connection</tt> dialog, but you can use any of them by
  manually typing their name into the <tt class="literal">Connection</tt> box of the <tt class="literal">Connection</tt> dialog.
 </p><div class="figure"><a name="id4747450"></a><p class="title"><b>Figure17.2.
   Options dialog: Connections
  </b></p><div><img src="images/options-connection.png" alt="Options dialog: Connections"></div></div><p>
  To edit an existing connection profile, click on its name and change
  the values that appear in the <tt class="literal">Connection Parameters</tt>
  and <tt class="literal">Advanced Parameters</tt> tabs, then click on the
  <span class="guibutton">Apply Changes</span> button to save your changes.
 </p><p>
    When you select a connection profile from either the
  <tt class="literal">Connections</tt> or <tt class="literal">History</tt> trees, the
  <tt class="literal">Connection Parameters</tt> tab displays the following
  fields:

  </p><div class="itemizedlist"><ul type="disc"><li><p>
    <tt class="literal">Connection</tt>: The connection profile label. This is
    the name by which you refer to the profile and that appears in the
    <tt class="literal">Connection</tt> drop-down box of the Connection dialog. It may contain any characters, including spaces.
    Choose distinctive names so that you can easily tell which profiles
    they refer to. The names can help you distinguish connections to
    different MySQL servers, or connections as different MySQL users to
    a given server.</p></li><li><p>
    <tt class="literal">Username</tt>: The username used to connect to the
    MySQL server.
   </p></li><li><p>
    <tt class="literal">Password</tt>: The password used to connect to the
    MySQL server. Note that passwords are not stored in the connection
    profile, unless you specify otherwise in the
    <a href="#mysql-gui-options-general-options" title="17.2.
  General Options
 ">General
    Options section</a>.
   </p></li><li><p>
    <tt class="literal">Hostname</tt>: The name of the host machine where the
    MySQL server runs, or its IP address.
   </p></li><li><p>
    <tt class="literal">Port</tt>: The TCP/IP port that the MySQL server
    listens to on the host machine.
   </p></li><li><p>
    <tt class="literal">Type</tt>: Specifies the protocol used to connect to
    the database server. The default protocol is
    <tt class="literal">MySQL</tt> (which uses the native MySQL protocol). The
    other protocols listed are not currently available.
   </p></li><li><p>
    <tt class="literal">Schema</tt>: The default database for a connection when using the MySQL Query Browser.
   </p></li><li><p>
    <tt class="literal">Notes</tt>: You can use this field to enter comments
    or additional information describing the connection profile.
   </p></li></ul></div><p>
 </p><p>
  <span class="emphasis"><em>Note that the <tt class="literal">Advanced Parameters</tt> tab may
  not be available in some of the first releases of MySQL Administrator.
  If that is the case in the version you are using, you can still set
  those parameters in the Connection dialog. Use the <span class="guibutton">Details ...</span> button of
  that dialog to display the <tt class="literal">Advanced Connection
  Options</tt>.</em></span>
 </p><p>
  When you select a connection profile from either the
  <tt class="literal">Connections</tt> or <tt class="literal">History</tt> list, the
  <tt class="literal">Advanced Parameters</tt> tab displays the following
  checkboxes:

  </p><div class="itemizedlist"><ul type="disc"><li><p>
    <tt class="literal">Use compressed protocol</tt>: If checked, the
    communication between the application and the MySQL server will be
    compressed, which may increase transfer rates. This corresponds to starting a
    MySQL command-line tool with the <tt class="literal">--compress</tt>
    option.
   </p></li><li><p>
    <tt class="literal">Return number of found rows, not number of affected
    rows</tt>: By default, MySQL returns the number of rows changed
    by the last <tt class="literal">UPDATE</tt>, deleted by the last
    <tt class="literal">DELETE</tt> or inserted by the last
    <tt class="literal">INSERT</tt> statement. When this option is checked,
    the server returns the number of rows matched by the
    <tt class="literal">WHERE</tt> statement for <tt class="literal">UPDATE</tt>
    statements.
   </p></li><li><p>
    <tt class="literal">Ignore spaces after function names, make them reserved
    words</tt>: Normally, any refereence to a function name in an
    SQL statement must be followed immediately by anopening parenthesis.
    If this option is checked, spaces may appear between the function
    name and the parenthesis, like this:

</p><pre class="programlisting">
       COUNT (*)
      </pre><p>

    Enabling this option has the effect that function names become
    reserved words. This option corresponds to starting a MySQL
    command-line tool with the <tt class="literal">--ignore-spaces</tt>
    option.
   </p></li><li><p>
    <tt class="literal">Allow interactive_timeout seconds of inactivity before
    disconnect</tt>: Normally, the connection is closed by the
    MySQL server after a certain period of inactivity on the client
    side. This period can be set with the
    <tt class="literal">interactive_timeout</tt> variable.

    
    If checked, the server will not close the connection unless the
    period of inactivity exceeds the value set by
    <tt class="literal">interactive_timeout</tt>. This corresponds to starting
    a MySQL command-line tool with the
    <tt class="literal">--connect-timeout=<i class="replaceable"><tt>seconds</tt></i>
    </tt> option.
   </p></li><li><p>
    <tt class="literal">Enable LOAD DATA LOCAL handling</tt>: By default, the
    <tt class="literal">LOCAL</tt> option of the <tt class="literal">LOAD DATA</tt>
    statement is disabled for security reasons. Enabling this option
    will allow to load data from the local machine (the machine where the client GUI application is running). This option corresponds to starting a
    MySQL command-line tool with the <tt class="literal">--local-infile=1</tt>
    option. (Note that this option is ineffective unless the MySQL
    server allows <tt class="literal">LOCAL</tt> handling.)
   </p></li></ul></div><p>
 </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-options-editors"></a>17.4.Editors</h2></div></div><div></div></div><p>The <tt class="literal">Editors</tt> section is used to configure options specific to the different editors available within the MySQL GUI Suite. At the time of writing this is limited to the <a href="#gui-table-editor" title="Chapter16.
   The MySQL Table Editor
  ">MySQL Table Editor</a>.</p><div class="itemizedlist"><ul type="disc"><li><p><tt class="literal">Show SQL command before applying changes</tt> toggles whether the MySQL Table Editor will show you the <tt class="literal">ALTER TABLE</tt> statement it is about to execute for confirmation when you click <span class="guibutton">Apply Changes</span>.</p></li><li><p><tt class="literal">All columns Not Null per default</tt> determines whether the MySQL Table Editor will designate columns as being <tt class="literal">NOT NULL</tt> by default when creating new columns.</p></li><li><p><tt class="literal">All integer columns unsigned per default</tt> sets whether integer columns are declared <tt class="literal">UNSIGNED</tt> by default when creating new columns.</p></li><li><p><tt class="literal">PK Naming</tt> dictates the format that should be used to name <tt class="literal">PRIMARY KEY</tt> columns that are automatically generated. the <i class="replaceable"><tt>%tablename%</tt></i> portion will be replaced with the name of the appropriate table.</p></li><li><p><tt class="literal">Index Naming</tt> sets the name automatically generated for new indexes. The <i class="replaceable"><tt>%nr%</tt></i> string will be replaced with an automatically incrementing number.</p></li><li><p><tt class="literal">FK Naming</tt> configures the name used when creating new foreign keys.</p></li><li><p><tt class="literal">PK Datatype</tt> is the datatype used when creating a <tt class="literal">PRIMARY KEY</tt> column.</p></li><li><p><tt class="literal">Def. Datatype</tt> is the default datatype assigned to all new columns that are not part of a <tt class="literal">PRIMARY KEY</tt>.</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-options-administrator"></a>17.5.
    Administrator
   </h2></div></div><div></div></div><p>
    The <tt class="literal">Administrator</tt> section allows you to specify
    options that affect the behavior of the MySQL Administrator. The <tt class="literal">Administrator</tt> section is divided into three sub-sections that will be discussed further in the sections that follow.
</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-gui-options-administrator-user-administration"></a>17.5.1.User Administration</h3></div></div><div></div></div><p>These options affect the interface of the <a href="#mysql-administrator-user-administration" title="Chapter9.
   User Administration
  ">User Administration</a> section of MySQL Administrator.</p><div class="itemizedlist"><ul type="disc"><li><p>
      <tt class="literal">Show Global Privileges</tt>: If checked, the
      <a href="#mysql-administrator-user-administration-global-privileges" title="9.4.
    Global Privileges
   ">Global
      Privileges</a> tab will be visible in the
      <a href="#mysql-administrator-user-administration" title="Chapter9.
   User Administration
  ">User
      Administration</a> section. In that tab, you can grant users
      global privileges (as opposed to privileges on a database, table,
      or column level only). This may affect security. See
      <a href="dev.mysql.com/doc/en/privilege-system" target="_top">The MySQL Access Privilege
      System</a> for details. If unchecked, the
      <a href="#mysql-administrator-user-administration-global-privileges" title="9.4.
    Global Privileges
   ">Global
      Privileges</a> tab will not be visible in the
      <a href="#mysql-administrator-user-administration" title="Chapter9.
   User Administration
  ">User
      Administration</a> section.
     </p></li><li><p>
      <tt class="literal">Show Table/Column Privileges</tt>: In most
      situations, it is sufficient to grant either global or database
      privileges for users. You can hide the
      <a href="#mysql-administrator-user-administration-table-column-privileges" title="9.6.
    Table Column Privileges
   ">Table/Column
      Privileges</a> tab in the
      <a href="#mysql-administrator-user-administration" title="Chapter9.
   User Administration
  ">User
      Administration</a> section by enabling this checkbox.
     </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-gui-options-administrator-health-graphs"></a>17.5.2.Health Graphs</h3></div></div><div></div></div><p>These options affect the appearance of the <a href="#mysql-administrator-health" title="Chapter10.
   Health
  ">Health Graphs</a> section of MySQL Administrator.</p><div class="itemizedlist"><ul type="disc"><li><p><tt class="literal">Use Peak Level Indicator</tt>: This will display a thin yellow line on the health graphs indicating the highest value recorded by the graph.</p></li><li><p><tt class="literal">Reset peak Level after a number of ticks</tt>: If this box is not checked, the <tt class="literal">Peak Level Indicator</tt> will be permanently positioned at the highest value ever recorded on the health graph. With this box checked, the <tt class="literal">Peak Value Indicator</tt> will be reset after a period of time indicated by the <tt class="literal">Time after the Peak level resets</tt> option. Use this option if you would like to know the peak level over an interval rather than the peak level overall.</p></li><li><p><tt class="literal">Time after the Peak level resets</tt>: When the <tt class="literal">Reset peak Level after a number of ticks</tt> option is set, this determines the amount of time (in ticks) that will pass before the <tt class="literal">Peak Level Indicator</tt> will be reset.</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-gui-options-administrator-backup"></a>17.5.3.Backup</h3></div></div><div></div></div><p>The backup options configure how MySQL Administrator performs backup operations.</p><div class="itemizedlist"><ul type="disc"><li><p><tt class="literal">Add Date/Time to Backup Files</tt>: This determines whether the date and time of the backup operation are added to the name of the backup file. See <a href="#mysql-administrator-backup" title="Chapter12.
   Backup
  ">the backup section</a> for more information.</p></li></ul></div></div></div></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-appendix-tray-monitor"></a>AppendixA.
   The MySQL System Tray Monitor
  </h2></div></div><div></div></div><p>
   The MySQL System Tray Monitor is a tool that allows you to monitor the status of
   your local mysql server through an indicator that resides in the
   system tray. The MySQL System Tray Monitor also gives quick access to the
   various MySQL GUI tools through its context menu.
  </p><p>
   To start the MySQL System Tray Monitor, you can either execute the
   <tt class="literal">MySQLSystemTrayMonitor.exe</tt> application that
   resides in your MySQL Administrator installation directory, or choose the
   <span class="guimenu">MySQL System Tray Monitor</span> option of the
   <span class="guimenu">Tools</span> menu.
  </p><p>
   Once the MySQL System Tray Monitor is running, it resides in the system tray and
   provides visual status information for your MySQL server. A green
   icon is displayed at the top left corner of the MySQL System Tray Monitorif the
   MySQL server is running, and a red icon is displayed if the service
   is stopped. In addition, the CPU load may optionally be displayed
   along the right side of the MySQL System Tray Monitor.
  </p><div class="figure"><a name="id4749125"></a><p class="title"><b>FigureA.1.
    The MySQL System Tray Monitor
   </b></p><div><img src="images/system-tray.png" alt="The MySQL System Tray Monitor"></div></div><p>
   If you right-click on the MySQL System Tray Monitor, a pop-up menu will appear,
   listing all installed MySQL services and their individual statuses.
   For each service, the following options are available:
  </p><div class="itemizedlist"><ul type="disc"><li><p>
    <tt class="literal">Shutdown Instance:</tt> this will begin the shutdown
    operation on the selected running service.
   </p></li><li><p>
    <tt class="literal">Start Instance:</tt> this will start a currently
    stopped server instance.
   </p></li><li><p>
    <tt class="literal">Configure Instance:</tt> this will launch the
    MySQL Administrator in configure service mode for the currently selected
    instance. See
    <a href="#mysql-administrator-starting-configure-service" title="3.3.
    Configure-service Mode
   ">Configure
    Service Mode</a> for more details.
   </p></li><li><p>
    <tt class="literal">Monitoring Options:</tt> currently the
    <tt class="literal">Monitoring Options</tt> submenu has one available
    option: <tt class="literal">Ignore Instance State</tt>. <tt class="literal">Ignore
    Instance State</tt> will cause the MySQL System Tray Monitor to stop
    monitoring the selected service.
   </p></li></ul></div><p>
   In addition to the service controls, you can also start the
   MySQL Query Browser and MySQL Administrator from the pop-up menu.
  </p><p>
   The <tt class="literal">Manage MySQL Instances</tt> option of the
   <tt class="literal">Actions</tt> menu can be used to start MySQL Administrator
   in configure service mode so you can manage your server
   configurations. See
   <a href="#mysql-administrator-starting-configure-service" title="3.3.
    Configure-service Mode
   ">Configure
   Service Mode</a> for more details.
  </p><p>
   The <tt class="literal">Monitor Options</tt> menu has two options, which
   affect the general behavior of the MySQL System Tray Monitor. <tt class="literal">Display
   CPU Load</tt> determines whether the CPU usage is displayed on
   the right of the MySQL System Tray Monitor. <tt class="literal">Launch Monitor after Login
   </tt>

   <i><span class="remark">
    [MH] APPLICATION CAPITALIZATION ERROR
   </span></i>

   sets the MySQL System Tray Monitorto launch when you log into Windows.
  </p></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-gui-install-source"></a>AppendixB.Installing From Source</h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-gui-install-source-introduction">B.1. Introduction</a></span></dt><dt><span class="sect1"><a href="#mysql-gui-install-source-download">B.2. Downloading The Source Code</a></span></dt><dt><span class="sect1"><a href="#mysql-gui-install-source-windows">B.3. 
    Building from Source under Windows
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-gui-install-source-windows-prerequisites">B.3.1. 
     Prerequisites
    </a></span></dt><dt><span class="sect2"><a href="#mysql-gui-install-source-windows-compiling">B.3.2. 
     Compiling and Building
    </a></span></dt></dl></dd><dt><span class="sect1"><a href="#mysql-gui-install-source-linux">B.4. 
    Building from Source under Linux
   </a></span></dt><dd><dl><dt><span class="sect2"><a href="#mysql-gui-install-source-linux-prerequisites">B.4.1. 
     Prerequisites
    </a></span></dt><dt><span class="sect2"><a href="#mysql-gui-install-source-linux-compiling">B.4.2. 
     Compiling and Building
    </a></span></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-install-source-introduction"></a>B.1.Introduction</h2></div></div><div></div></div><p>
    Normally, you will want to install the MySQL GUI tools from binaries. We put a lot of effort into making sure that our binaries are built with the best possible options. If, for whatever reason, you wish to compile the tools yourself, follow these instructions.
   </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-install-source-download"></a>B.2.Downloading The Source Code</h2></div></div><div></div></div><p>
     You can get the source code of the MySQL GUI tools from our public
     BitKeeper trees. To be able to access trees, you have to have
     BitKeeper installed. BitKeeper is freely available from
     <a href="http://www.bitmover.com/" target="_top">Bitmover</a>. To
     run under Windows, BitKeeper requires Cygwin. If, during the
     installation process, BitKeeper finds that either Cygwin is not
     installed, or that the Cygwin version is too old, it will suggest
     to download and install Cygwin (or a newer version). You may,
     however, install Cygwin before installing BitKeeper. You can get
     Cygwin from
     <a href="http://www.cygwin.com/" target="_top">Cygwin.com</a>.
    </p><p>
     Our public BitKeeper trees that contain the MySQL GUI tools source
     code can be retrieved by the following BitKeeper commands:

</p><pre class="programlisting">
     bk clone bk://mysql.bkbits.net/mysql-administrator mysql-administrator
     bk clone bk://mysql.bkbits.net/mysql-gui-common mysql-gui-common
     bk clone bk://mysql.bkbits.net/mysql-query-browser mysql-query-browser
    </pre><p>

     You will need the <tt class="literal">mysql-gui-common</tt> tree regardless of which GUI tools you intend to build. The
     <tt class="literal">mysql-gui-common</tt> tree contains source and
     graphics files used for all MySQL GUI tools.</p><p>You can also download the source for the various GUI tools from the <a href="http://dev.mysql.com/downloads" target="_top">downloads page</a>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-install-source-windows"></a>B.3.
    Building from Source under Windows
   </h2></div></div><div></div></div><p>Installing from source under Windows requires multiple commercial compilers and because of this it is preferable to install from binaries. If you meet the prerequisites needed you can build the MySQL GUI tools from source under Windows.</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-gui-install-source-windows-prerequisites"></a>B.3.1.
     Prerequisites
    </h3></div></div><div></div></div><p>
     To compile the MySQL GUI tools from source under Windows, you need
     Borland Delphi 7, Microsoft Visual Studio.NET 2003, and some libraries which
     are available on the internet as open source software. Make sure the programs <tt class="literal">DCC32.exe</tt> and <tt class="literal">DEVENV.exe /?</tt> can be launched from the command line.
    </p><p>You will need the following libraries to build from source:</p><div class="itemizedlist"><ul type="disc"><li><p>glib-2.0</p></li><li><p>libxml-2</p></li><li><p>mysql client libraries (4.0 or newer, 5.0 prefered)</p></li><li><p>pcre-1.4</p></li><li><p>MS Visual C runtime libraries 7.1</p></li><li><p>Java include files 1.4.2_04</p></li><li><p>Lua 5.0.2</p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-gui-install-source-windows-compiling"></a>B.3.2.
     Compiling and Building
    </h3></div></div><div></div></div><p>
     Make sure you have cloned the <tt class="literal">mysql-administrator</tt>,
     <tt class="literal">mysql-gui-common</tt>, and <tt class="literal">mysql-query-browser</tt> trees, and that their local
     directories are located in the same directory, for example in
     <tt class="literal">Personal Files\MySQLGUI\</tt>.
    </p><p>The source files and libraries should be placed into the following tree structure:</p><pre class="programlisting">
  Working Directory
  |
  |- mysql-administrator
  |- mysql-gui-common
  |- mysql-query-browser
  |- mysql-gui-win-res
     |
     |-include
     | |
     | |-glib-2.0
     | |-java
     | | |
     | | |-win32
     | |
     | |-libxml
     | |-lua
     | |-mysql
     | |-pcre
     | |-windows
     |
     |-lib
       |
       |-glib-2.0
       |-java
       |-libxml
       |-lua
       |-mysql
       |-pcre
       |-windows
</pre><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-gui-install-source-windows-compiling-command-line"></a>B.3.2.1.Building from Command Line</h4></div></div><div></div></div><p>To build from the command line open a windows command line prompt and change into the main repository of the tool (i.e. for MySQL Administrator this is <tt class="literal">work\mysql-administrator</tt>). There are three batch-files to start the build:</p><div class="itemizedlist"><ul type="disc"><li><p>build_debug.cmd</p></li><li><p>build_release.cmd</p></li><li><p>build_commercial.cmd</p></li></ul></div><p>Execute one of those to generate a runtime image of the application. It will be generated in a <tt class="literal">bin\windows</tt> directory.</p><p>Another method is to doubleclick on one of the <tt class="literal">build_<i class="replaceable"><tt>buildtype</tt></i>.cmd</tt> files, where <i class="replaceable"><tt>buildtype</tt></i> is one of <tt class="literal">debug</tt>, <tt class="literal">release</tt>, and <tt class="literal">commercial</tt>. The <tt class="literal">commercial</tt> build script is for users with commercial licenses, and makes use of the commercial version of the MySQL client library.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-gui-install-source-windows-compiling-ide"></a>B.3.2.2.Building from the IDE</h4></div></div><div></div></div><p>Before you can open any projects, you have to install these components. Otherwise some of the forms will not open and you will receive error messages.</p><p>To install the components, goto the <tt class="literal">mysql-gui-common\source\windows\</tt> directory. Copy the following directories to your Delphi source directory (<tt class="literal">C:\Program Files\Borland\Delphi7\Source\</tt>).</p><div class="itemizedlist"><ul type="disc"><li><p>png</p></li><li><p>SynEdit</p></li><li><p>TNT</p></li><li><p>UniCodeEditor</p></li><li><p>VirtualTreeview</p></li></ul></div><p>Then doubleclick each <tt class="literal">*.dpk</tt> file outlined below. It will open Delphi. Press compile and install to install the components. Repeat this for each <tt class="literal">*.dpk</tt> file.</p><div class="itemizedlist"><ul type="disc"><li><p>SynEdit\Packages\SynEdit_D7.dpk</p></li><li><p>TNT\Packages\TntUnicodeVcl_D70.dpk</p></li><li><p>VirtualTreeview\Packages\VirtualTreesD7D.dpk</p></li><li><p>UniCodeEditor\Packages\UniCodeEditorD7.dpk</p></li></ul></div><p>These components have to be installed via the <span class="guimenu">Install</span> option of the <span class="guimenu">Component</span> menu. Click on the <span class="guibutton">Browse</span> button and select the the files below. Press <span class="guibutton">OK</span> after each file.</p><div class="itemizedlist"><ul type="disc"><li><p>png\PNGImage.pas</p></li></ul></div><p>After installing the components you can open the projects as outlined below.</p><p>To build the application from the Delphi 7 IDE simply doubleclick the <tt class="literal">edit_xxxx.cmd</tt>. This will launch Delphi 7 and open the file. To generate the complete runtime image select <span class="guimenu">Build All Projects</span> option from the <span class="guimenu">Project</span> menu.</p><p>Like for building from command line there are three different files.</p><div class="itemizedlist"><ul type="disc"><li><p>edit_debug.cmd</p></li><li><p>edit_release.cmd</p></li><li><p>edit_commercial.cmd</p></li></ul></div><p>The runtime image will be generated in a <tt class="literal">bin\windows</tt> directory.</p><p><span class="emphasis"><em>Opening the Delphi project not using the <tt class="literal">edit_*.cmd</tt> script will lead to incorrect project settings and problems while building the projects.</em></span></p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-install-source-linux"></a>B.4.
    Building from Source under Linux
   </h2></div></div><div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-gui-install-source-linux-prerequisites"></a>B.4.1.
     Prerequisites
    </h3></div></div><div></div></div><p>
     To be able to build the MySQL GUI tools from source, you need the
     following software:

     </p><div class="itemizedlist"><ul type="disc"><li><p>
       g++ development suite
      </p></li><li><p>
       gtk-2.x
      </p></li><li><p>
       gtkmm-2.0 or gtkmm-2.2
      </p></li><li><p>
       libglade-2.x
      </p></li><li><p>libxml-2.6.x</p></li><li><p> mysql client libraries (4.0 or newer, 5.0 prefered)</p></li><li><p> pcre-1.4</p></li><li><p> autoconf-2.54, automake-1.7.x</p></li></ul></div><p>
    
    In addition, you will need gtkhtml-3.0.x to build the MySQL Query Browser.
    </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="mysql-gui-install-source-linux-compiling"></a>B.4.2.
     Compiling and Building
    </h3></div></div><div></div></div><p>To build any of the tools, you need to have the bk tree for <tt class="literal">mysql-gui-common</tt> and the tree for the desired app (i.e.: <tt class="literal">mysql-administrator</tt>, <tt class="literal">mysql-query-browser</tt>) in the same top-level directory.</p><p>First build <tt class="literal">mysql-gui-common</tt>:</p><div class="orderedlist"><ol type="1"><li><p>cd mysql-gui-common</p></li><li><p>sh ./autogen.sh</p></li><li><p>./configure --prefix=/opt/mysql-<i class="replaceable"><tt>administrator</tt></i></p></li><li><p>make</p></li><li><p>make install</p></li></ol></div><p>The <tt class="literal">--prefix</tt> option can have whatever value you want, normally one would specify <tt class="literal">/usr/local</tt> (the default) or <tt class="literal">/usr</tt>, but for making precompiled binaries, something in <tt class="literal">/opt</tt> might be more appropriate.</p><p>After you have successfully built <tt class="literal">mysql-gui-common</tt>, you can build the individual tools (in this example we will build mysql-administrator):</p><div class="orderedlist"><ol type="1"><li><p>cd mysql-administrator</p></li><li><p>sh ./autogen.sh</p></li><li><p>./configure --prefix=/opt/mysql-<i class="replaceable"><tt>administrator</tt></i></p></li><li><p>make</p></li><li><p>make install</p></li></ol></div><p>If everything went well, things should be properly built and installed.</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-gui-install-source-linux-compiling-static"></a>B.4.2.1.Building Static Binaries</h4></div></div><div></div></div><p>Building static binaries is non-trivial under Linux, due to the enormous amount of library dependencies that come from GNOME and associated libraries. Additionally:</p><div class="itemizedlist"><ul type="disc"><li><p>Many libraries do not come with their static (lib*.a) versions shipped, so we need to build them ourselves.</p></li><li><p>Some libraries can't be linked statically, such as glibc, because of libnss*.so.</p></li><li><p>Some libraries depend on data files and modules from the original package, esp. in case of gtk/gnome. Problems don't just appear when the user don't have these data files installed; things may not work if they use distributions that put data files in different paths.</p></li></ul></div><p>The current solution is to build a partially static binary, with the most common libraries left dynamically linked (<tt class="literal">glibc</tt> and <tt class="literal">gtk</tt>). <tt class="literal">gtkmm</tt>, <tt class="literal">gtksourceview</tt>, <tt class="literal">gtkhtml</tt> and dependencies (like gnome) are being linked statically. The ideal solution would be to build custom binaries for each major/chosen distribution, but we don't have time/resources for that at the moment.</p><p>To build these binaries:</p><div class="orderedlist"><ol type="1"><li><p>Look at the <tt class="literal">source/linux/static_make</tt> script for all the files that should be removed/moved out of <tt class="literal">/usr/lib</tt>.</p></li><li><p>Run the script.</p></li></ol></div><p>That's needed to force the linker to look for the static version of each library and also to explicitly list the dependency libs that were otherwise linked to the dynamic libs.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="mysql-gui-install-source-linux-compiling-rpm"></a>B.4.2.2.Building RPMs</h4></div></div><div></div></div><p>For building RPMs, a spec file is already supplied and will be made automatically after <tt class="literal">./configure</tt> is ran. The spec file expects a source tarball with the following structure:</p><pre class="programlisting">mysql-administrator/ mysql-administrator/mysql-gui-common/* mysql-administrator/mysql-administrator/*</pre><p>The contents of each subdir is the entire bk tree for each tool (Windows specific files and bk metadata are optional, of course). You must make a tar.gz file and put it in <tt class="literal">/usr/src/redhat/SOURCES</tt> (or whatever is your rpm SOURCES directory).</p><p>Then, execute: <tt class="literal">rpmbuild -ba mysql-administrator.spec</tt></p><p>That should build the srpm and rpm files for the tool.</p></div></div></div></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-gui-appendix-troubleshooting"></a>AppendixC.
  Troubleshooting Application Errors
 </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-gui-appendix-troubleshooting-connection-errors">C.1. 
   Troubleshooting Connection Errors
  </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-appendix-troubleshooting-display-problems">C.2. 
   Troubleshooting Display Problems
  </a></span></dt></dl></div><p></p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-appendix-troubleshooting-connection-errors"></a>C.1.
   Troubleshooting Connection Errors
  </h2></div></div><div></div></div><p>
   If an error occurs when you select a connection profile and attempt
   to establish a connection to the MySQL server named in the profile, a
   window containing error information will be displayed (see figure).
  </p><div class="figure"><a name="id4751562"></a><p class="title"><b>FigureC.1.
    Error message dialog
   </b></p><div><img src="images/connectionerror.png" alt="Error message dialog"></div></div><p>
   Normally, this means either that the credentials specified in the
   profile are wrong (wrong username, wrong password), or that you do
   not have privileges to connect to the MySQL server from the client
   machine. You can find more information about the error in the
   <a href="http://dev.mysql.com/doc/mysql/en/Access_denied.html" target="_top">Causes
   of <tt class="literal">Access denied</tt> Errors</a> section of the
   reference manual.
  </p><p>
   However, another cause of connection failure is that there might be a
   network problem that prevents you from reaching the machine where the
   MySQL server is running. For this reason, the error dialog provides a
   <span class="guibutton">PING</span> button. Clicking this button will send an
   ICMP PING request to the MySQL server host machine. If the host
   machine is available over the network, you will see something like
   this:

</p><pre class="programlisting">
    Reply from 127.0.0.1: Time=0ms TTL=128
    Reply from 127.0.0.1: Time=1ms TTL=128
   </pre><p>

   This would indicate that the machine is reachable, and that the cause
   of connection failure is not a network problem.
  </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-appendix-troubleshooting-display-problems"></a>C.2.
   Troubleshooting Display Problems
  </h2></div></div><div></div></div><p>
   If, under Windows, the controls in the windows look somehow
   displaced, select <span class="guimenu">Start</span>, <span class="guimenu">Control
   Panel</span>, <span class="guimenu">Display</span>. Select the
   <span class="guilabel">Settings</span> tab and click the
   <span class="guibutton">Advanced...</span> button. Change your DPI settings
   to <tt class="literal">Normal (96 DPI)</tt>.
  </p><p>
   If, under Linux, messages and captions appear very big, your display
   resolution is probably set too high. Use
   <tt class="literal">gnome-font-properties</tt> to change your default font
   to a smaller value or go to <tt class="literal">Details</tt> and set your
   resolution to <tt class="literal">72</tt> or some other more appropriate
   value.
  </p></div></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-gui-appendix-store-connections"></a>AppendixD.
  How Connections Are Stored
 </h2></div></div><div></div></div><p>
  On Windows, connection profiles are stored in <tt class="literal">C:\Documents and
  Settings\<i class="replaceable"><tt>UserName</tt></i>\Application
  Data\MySQL</tt> directory, where
  <i class="replaceable"><tt>UserName</tt></i> is the name of the current Windows
  user. On Linux, the files are stored in the
  <tt class="literal">~/.mysqlgui</tt> directory. The settings are stored in a
  file called <tt class="literal">mysqlx_user_connections.xml</tt>. The
  contents of that file look like this:

</p><pre class="programlisting">

   &lt;?xml version="1.0"?&gt;
   &lt;user_connections&gt;
    &lt;last_connection&gt;1&lt;/last_connection&gt;
    &lt;password_storage_type&gt;2&lt;/password_storage_type&gt;
    &lt;user_connection&gt;
     &lt;connection_name&gt;&lt;/connection_name&gt;
     &lt;username&gt;root&lt;/username&gt;
     &lt;hostname&gt;localhost&lt;/hostname&gt;
     &lt;port&gt;3306&lt;/port&gt;
     &lt;schema&gt;&lt;/schema&gt;
     &lt;advanced_options/&gt;
     &lt;storage_path&gt;&lt;/storage_path&gt;
     &lt;notes&gt;&lt;/notes&gt;
     &lt;connection_type&gt;0&lt;/connection_type&gt;
     &lt;storage_type&gt;2&lt;/storage_type&gt;
     &lt;password&gt;&lt;/password&gt;
    &lt;/user_connection&gt;
    ...
  </pre><p>

  You can edit the file manually, but take care not to invalidate the
  XML. When applying changes by editing and saving the file, those
  changes will show up the next time you open the
  <a href="#mysql-gui-options-connections" title="17.3.
  Connections
 ">Connections</a>
  section of the <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options
  Dialog</a>. You do not need to restart your application for the
  changes to take effect.
 </p><p>
  As a database administrator, you may also edit the file according to
  your preferences, and then copy it to any other machine running the
  MySQL GUI tools. This makes it easy to have identical connection
  profiles on all machines, without having to set up those profiles
  individually. All XML configuration files for the MySQL GUI Tools are
  cross-platform compatible and can be transferred between Windows and
  Linux machines.
 </p></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-gui-appendix-xml-files"></a>AppendixE.
  XML Files Common to the MySQL GUI Applications
 </h2></div></div><div></div></div><p>
  On Windows, XML files common to all MySQL GUI applications are stored in the
  <tt class="literal">C:\Documents and
  Settings\<i class="replaceable"><tt>UserName</tt></i>\Application
  Data\MySQL</tt> directory, where
  <i class="replaceable"><tt>UserName</tt></i> is the name of the current Windows
  user. On Linux, the files are stored in the
  <tt class="literal">~/.mysqlgui</tt> directory.

  </p><div class="itemizedlist"><ul type="disc"><li><p>
    <tt class="literal">mysqlx_common_options.xml</tt>: Stores options
    selected in the <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options
    dialog</a>.
   </p></li><li><p>
    <tt class="literal">mysqlx_user_connections.xml</tt>: This file is
    described in
    <a href="#mysql-gui-appendix-store-connections" title="AppendixD.
  How Connections Are Stored
 ">How
    Connections are Stored</a>.
   </p></li></ul></div><p>
 </p></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-administrator-appendix-xml-files"></a>AppendixF.
   XML Files Used by MySQL Administrator
  </h2></div></div><div></div></div><p>
   Besides the documentation you are just reading (which is written in
   DocBook XML), MySQL Administrator uses a number of XML files for internal
   purposes.

   </p><div class="itemizedlist"><ul type="disc"><li><p>
     <tt class="literal">mysqlx-options.xml</tt>: Stores options selected in
     the <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options dialog</a>.
    </p></li><li><p>
     <tt class="literal">mysqlx-status-variables.xml</tt>: Stores the status
     variables known to MySQL Administrator, so that they can be assigned
     descriptions in various languages (see below for the XML file
     containing those descriptions). Those descriptions will show up in
     the
     <a href="#mysql-administrator-health-status-variables" title="10.5.
    Status Variables
   ">Status
     Variables</a> tab of the
     <a href="#mysql-administrator-health" title="Chapter10.
   Health
  ">Health</a>
     section. You can select the language of the descriptions in the
     <a href="#mysql-gui-options-general-options" title="17.2.
  General Options
 ">General
     Options</a> section of the
     <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options dialog</a>.
     That file also determines in which categories or subcategories a
     variable will appear, and the order in which categories and
     subcategories appear. It does not, however, determine in which
     order variables appear within a category or subcategory, as those
     are sorted lexically by MySQL Administrator.
    </p></li><li><p>
     <tt class="literal">mysqlx-system-variables.xml</tt>: Stores the system
     variables known to MySQL Administrator, so that they can be assigned
     descriptions in various languages (see below for the XML file
     containing those descriptions). Those descriptions will show up in
     the
     <a href="#mysql-administrator-health-system-variables" title="10.6.
    System Variables
   ">System
     Variables</a> tab of the
     <a href="#mysql-administrator-health" title="Chapter10.
   Health
  ">Health</a>
     section. You can select the language of the descriptions in the
     <a href="#mysql-gui-options-general-options" title="17.2.
  General Options
 ">General
     Options</a> section of the
     <a href="#mysql-gui-options" title="Chapter17.
 Options Dialog
">Options dialog</a>.
     That file also determines in which categories or subcategories a
     variable will appear, and the order in which categories and
     subcategories appear. It does not, however, determine in which
     order variables appear within a category or subcategory, as those
     are sorted lexically by MySQL Administrator.
    </p></li><li><p>
     <tt class="literal">mysqlx-translations-administrator.xml</tt> : Stores
     descriptions specific to MySQL Administrator, like descriptions for
     status and server variables, or category names, or labels used in
     dialogs. Here is an excerpt from that file, which contains English
     and German texts:

</p><pre class="programlisting">
     &lt;textgroup id="MySQLVariables"&gt;
      &lt;text id="status-var-group-General"&gt;
       &lt;trans xml:lang="en"&gt;General&lt;/trans&gt;
       &lt;trans xml:lang="de"&gt;Allgemein&lt;/trans&gt;
      &lt;/text&gt;
      &lt;text id="status-var-Uptime"&gt;
       &lt;trans xml:lang="en"&gt;How many seconds the server has been 
up.&lt;/trans&gt;
      &lt;/text&gt;
      ...
      &lt;textgroup id="Form-InstanceForm"&gt;
       &lt;text id="FileMI"&gt;
         &lt;trans xml:lang="en"&gt;&amp;File&lt;/trans&gt;
         &lt;trans xml:lang="de"&gt;&amp;Datei&lt;/trans&gt;
       &lt;/text&gt;
       &lt;text id="NewConnectionMI"&gt;
         &lt;trans xml:lang="en"&gt;&amp;New Connection 
...&lt;/trans&gt;
         &lt;trans xml:lang="de"&gt;&amp;Neue Verbindung 
...&lt;/trans&gt;
       &lt;/text&gt;
       &lt;text id="SaveConnectionMI"&gt;
         &lt;trans xml:lang="en"&gt;&amp;Save Connection 
...&lt;/trans&gt;
         &lt;trans xml:lang="de"&gt;Verbindung &amp;speichern 
...&lt;/trans&gt;
       &lt;/text&gt;
       &lt;text id="CloseMI"&gt;
         &lt;trans xml:lang="en"&gt;Clos&amp;e&lt;/trans&gt;
         &lt;trans xml:lang="de"&gt;Be&amp;enden&lt;/trans&gt;
       &lt;/text&gt;
      &lt;/textgroup&gt;
      ...
    </pre><p>

     From that excerpt, you can learn a number of things:

     </p><div class="itemizedlist"><ul type="circle"><li><p>
       A description (called <span class="emphasis"><em>text</em></span>) does not
       necessarily have to be translated (see
       <tt class="literal">status-var-Uptime</tt>). If it isn't, English will
       be used instead.
      </p></li><li><p>
       Adding another translation is as simple as adding another
       <tt class="literal">&lt;trans
       xml:lang="<i class="replaceable"><tt>language</tt></i>"&gt;</tt> tag.
      </p></li></ul></div><p>

     Therefore, translating the software is a painless task; however,
     please have a look at the
     <a href="#mysql-gui-appendix-notes-for-translators" title="AppendixG.
  Notes for Translators
 ">Notes
     for Translators</a> below!
    </p></li><li><p>
     <tt class="literal">mysqlx-translations-general.xml</tt>: Stores terms
     and descriptions that appear not only in MySQL Administrator, but also
     in other graphical MySQL programs. Its format, however, is
     identical with the format of the
     <tt class="literal">mysqlx-translations-administrator.xml</tt> file. Here
     is an excerpt from that file:

</p><pre class="programlisting">
     &lt;textgroup id="ResourceStrings"&gt;
      &lt;text id="OKBtn"&gt;
        &lt;trans xml:lang="en"&gt;OK&lt;/trans&gt;
      &lt;/text&gt;
      &lt;text id="CancelBtn"&gt;
        &lt;trans xml:lang="en"&gt;Cancel&lt;/trans&gt;
        &lt;trans xml:lang="de"&gt;Abbruch&lt;/trans&gt;
      &lt;/text&gt;
      ...
    </pre><p>
    </p></li><li><p>
     <tt class="literal">mysqlx-user-connections.xml</tt>: This file is
     described in
     <a href="#mysql-gui-appendix-store-connections" title="AppendixD.
  How Connections Are Stored
 ">How
     MySQL Administrator Stores Connections</a>.
    </p></li></ul></div><p>
  </p></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-gui-appendix-notes-for-translators"></a>AppendixG.
  Notes for Translators
 </h2></div></div><div></div></div><p>
  You may find that the MySQL GUI tools and/or their documentation are
  not available in your preferred language. If you would like to
  translate the software, or its documentation, or participate in that
  translation, <span class="emphasis"><em>please contact the MySQL documentation team
  before starting your translation!</em></span>
 </p><p>
  The MySQL documentation team's address is
  <tt class="email">&lt;<a href="mailto:docs@mysql.com">docs@mysql.com</a>&gt;</tt>. In your mail, please state what you
  would like to translate (the tools, their documentation, or even the
  whole MySQL reference manual if you dare), and give some information
  regarding your background:

  </p><div class="itemizedlist"><ul type="disc"><li><p>
    What is your name?
   </p></li><li><p>
    In which country and city are you located?
   </p></li><li><p>
    How long have you used MySQL?
   </p></li><li><p>
    Have you done other translations?
   </p></li><li><p>
    Will you work alone, or with a group of translators?
   </p></li><li><p>
    What's your timetable regarding the translation?
   </p></li><li><p>
    What is your motivation for translating?
   </p></li></ul></div><p>

  We will get back to you as soon as possible.
 </p><p>
  The format used for both software and documentation is
  <span class="emphasis"><em>DocBook XML</em></span>. From that base format, all other
  available formats (HTML, CHM, PDF, etc.) are being generated. It would
  be a pity if you started translating, say, the HTML version of this
  documentation, because we will not be able to use it in that format.
  Also, you might find that someone else has already done (or is in the
  process of doing) that translation. So, once again, please contact the
  MySQL documentation team first!
 </p></div><div class="appendix" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="mysql-gui-appendix-third-party-software"></a>AppendixH.
  Third-party Software Used by the MySQL GUI Tools
 </h2></div></div><div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="#mysql-gui-appendix-third-party-software-pcre">H.1. 
   PCRE Library
  </a></span></dt><dt><span class="sect1"><a href="#mysql-gui-appendix-third-party-software-png">H.2. 
   PNG Support
  </a></span></dt></dl></div><p>
  The MySQL GUI tools incorporate PCRE and PNG support through the use
  of third-party libraries.
 </p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-appendix-third-party-software-pcre"></a>H.1.
   PCRE Library
  </h2></div></div><div></div></div><p>
   Regular expression support is provided by the PCRE library package,
   which is open source software, written by Philip Hazel, and copyright
   by the University of Cambridge, England. The source for the PCRE
   library can be found at:
   <a href="ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/" target="_top">ftp:/
   /ftp.csx.cam.ac.uk/pub/software/programming/pcre/</a>.
  </p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="mysql-gui-appendix-third-party-software-png"></a>H.2.
   PNG Support
  </h2></div></div><div></div></div><p>
   PNG support for the Windows version is provided by the TPNGImage
   component which is open source software, written and copyright by
   Gustavo Daud. The source for the TPNGImage can be found at:
   <a href="http://pngdelphi.sourceforge.net" target="_top">
   http://pngdelphi.sourceforge.net </a>.
  </p></div></div></div></body></html>