Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.3034 05/07/16 04:33:22 jon@stripped +1 -0
Updating Installation chapter
for RefMan-5.0 (first part).
refman-5.0/installing.xml
1.20 05/07/16 04:33:21 jon@stripped +859 -1067
Updating for refman-5.0 (first part).
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: jon
# Host: gigan.
# Root: /home/jon/bk/mysqldoc
--- 1.19/refman-5.0/installing.xml 2005-07-15 02:56:00 +10:00
+++ 1.20/refman-5.0/installing.xml 2005-07-16 04:33:21 +10:00
@@ -9,6 +9,12 @@
]>
<chapter id='installing'>
+<!--
+ TODO: Change version number used in example filenames etc. to
+ 5.0. release version after release (currently using 5.0.9-beta as
+ a placeholder for these).
+-->
+
<title id='title-installing'>&title-installing;</title>
<!-- TODO: each major section needs intro about what's in section. -->
@@ -27,7 +33,7 @@
<listitem><para>
<emphasis role="bold">Determine whether your platform is
supported.</emphasis> Please note that not all supported systems are
- equally good for running MySQL on them. On some it is much more
+ equally suitable for running MySQL. On some pltforms it is much more
robust and efficient than others. See <xref linkend="which-os"/> for
details.
</para></listitem>
@@ -350,15 +356,15 @@
<para>
Based on the preceding criteria, the best platforms for running
- MySQL at this point are x86 with SuSE Linux using a 2.4 kernel, and
- ReiserFS (or any similar Linux distribution) and SPARC with Solaris
- (2.7-9). FreeBSD comes third, but we really hope it joins the top
- club once the thread library is improved. We also hope that at some
- point we is able to include into the top category all other
- platforms on which MySQL currently compiles and runs okay, but not
+ MySQL at this point are x86 with SuSE Linux using a 2.4 or 2.6
+ kernel, and ReiserFS (or any similar Linux distribution) and SPARC
+ with Solaris (2.7-9). FreeBSD comes third, but we really hope it
+ joins the top club once the thread library is improved. We also hope
+ that at some point we are able to include into the top category all
+ other platforms on which MySQL currently compiles and runs, but not
quite with the same level of stability and performance. This
requires some effort on our part in cooperation with the developers
- of the operating system and library components that MySQL depends
+ of the operating systems and library components that MySQL depends
on. If you are interested in improving one of those components, are
in a position to influence its development, and need more detailed
instructions on what MySQL needs to run better, send an email
@@ -385,17 +391,18 @@
<title id='title-which-version'>&title-which-version;</title>
-<!-- TODO: We need to define what a "release" is, i.e., when we assign a new -->
-
-<!-- version number a produce distributions that users can grab and install. -->
-
-<!-- Also, define "release series", and "distribution" (an installable package). -->
-
-<!-- TODO: This needs to describe the Standard/Max/Pro/Classic breakdown -->
-
-<!-- TODO: This needs to describe distribution formats as well -->
-
-<!-- (.tar.gz, RPM, PKG, .msi) -->
+<!--
+ TODO: We need to define what a "release" is, i.e., when we assign
+ a new version number and produce distributions that users can grab
+ and install. Also, define "release series", and "distribution" (an
+ installable package).
+-->
+
+<!-- TODO: This needs to describe the Standard/Max/etc breakdown. -->
+
+<!-- TODO: This needs to describe distribution formats as well.
+ (.tar.gz, RPM, PKG, .msi, etc.)
+-->
<para>
When preparing to install MySQL, you should decide which version to
@@ -441,55 +448,57 @@
<itemizedlist>
<listitem><para>
- MySQL 5.0 is the newest development release series and is under
- very active development for new features. Alpha releases have been
- issued to allow more widespread testing.
+ MySQL 5.1 is the next development release series and is the series
+ in which new features are to be implemented. Alpha releases will
+ be made avilable in the near future to allow widespread testing by
+ interested users.
</para></listitem>
<listitem><para>
- MySQL 4.1 is the current stable (production-quality) release
- series. New releases are issued for bugfixes. No new features are
- added that could diminish the code stability.
+ MySQL 5.0 is the current stable (production-quality) release
+ series. New releases are issued for bugfixes only; no new features
+ are being added that could effect stability.
</para></listitem>
<listitem><para>
- MySQL 4.0 is the previous stable (production-quality) release
- series. New releases are issued for bugfixes. No new features are
- added that could diminish the code stability.
+ MySQL 4.1 is the previous stable (production-quality) release
+ series. New releases are issued for critical bugfixes and security
+ fixes. No significant new features are to be added to this series.
</para></listitem>
<listitem><para>
- MySQL 3.23 is the old stable (production-quality) release series.
- This series is retired, so new releases are issued only to fix
- critical bugs.
+ MySQL 4.0 and 3.23 are the old stable (production-quality) release
+ series. These versions are now retired, so new releases are issued
+ only to fix extremely critical bugs (primarily security issues).
</para></listitem>
</itemizedlist>
<para>
- We don't believe in a complete freeze, as this also leaves out
- bugfixes and things that ``must be done.'' ``Somewhat frozen''
- means that we may add small things that ``almost surely do not
- affect anything that's currently working.'' Naturally, relevant
- bugfixes from an earlier series propagate to later series.
+ We do not believe in a complete freeze, as this also leaves out
+ bugfixes and and other fixes that must be done. By <quote>somewhat
+ frozen</quote> we mean that we may add small things that should
+ not affect anything that currently works in a production release.
+ Naturally, relevant bugfixes from an earlier series propagate to
+ later series.
</para>
<para>
Normally, if you are beginning to use MySQL for the first time or
trying to port it to some system for which there is no binary
distribution, we recommend going with the production release
- series. Currently this is MySQL 4.1. All MySQL releases, even those
+ series. Currently this is MySQL 5.0. All MySQL releases, even those
from development series, are checked with the MySQL benchmarks and
an extensive test suite before being issued.
</para>
<para>
- If you are running an old system and want to upgrade, but don't
+ If you are running an older system and want to upgrade, but do not
want to take the chance of having a non-seamless upgrade, you
should upgrade to the latest version in the same release series you
are using (where only the last part of the version number is newer
- than yours). We have tried to fix only fatal bugs and make small,
- relatively safe changes to that version.
+ than yours). We have tried to fix only fatal bugs and make only
+ small, relatively <quote>safe</quote> changes to that version.
</para>
<para>
@@ -502,8 +511,9 @@
<para>
If you want to use the very latest sources containing all current
patches and bugfixes, you can use one of our BitKeeper
- repositories. These are not ``releases'' as such, but are available
- as previews of the code on which future releases are based.
+ repositories. These are not <quote>releases</quote> as such, but
+ are available as previews of the code on which future releases are
+ to be based.
</para>
<indexterm type="concept">
@@ -519,29 +529,29 @@
<para>
The MySQL naming scheme uses release names that consist of three
numbers and a suffix; for example,
- <literal>mysql-4.1.2-alpha</literal>. The numbers within the
- release name are interpreted like this:
+ <emphasis role="bold">mysql-5.0.9-beta</emphasis>. The numbers
+ within the release name are interpreted as follows:
</para>
<itemizedlist>
<listitem><para>
- The first number (<literal>4</literal>) is the major version and
- also describes the file format. All Version 4 releases have the
- same file format.
+ The first number (<emphasis role="bold">5</emphasis>) is the major
+ version and describes the file format. All Version 5 releases have
+ the same file format.
</para></listitem>
<listitem><para>
- The second number (<literal>1</literal>) is the release level.
- Taken together, the major version and release level constitute the
- release series number.
+ The second number (<emphasis role="bold">0</emphasis>) is the
+ release level. Taken together, the major version and release level
+ constitute the release series number.
</para></listitem>
<listitem><para>
- The third number (<literal>2</literal>) is the version number
- within the release series. This is incremented for each new
- release. Usually you want the latest version for the series you
- have chosen.
+ The third number (<emphasis role="bold">9</emphasis>) is the
+ version number within the release series. This is incremented for
+ each new release. Usually you want the latest version for the
+ series you have chosen.
</para></listitem>
</itemizedlist>
@@ -564,37 +574,37 @@
<itemizedlist>
<listitem><para>
- <literal>alpha</literal> indicates that the release contains some
- large section of new code that hasn't been 100% tested. Known bugs
- (usually there are none) should be documented in the News section.
- See <xref linkend="news"/>. There are also new commands and
- extensions in most alpha releases. Active development that may
- involve major code changes can occur in an alpha release, but
- everything is tested before issuing a release. For this reason,
+ <emphasis role="bold">alpha</emphasis> indicates that the release
+ contains new features that have not been thoroughly tested. Known
+ bugs (usually there are none) should be documented in the News
+ section. See <xref linkend="news"/>. Most alpha releases implement
+ new commands and extensions. Active development that may involve
+ major code changes can occur in an alpha release. However, we do
+ conduct testing before issuing a release. For this reason,
there should be no known bugs in any MySQL release.
</para></listitem>
<listitem><para>
- <literal>beta</literal> means that we are feature complete and
- that all new code has been tested. No major new features that
- could cause corruption in old code are added. There should be no
+ <emphasis role="bold">beta</emphasis> means that the release is
+ intended to be feature-complete and that all new code has been
+ tested. No major new features that are added. There should be no
known critical bugs. A version changes from alpha to beta when
- there haven't been any reported fatal bugs within an alpha version
- for at least a month and we have no plans to add any features that
- could make any old command unreliable.
+ there have been no reported fatal bugs within an alpha version
+ for at least a month and we have no plans to add any new features
+ that could make previously implemented features unreliable.
</para>
<para>
- All API's, extern visible structures and columns for SQL commands
- will not change during future beta, release candidate, or
+ All API's, externally visible structures and columns for SQL
+ commands will not change during future beta, release candidate, or
production releases.
</para></listitem>
<listitem><para>
- <literal>rc</literal> is a release candidate; that is, a beta that
- has been around a while and seems to work fine. Only minor fixes
- are added. (A release candidate is what formerly was known as a
- gamma release.)
+ <emphasis role="bold">rc</emphasis> is a release candidate; that
+ is, a beta that has been around for a while and seems to work
+ well. Only minor fixes are added. (A release candidate is what
+ formerly was known as a gamma release.)
</para></listitem>
<listitem><para>
@@ -602,16 +612,17 @@
a while at many different sites with no reports of critical
repeatable bugs other than platform-specific bugs. Only critical
bugfixes are applied to the release. This is what we call a
- production (stable) or `General Availability' (GA) release.
+ production (stable) or <quote>General Availability</quote> (GA)
+ release.
</para></listitem>
</itemizedlist>
<para>
MySQL uses a naming scheme that is slightly different from most
- other products. In general, it's relatively safe to use any version
- that has been out for a couple of weeks without being replaced with
- a new version within the release series.
+ other products. In general, it is usually safe to use any version
+ that has been out for a couple of weeks without being replaced by
+ a new version within the same release series.
</para>
<para>
@@ -704,13 +715,12 @@
<listitem><para>
Binary distributions generally are easier to install than source
distributions.
- </para>
-
-<!-- TODO: This makes a false characterization of max vs. non-max as -->
-
-<!-- transactional vs. non-transactional. Replace this with descriptions -->
+ </para></listitem>
-<!-- of Standard/Max/Pro/Classic? --></listitem>
+<!-- TODO: This makes a false characterization of max vs. non-max as
+ transactional vs. non-transactional. Replace this with
+ descriptions of Standard/Max/Pro/Classic?
+-->
<listitem><para>
To satisfy different user requirements, we provide two different
@@ -745,7 +755,7 @@
<listitem><para>
You want to install MySQL at some explicit location. The standard
- binary distributions are ``ready to run'' at any place, but you
+ binary distributions are ready to run at any place, but you
may want to have even more flexibility to place MySQL components
where you want.
</para></listitem>
@@ -760,7 +770,8 @@
<itemizedlist>
<listitem><para>
- <literal>--with-innodb</literal> (default for MySQL 4.0 and up)
+ <literal>--with-innodb</literal> (enabled by default for all
+ MySQL 5.0 binary releases)
</para></listitem>
<listitem><para>
@@ -769,10 +780,6 @@
</para></listitem>
<listitem><para>
- <literal>--with-raid</literal>
- </para></listitem>
-
- <listitem><para>
<literal>--with-libwrap</literal>
</para></listitem>
@@ -842,23 +849,23 @@
</indexterm>
<para>
- MySQL is evolving quite rapidly here at MySQL AB and we want to
- share new developments with other MySQL users. We try to make a
- release when we have very useful features that others seem to have
- a need for.
+ MySQL is evolving quite rapidly and we want to share new
+ developments with other MySQL users. We try to produce a new
+ release whenever we have new and useful features that others also
+ seem to have a need for.
</para>
<para>
- We also try to help out users who request features that are easy to
- implement. We take note of what our licensed users want to have,
- and we especially take note of what our support customers want and
- try to help them out.
+ We also try to help users who request features that are easy to
+ implement. We take note of what our licensed users want, and we
+ especially take note of what our support customers want and try to
+ help them in this regard.
</para>
<para>
- No one has to download a new release. The News section tells you if
- the new release has something you really want. See
- <xref linkend="news"/>.
+ No one is <emphasis>required</emphasis> to download a new release.
+ The News section tells you if the new release has something you
+ really want. See <xref linkend="news"/>.
</para>
<para>
@@ -898,9 +905,9 @@
</para></listitem>
<listitem><para>
- If by any chance a fatal bug is found in a release, we make a new
- release as soon as possible. (We would like other companies to do
- this, too!)
+ If by any chance a fatal bug is found in a release, our policy is
+ to fix it in a new release as soon as possible. (We would like
+ other companies to do this, too!)
</para></listitem>
</itemizedlist>
@@ -914,8 +921,8 @@
<para>
We put a lot of time and effort into making our releases bug-free.
To our knowledge, we have not knowingly released a single MySQL
- version with any <emphasis>known</emphasis> ``fatal'' repeatable
- bugs. (A ``fatal'' bug is something that crashes MySQL under normal
+ version with any <emphasis>known</emphasis> fatal repeatable
+ bugs. (A <quote>fatal</quote> bug is something that crashes MySQL under normal
usage, produces incorrect answers for normal queries, or has a
security problem.)
</para>
@@ -926,8 +933,8 @@
</para>
<para>
- Our aim is to fix everything that is fixable without risk of making
- a stable MySQL version less stable. In certain cases, this means we
+ Our aim is to fix everything that is fixable without making a
+ stable MySQL version less stable. In certain cases, this means we
can fix an issue in the development versions, but not in the stable
(production) version. Naturally, we document such issues so that
users are aware of them.
@@ -953,8 +960,8 @@
<listitem><para>
When we fix a bug, we always try to make a test case for it and
include it into our test system to ensure that the bug can never
- recur without being detected. (About 90% of all fixed bugs have a
- test case.)
+ recur without being detected. (About 90% of all fixed bugs have
+ test cases.)
</para></listitem>
<listitem><para>
@@ -963,10 +970,10 @@
<listitem><para>
Before we start to build a new MySQL release, we ensure that all
- reported repeatable bugs for the MySQL version (3.23.x, 4.0.x,
- etc) are fixed. If something is impossible to fix (due to some
- internal design decision in MySQL), we document this in the
- manual. See <xref linkend="bugs"/>.
+ reported repeatable bugs for that MySQL version (3.23.x, 4.0.x,
+ 4.1.x, 5.0.x, and so on) are fixed. If something is impossible to
+ fix (due to some internal design decision in MySQL), we document
+ this in the manual. See <xref linkend="bugs"/>.
</para></listitem>
<listitem><para>
@@ -996,29 +1003,30 @@
<literal>announce</literal> mailing lists. See
<xref linkend="mailing-list"/>. The announcement message contains
a list of all changes to the release and any known problems with
- the release. The Known Problems section in the release notes has
- been needed for only a handful of releases.
+ the release. The <emphasis role="bold">Known Problems</emphasis>
+ section in the release notes has been needed for only a handful of
+ releases.
</para></listitem>
<listitem><para>
To quickly give our users access to the latest MySQL features, we
- do a new MySQL release every 4-8 weeks. Source code snapshots are
- built daily and are available at
+ produce a new MySQL release every 4-8 weeks. Source code snapshots
+ are built daily and are available at
<ulink url="http://downloads.mysql.com/snapshots.php"/>.
</para></listitem>
<listitem><para>
- If, despite our best efforts, we get any bug reports after the
- release is done that there was something critically wrong with the
- build on a specific platform, we fix it at once and build a new
- <literal>'a'</literal> release for that platform. Thanks to our
- large user base, problems are found quickly.
+ If, despite our best efforts, we receive any bug reports after the
+ release is made a critical problem with that build on a specific
+ platform, we fix it at once and build a new <literal>'a'</literal>
+ release for that platform. Thanks to our large user base, any such
+ problems are found and resolved very quickly.
</para></listitem>
<listitem><para>
Our track record for making stable releases is quite good. In the
last 150 releases, we had to do a new build for fewer than 10
- releases. In three of these cases, the bug was a faulty
+ of them. In three of these cases, the bug was a faulty
<literal>glibc</literal> library on one of our build machines that
took us a long time to track down.
</para></listitem>
@@ -1070,7 +1078,10 @@
<command>bin/mysqlbug</command> of every binary
<command>tar</command> file distribution.
</para>
-
+<!--
+ TODO: Verify that the info in this list is current. (Aren't we
+ doing any Linux builds with the 2.6 kernel yet?)
+-->
<para>
The following binaries are built on MySQL AB development systems:
</para>
@@ -1636,9 +1647,8 @@
</para>
<para>
- RPM distributions prior to MySQL 3.22 are user-contributed.
- Beginning with MySQL 3.22, RPM distributions are generated by MySQL
- AB.
+ The RPM distributions for MySQL 5.0 releases which we make
+ available through our website are generated by MySQL AB.
</para>
<para>
@@ -1763,8 +1773,8 @@
Example:
<programlisting>
-shell> md5sum mysql-standard-4.0.17-pc-linux-i686.tar.gz
-60f5fe969d61c8f82e4f7f62657e1f06 mysql-standard-4.0.17-pc-linux-i686.tar.gz
+ shell> md5sum mysql-standard-5.0.9-beta-linux-i686.tar.gz
+ aaab65abbec64d5e907dcd41b8699945 mysql-standard-5.0.9-beta-linux-i686.tar.gz
</programlisting>
</para>
@@ -1778,24 +1788,24 @@
<emphasis role="bold">Note</emphasis>: Make sure to verify the
checksum of the <emphasis role="bold">archive file</emphasis> (e.g.
the <literal>.zip</literal> or <literal>.tar.gz</literal> file) and
- not of the files that are contained inside of the archive!
+ not of the files that are contained inside of the archive.
</para>
<para>
Note that not all operating systems support the
- <literal>md5sum</literal> command. On some, it is simply called
- <literal>md5</literal> and others do not ship it at all. On Linux,
- it is part of the <literal>GNU Text Utilities</literal> package,
- which is available for a wide range of platforms. You can download
- the source code from
+ <command>md5sum</command> command. On some, it is simply called
+ <command>md5</command> and others do not ship it at all. On Linux,
+ it is part of the <emphasis role="bold">GNU Text
+ Utilities</emphasis> package, which is available for a wide range
+ of platforms. You can download the source code from
<ulink url="http://www.gnu.org/software/textutils/"/> as well. If
- you have <literal>OpenSSL</literal> installed, you can also use the
- command <literal>openssl md5 package_name</literal> instead. A
- DOS/Windows implementation of the <literal>md5</literal> command
- line utility is available from
- <ulink url="http://www.fourmilab.ch/md5/"/>. A graphical MD5
- checking tool is <literal>winMd5Sum</literal>, which can be
- obtained from <ulink url="http://winmd5sum.solidblue.biz/"/>.
+ you have OpenSSL installed, you can also use the command
+ <command>openssl md5 package_name</command> instead. A DOS/Windows
+ implementation of the <command>md5</command> command line utility
+ is available from <ulink url="http://www.fourmilab.ch/md5/"/>.
+ <command>winMd5Sum</command> is a graphical MD5 checking tool which
+ can be obtained from
+ <ulink url="http://winmd5sum.solidblue.biz/"/>.
</para>
</section>
@@ -1811,22 +1821,23 @@
</para>
<para>
- Beginning with MySQL 4.0.10 (February 2003), MySQL AB started
- signing downloadable packages with <literal>GnuPG</literal>
- (<literal>GNU Privacy Guard</literal>). <literal>GnuPG</literal> is
- an Open Source alternative to the very well-known <literal>Pretty
- Good Privacy</literal> (<literal>PGP</literal>) by Phil Zimmermann.
- See <ulink url="http://www.gnupg.org/"/> for more information about
- <literal>GnuPG</literal> and how to obtain and install it on your
- system. Most Linux distributions ship with <literal>GnuPG</literal>
- installed by default. For more information about
- <literal>OpenPGP</literal>, see
- <ulink url="http://www.openpgp.org/"/>.
- </para>
-
-<!-- Do not use @email with the key name, that comes out as <...> in -->
-
-<!-- some output formats, which are not part of the key name. -->
+ MySQL AB signs MySQL 5.0 downloadable packages with
+ <command>GnuPG</command> (GNU Privacy Guard).
+ <command>GnuPG</command> is an Open Source alternative to the
+ well-known Pretty Good Privacy (<command>PGP</command>) by Phil
+ Zimmermann. See <ulink url="http://www.gnupg.org/"/> for more
+ information about <command>GnuPG</command> and how to obtain and
+ install it on your system. Most Linux distributions ship with
+ <command>GnuPG</command> installed by default. For more
+ information about <command>GnuPG</command>, see
+ <ulink url="http://www.openpgp.org/"/>.
+ </para>
+
+<!--
+ Do not use @email with the key name, that comes out as
+ <...> in some output formats, which are not part of the key
+ name.
+-->
<para>
To verify the signature for a specific package, you first need to
@@ -1883,7 +1894,7 @@
<para>
You can import the build key into your personal public GPG keyring
- by using <literal>gpg --import</literal>. For example, if you save
+ by using <command>gpg --import</command>. For example, if you save
the key in a file named <filename>mysql_pubkey.asc</filename>, the
import command looks like this:
</para>
@@ -1915,7 +1926,7 @@
Distribution file
</entry>
<entry>
- <literal>mysql-standard-4.0.17-pc-linux-i686.tar.gz</literal>
+ <literal>mysql-standard-5.0.9-beta-linux-i686.tar.gz</literal>
</entry>
</row>
<row>
@@ -1923,7 +1934,7 @@
Signature file
</entry>
<entry>
- <literal>mysql-standard-4.0.17-pc-linux-i686.tar.gz.asc</literal>
+ <literal>mysql-standard-5.0.9-beta-linux-i686.tar.gz.asc</literal>
</entry>
</row>
</tbody>
@@ -1945,18 +1956,15 @@
</para>
<programlisting>
-shell> gpg --verify mysql-standard-4.0.17-pc-linux-i686.tar.gz.asc
-gpg: Warning: using insecure memory!
-gpg: Signature made Mon 03 Feb 2003 08:50:39 PM MET
-using DSA key ID 5072E1F5
-gpg: Good signature from
- "MySQL Package signing key (www.mysql.com) <build@stripped>"
+ shell> gpg --verify mysql-standard-5.0.9-beta-linux-i686.tar.gz.asc
+ gpg: Signature made Tue 12 Jul 2005 23:35:41 EST using DSA key ID 5072E1F5
+ gpg: Good signature from "MySQL Package signing key (www.mysql.com) <build@stripped>"
</programlisting>
<para>
The <literal>Good signature</literal> message indicates that
- everything is all right. You can ignore the <literal>insecure
- memory</literal> warning.
+ everything is all right. You can ignore any <literal>insecure
+ memory</literal> warning you might obtain.
</para>
</section>
@@ -1980,8 +1988,8 @@
</para>
<programlisting>
-shell> rpm --checksig MySQL-server-4.0.10-0.i386.rpm
-MySQL-server-4.0.10-0.i386.rpm: md5 gpg OK
+shell> rpm --checksig MySQL-server-5.0.9-0.i386.rpm
+MySQL-server-5.0.9-0.i386.rpm: md5 gpg OK
</programlisting>
<para>
@@ -2042,11 +2050,12 @@
</para>
<para>
- On Windows, the default installation directory is
- <filename>C:\mysql</filename>. With MySQL version 4.1.5 and higher,
- this has changed to <filename>C:\Program Files\MySQL\MySQL Server
- 4.1</filename>, where 4.1 is the major version of the installation.
- The folder has the following subdirectories:
+ For MySQL 5.0 on Windows, the default installation directory is
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0</filename>. (Some
+ Windows users prefer to install to the older default installation
+ directory <filename>C:\mysql</filename>. However, the layout of the
+ subdirectories remains the same.) The installation directory has the
+ following subdirectories:
</para>
<informaltable>
@@ -2131,8 +2140,8 @@
</informaltable>
<para>
- Installations created from Linux RPM distributions result in files
- under the following system directories:
+ Installations created from MySQL AB's Linux RPM distributions result
+ in files under the following system directories:
</para>
<informaltable>
@@ -2392,7 +2401,7 @@
</informaltable>
<para>
- Within an installation directory, the layout of a source
+ Within its installation directory, the layout of a source
installation differs from that of a binary installation in the
following ways:
</para>
@@ -2444,8 +2453,8 @@
The next several sections cover the installation of MySQL on
platforms where we offer packages using the native packaging format
of the respective platform. (This is also known as performing a
- ``binary install.'') However, binary distributions of MySQL are
- available for many other platforms as well. See
+ <quote>binary install</quote>.) However, binary distributions of
+ MySQL are available for many other platforms as well. See
<xref linkend="installing-binary"/> for generic installation
instructions for these packages that apply to all platforms.
</para>
@@ -2474,16 +2483,15 @@
</para>
<para>
- With the release of MySQL 4.1.5, MySQL AB has introduced a new
- installer for the Windows version of MySQL, combined with a new GUI
- Configuration Wizard. This combination automatically installs MySQL,
- creates an option file, starts the server, and secures the default
- user accounts.
+ The installer for the Windows version of MySQL 5.0, combined with a
+ GUI Configuration Wizard, automatically installs MySQL, creates an
+ option file, starts the server, and secures the default user
+ accounts.
</para>
<para>
- If you have installed a version of MySQL prior to version 4.1.5, you
- must perform the following steps:
+ If you are upgrading an existing installation of MySQL prior to
+ version 4.1.5, you must perform the following steps:
</para>
<orderedlist>
@@ -2516,7 +2524,7 @@
</para>
<para>
- MySQL for Windows is available in two distribution formats:
+ MySQL 5.0 for Windows is available in three distribution formats:
</para>
<itemizedlist>
@@ -2525,7 +2533,7 @@
The binary distribution contains a setup program that installs
everything you need so that you can start the server immediately.
</para></listitem>
-
+
<listitem><para>
The source distribution contains all the code and support files for
building the executables using the VC++ 6.0 compiler.
@@ -2534,9 +2542,9 @@
</itemizedlist>
<para>
- Generally speaking, you should use the binary distribution. It's
- simpler, and you need no additional tools to get MySQL up and
- running.
+ Generally speaking, you should use the binary distribution. It is
+ simpler to use than the others, and you need no additional tools to
+ get MySQL up and running.
</para>
<para>
@@ -2623,9 +2631,8 @@
<title id='title-windows-choosing-package'>&title-windows-choosing-package;</title>
<para>
- Starting with MySQL version 4.1.5, there are three install packages
- to choose from when installing MySQL on Windows. The Packages are as
- follows:
+ For MySQL 5.0, there are three installation packages to choose from
+ when installing MySQL on Windows. The packages are as follows:
</para>
<itemizedlist>
@@ -2633,17 +2640,17 @@
<listitem><para>
<emphasis role="bold">The Essentials Package</emphasis>: This
package has a filename similar to
- <filename>mysql-essential-4.1.9-win32.msi</filename> and contains
- the minimum set of files needed to install MySQL on Windows,
- including the Configuration Wizard. This package does not include
- optional components such as the embedded server and benchmark
- suite.
+ <filename>mysql-essential-5.0.9-beta-win32.msi</filename> and
+ contains the minimum set of files needed to install MySQL on
+ Windows, including the Configuration Wizard. This package does not
+ include optional components such as the embedded server and
+ benchmark suite.
</para></listitem>
<listitem><para>
<emphasis role="bold">The Complete Package</emphasis>: This package
has a filename similar to
- <filename>mysql-4.1.9-win32.zip</filename> and contains all files
+ <filename>mysql-5.0.9-beta-win32.zip</filename> and contains all files
needed for a complete Windows installation, including the
Configuration Wizard. This package includes optional components
such as the embedded server and benchmark suite.
@@ -2652,9 +2659,9 @@
<listitem><para>
<emphasis role="bold">The Noinstall Archive</emphasis>: This
package has a filename similar to
- <filename>mysql-noinstall-4.1.9-win32.zip</filename> and contains
- all the files found in the Complete install package, with the
- exception of the Configuration Wizard. This package does not
+ <filename>mysql-noinstall-5.0.9-beta-win32.zip</filename> and
+ contains all the files found in the Complete install package, with
+ the exception of the Configuration Wizard. This package does not
include an automated installer, and must be manually installed and
configured.
</para></listitem>
@@ -2681,11 +2688,10 @@
<title id='title-windows-using-installer'>&title-windows-using-installer;</title>
<para>
- Starting with MySQL 4.1.5, users can use the new MySQL Installation
- Wizard and MySQL Configuration Wizard to install MySQL on Windows.
- The MySQL Installation Wizard and MySQL Configuration Wizard are
- designed to install and configure MySQL in such a way that new users
- can immediately get started using MySQL.
+ New MySQL 5.0 users can use the MySQL Installation Wizard and MySQL
+ Configuration Wizard to install MySQL on Windows. These are designed
+ to install and configure MySQL in such a way that new users can
+ immediately get started using MySQL.
</para>
<para>
@@ -2697,13 +2703,6 @@
configuration.
</para>
- <para>
- If you are installing a version of MySQL prior to MySQL 4.1.5,
- please follow the instructions for installing MySQL from the
- Noinstall installation package. See
- <xref linkend="windows-install-archive"/>.
- </para>
-
</section>
<section id="windows-install-wizard">
@@ -2715,30 +2714,29 @@
<title id='title-mysql-install-wizard-introduction'>&title-mysql-install-wizard-introduction;</title>
<para>
- MySQL Installation Wizard is a new installer for the MySQL server
- that uses the latest installer technologies for Microsoft Windows.
- The MySQL Installation Wizard, in combination with the MySQL
+ MySQL Installation Wizard is an installer for the MySQL server that
+ uses the latest installer technologies for Microsoft Windows. The
+ MySQL Installation Wizard, in combination with the MySQL
Configuration Wizard, allows a user to install and configure a
MySQL server that is ready for use immediately after installation.
</para>
<para>
The MySQL Installation Wizard is the standard installer for all
- MySQL server distributions, version 4.1.5 and higher. Users of
- previous versions of MySQL need to manually shut down and remove
- their existing MySQL installations before installing MySQL with the
- MySQL Installation Wizard. See
- <xref linkend="mysql-install-wizard-upgrading"/> for more
- information on upgrading from a previous version.
+ MySQL 5.0 server distributions. Users of previous versions of MySQL
+ need to shut down and remove their existing MySQL installations
+ manually before installing MySQL with the MySQL Installation
+ Wizard. See <xref linkend="mysql-install-wizard-upgrading"/> for
+ more information on upgrading from a previous version.
</para>
<para>
Microsoft has included an improved version of their Microsoft
- Windows Installer (MSI) in the recent versions of Windows. Using
- the MSI has become the de-facto standard for application
- installations on Windows 2000, Windows XP, and Windows Server 2003.
- The MySQL Installation Wizard makes use of this technology to
- provide a smoother and more flexible installation progress.
+ Windows Installer (MSI) in the recent versions of Windows. MSI has
+ become the de-facto standard for application installations on
+ Windows 2000, Windows XP, and Windows Server 2003. The MySQL
+ Installation Wizard makes use of this technology to provide a
+ smoother and more flexible installation process.
</para>
<para>
@@ -2751,11 +2749,11 @@
</para>
<para>
- Further, Microsoft has introduced the WiX (Windows Installer XML)
- tool set recently. It is the first highly acknowledged Open Source
- project from Microsoft. We switched to WiX because it is an Open
- Source project and it allows us to handle the complete Windows
- installation process in a flexible way with scripts.
+ In addition, Microsoft has introduced the WiX (Windows Installer
+ XML) toolkit recently. This is the first highly acknowledged Open
+ Source project from Microsoft. We have switched to WiX because it
+ is an Open Source project and it allows us to handle the complete
+ Windows installation process in a flexible manner using scripts.
</para>
<para>
@@ -2768,93 +2766,68 @@
<!-- END INTRODUCTION -->
-<!-- @node mysql-install-wizard-versions, mysql-install-wizard-starting, mysql-install-wizard-introduction, Windows install wizard -->
-
-<!-- @subsubsection Choosing an Install Package -->
-
-<!-- -->
-
-<!-- There are three different packages available that you can use to -->
-
-<!-- install the MySQL server under Windows, each targeted at different -->
-
-<!-- user requirements: -->
-
-<!-- -->
-
-<!-- [MH] Looks like the GUI team changes these to Minimal and Full, -->
-
-<!-- and will eventually drop the Zip archives around the .MSI installers. -->
-
-<!-- Let's watch and change this when they do. -->
-
-<!-- -->
-
-<!-- @itemize @bullet -->
-
-<!-- -->
-
-<!-- @item -->
-
-<!-- @code{mysql-@var{version}-win-noinstall.zip}: -->
-
-<!-- This package is a simple Zip archive of all the files found in a -->
-
-<!-- full installation. It must be manually extracted and configured to -->
-
-<!-- be fully operational. If you are using this package, the rest of -->
-
-<!-- this document does not apply to you. -->
-
-<!-- -->
-
-<!-- @item -->
-
-<!-- @code{mysql-@var{version}-win.zip}: -->
-
-<!-- This package contains the MySQL Installation Wizard with all components of -->
-
-<!-- MySQL and is intended for a full installation with all optional -->
-
-<!-- packages. This is recommended for users who need additional -->
-
-<!-- components such as the embedded server, benchmark suite, and -->
-
-<!-- additional support scripts. -->
-
-<!-- -->
-
-<!-- @item -->
-
-<!-- @code{mysql-@var{version}-essential-win.msi}: -->
-
-<!-- This package contains the MySQL Installation Wizard with the minimum -->
-
-<!-- components required to install a working MySQL server, without any -->
-
-<!-- optional packages. This is recommended for typical users who do not -->
-
-<!-- need any optional packages such as the embedded server or the -->
-
-<!-- benchmark suite. Omitted packages can be added later. -->
-
-<!-- -->
-
-<!-- @end itemize -->
-
-<!-- -->
-
-<!-- For most users, the -->
-
-<!-- @code{mysql-@var{version}-essential-win.msi} -->
-<!-- package is recommended because of its smaller size and decreased -->
+<!-- @subsubsection Choosing an Install Package
+
+ There are three different packages available that you can use to
+ install the MySQL server under Windows, each targeted at different
+ user requirements:
+-->
+
+<!-- [MH] Looks like the GUI team changes these to Minimal and Full,
+ and will eventually drop the Zip archives around the .MSI
+ installers.
+
+ Let's watch and change this when they do.
+
+ [JS] Let's hope they do NOT drop the no-install zipfiles.
+-->
+
+
+<!--
+ @code{mysql-@var{version}-win-noinstall.zip}:
+
+ This package is a simple Zip archive of all the files found in a
+ full installation. It must be manually extracted and configured to
+ be fully operational. If you are using this package, the rest of
+ this document does not apply to you.
+-->
+
+<!--
+ @code{mysql-@var{version}-win.zip}:
+
+ This package contains the MySQL Installation Wizard with all
+ components of MySQL and is intended for a full installation with
+ all optional packages. This is recommended for users who need
+ additional components such as the embedded server, benchmark
+ suite, and additional support scripts.
+-->
+
+
+<!--
+ @code{mysql-@var{version}-essential-win.msi}:
+
+ This package contains the MySQL Installation Wizard with the
+ minimum components required to install a working MySQL server,
+ without any optional packages. This is recommended for typical
+ users who do not need any optional packages such as the embedded
+ server or the benchmark suite. Omitted packages can be added
+ later.
+-->
+
+<!-- For most users, the @code{mysql-@var{version}-essential-win.msi}
+ package is recommended because of its smaller size and decreased
+ download time.
+-->
+<!-- END CHOOSE PACKAGES -->
-<!-- download time. -->
+<!-- NOTE:
+ - "install" is a verb.
+ - "installation" is a noun.
+ - "install" is NOT a noun, it's a verb.
-<!-- -->
-
-<!-- END CHOOSE PACKAGES -->
+ Thank you. /JS
+-->
</section>
@@ -2863,7 +2836,7 @@
<title id='title-mysql-install-wizard-starting'>&title-mysql-install-wizard-starting;</title>
<para>
- The MySQL server install packages can be downloaded from
+ The MySQL server installation packages can be downloaded from
<ulink url="http://dev.mysql.com/downloads/"/>. If the package you
download is contained within a Zip archive, you need to extract the
archive first.
@@ -2871,10 +2844,11 @@
<para>
The process for starting the wizard depends on the contents of the
- install package you download. If there is a
- <literal>setup.exe</literal> file present, double-click it to start
- the install process. If there is a <literal>.msi</literal> file
- present, double-click it to start the install process.
+ installation package you download. If there is a
+ <filename>setup.exe</filename> file present, double-click it to
+ start the installation process. If there is a
+ <filename>.msi</filename> file present, double-click it to start
+ the installation process.
</para>
<!-- END STARTING -->
@@ -2886,46 +2860,50 @@
<title id='title-mysql-install-wizard-install-type'>&title-mysql-install-wizard-install-type;</title>
<para>
- There are up three installation types available:
- <literal>Typical</literal>, <literal>Complete</literal>, and
- <literal>Custom</literal>.
+ There are three installation types available:
+ <emphasis role="bold">Typical</emphasis>,
+ <emphasis role="bold">Complete</emphasis>, and
+ <emphasis role="bold">Custom</emphasis>.
</para>
<para>
- The <literal>Typical</literal> installation type installs the MySQL
- server, the <command>mysql</command> command-line client, and the
- command-line utilities. The command-line clients and utilities
- include <command>mysqldump</command>, <command>myisamchk</command>,
- and several other tools to help you manage the MySQL server.
+ The <emphasis role="bold">Typical</emphasis> installation type
+ installs the MySQL server, the <command>mysql</command>
+ command-line client, and the command-line utilities. The
+ command-line clients and utilities include
+ <command>mysqldump</command>, <command>myisamchk</command>,
+ and several other tools to help you manage the MySQL server.
</para>
<para>
- The <literal>Complete</literal> installation type installs all
- components included in the installation package. The full
- installation package includes components such as the embedded
- server library, the benchmark suite, support scripts, and
- documentation.
+ The <emphasis role="bold">Complete</emphasis> installation type
+ installs all components included in the installation package. The
+ full installation package includes components such as the embedded
+ server library, the benchmark suite, support scripts, and
+ documentation.
</para>
<para>
- The <literal>Custom</literal> installation type gives you complete
- control over which packages you wish to install and the
- installation path that is used. See
- <xref linkend="mysql-install-wizard-custom-install"/> for more
- information on performing a custom install.
+ The <emphasis role="bold">Custom</emphasis> installation type
+ gives you complete control over which packages you wish to install
+ and the installation path that is used. See
+ <xref linkend="mysql-install-wizard-custom-install"/> for more
+ information on performing a custom install.
</para>
<para>
- If you choose the <literal>Typical</literal> or
- <literal>Complete</literal> installation types and click the Next
- button, you advance to the confirmation screen to confirm your
- choices and begin the installation. If you choose the
- <literal>Custom</literal> installation type and click the Next
- button, you advance to the custom install dialog, described in
- <xref linkend="mysql-install-wizard-custom-install"/>
+ If you choose the <emphasis role="bold">Typical</emphasis> or
+ <emphasis role="bold">Complete</emphasis> installation types and
+ click the <guibutton>Next</guibutton> button, you advance to the
+ confirmation screen to verify your choices and begin the
+ installation. If you choose the
+ <emphasis role="bold">Custom</emphasis> installation type and
+ click the <guibutton>Next</guibutton> button, you advance to the
+ custom installation dialog, described in
+ <xref linkend="mysql-install-wizard-custom-install"/>
</para>
-<!-- END INSTALL TYPES -->
+<!-- END INSTALLATION TYPES -->
</section>
@@ -2936,29 +2914,32 @@
<para>
If you wish to change the installation path or the specific
components that are installed by the MySQL Installation Wizard, you
- should choose the <literal>Custom</literal> installation type.
+ should choose the <emphasis role="bold">Custom</emphasis>
+ installation type.
</para>
<para>
All available components are listed in a tree view on the left side
of the custom install dialog. Components that are not installed
- have a red <literal>X</literal> icon, components that are installed
+ have a red <guiicon>X</guiicon> icon; components that are installed
have a gray icon. To change whether a component is installed, click
- on the component's icon and choose an new option from the drop-down
+ on that component's icon and choose a new option from the drop-down
list that appears.
</para>
<para>
You can change the default installation path by clicking the
- Change... button to the right of the displayed installation path.
+ <guibutton>Change...</guibutton> button to the right of the
+ displayed installation path.
</para>
<para>
- After choosing your install components and installation path, click
- the Next button to advance to the confirmation dialog.
+ After choosing your installation components and installation path,
+ click the <guibutton>Next</guibutton> button to advance to the
+ confirmation dialog.
</para>
-<!-- END CUSTOM INSTALL -->
+<!-- END CUSTOM INSTALLATION -->
</section>
@@ -2975,9 +2956,10 @@
<para>
To install MySQL if you are satisfied with your settings, click the
- Install button. To change your settings, click the Back button. To
- exit the MySQL Installation Wizard without installing MySQL, click
- the Cancel button.
+ <guibutton>Install</guibutton> button. To change your settings,
+ click the <guibutton>Back</guibutton> button. To exit the MySQL
+ Installation Wizard without installing MySQL, click the
+ <guibutton>Cancel</guibutton> button.
</para>
<para>
@@ -3003,9 +2985,10 @@
<title id='title-mysql-install-wizard-changes'>&title-mysql-install-wizard-changes;</title>
<para>
- Once you click the Install button, the MySQL Installation Wizard
- begins the installation process and makes certain changes to your
- system which are described in the sections that follow.
+ Once you click the <guibutton>Install</guibutton> button, the MySQL
+ Installation Wizard begins the installation process and makes
+ certain changes to your system which are described in the sections
+ that follow.
</para>
<para>
@@ -3021,14 +3004,14 @@
<para>
The MySQL Installation Wizard creates a key named after the major
version of the server that is being installed, such as
- <literal>MySQL Server 4.1</literal>. It contains two string values,
+ <literal>MySQL Server 5.0</literal>. It contains two string values,
<literal>Location</literal> and <literal>Version</literal>. The
<literal>Location</literal> string contains the path to the
installation directory. In a default installation it contains
- <literal>C:\Program Files\MySQL\MySQL Server 4.1\</literal>. The
+ <literal>C:\Program Files\MySQL\MySQL Server 5.0\</literal>. The
<literal>Version</literal> string contains the release number. For
- example, for an installation of MySQL Server 4.1.5 the key contains
- a value of <literal>4.1.5</literal>.
+ example, for an installation of MySQL Server 5.0.9 the key contains
+ a value of <literal>5.0.9</literal>.
</para>
<para>
@@ -3048,40 +3031,41 @@
<para>
The MySQL Installation Wizard creates a new entry in the Windows
- Start menu under a common MySQL menu heading named after the major
- version of MySQL that you have installed. For example, if you
- install MySQL 4.1, the MySQL Installation Wizard creates a MySQL
- Server 4.1 section in the start menu.
+ <guimenu>Start</guimenu> menu under a common MySQL menu heading
+ named after the major version of MySQL that you have installed. For
+ example, if you install MySQL 5.0, the MySQL Installation Wizard
+ creates a <guisubmenu>MySQL Server 5.0</guisubmenu> section in the
+ <guimenu>Start</guimenu> menu.
</para>
<para>
- The following entries are created within the new Start menu
- section:
+ The following entries are created within the new
+ <guimenu>Start</guimenu> menu section:
</para>
<itemizedlist>
<listitem><para>
- <literal>MySQL Command Line Client</literal>: This is a shortcut
- to the <command>mysql</command> command-line client and is
- configured to connect as the <literal>root</literal> user. The
+ <guimenuitem>MySQL Command Line Client</guimenuitem>: This
+ is a shortcut to the <command>mysql</command> command-line client
+ and is configured to connect as the <literal>root</literal> user. The
shortcut prompts for a <literal>root</literal> user password when
connecting.
</para></listitem>
<listitem><para>
- <literal>MySQL Server Instance Config Wizard</literal>: This is a
- shortcut to the MySQL Configuration Wizard. Use this shortcut to
- configure a newly installed server, or to re-configure an existing
- server.
+ <guimenuitem>MySQL Server Instance Config Wizard</guimenuitem>:
+ This is a shortcut to the MySQL Configuration Wizard. Use this
+ shortcut to configure a newly installed server, or to re-configure
+ an existing server.
</para></listitem>
<listitem><para>
- <literal>MySQL Documentation</literal>: This is a link to the
- MySQL server documentation that is stored locally in the MySQL
+ <guimenuitem>MySQL Documentation</guimenuitem>: This is a link to
+ the MySQL server documentation that is stored locally in the MySQL
server installation directory. This option is not available when
- the MySQL server is installed from the
- <literal>essential</literal> installation package.
+ the MySQL server is installed using the Essentials installation
+ package.
</para></listitem>
</itemizedlist>
@@ -3096,26 +3080,25 @@
<para>
The MySQL Installation Wizard by default installs the MySQL server
- to <literal>C:\<replaceable>Program Files</replaceable>\MySQL\MySQL
- Server <replaceable>4.1</replaceable></literal>, where
+ to <filename>C:\<replaceable>Program Files</replaceable>\MySQL\MySQL
+ Server <replaceable>5.0</replaceable></filename>, where
<replaceable>Program Files</replaceable> is the default location
- for applications in your system, and <replaceable>4.1</replaceable>
+ for applications in your system, and <replaceable>5.0</replaceable>
is the major version of your MySQL server. This is the new
recommended location for the MySQL server, replacing the previous
- default location of <filename>c:\mysql</filename>.
+ default location <filename>c:\mysql</filename>.
</para>
<para>
By default, all MySQL applications are stored in a common directory
- at <literal>C:\<replaceable>Program
- Files</replaceable>\MySQL</literal>, where <replaceable>Program
+ at <filename>C:\<replaceable>Program
+ Files</replaceable>\MySQL</filename>, where <replaceable>Program
Files</replaceable> is the default location for applications in
your Windows installation. A typical MySQL installation on a
developer machine may look like this:
</para>
<programlisting>
-C:\Program Files\MySQL\MySQL Server 4.1
C:\Program Files\MySQL\MySQL Server 5.0
C:\Program Files\MySQL\MySQL Administrator 1.0
C:\Program Files\MySQL\MySQL Query Browser 1.0
@@ -3137,32 +3120,22 @@
<title id='title-mysql-install-wizard-upgrading'>&title-mysql-install-wizard-upgrading;</title>
<para>
- From MySQL version 4.1.5, the new MySQL Installation Wizard can
- perform server upgrades automatically using the upgrade
- capabilities of MSI. That means you do not need to remove a
- previous installation manually before installing a new release. The
- installer automatically shuts down and removes the previous MySQL
- service before installing the new version.
+ The MySQL Installation Wizard can perform server upgrades
+ automatically using the upgrade capabilities of MSI. That means you
+ do not need to remove a previous installation manually before
+ installing a new release. The installer automatically shuts down
+ and removes the previous MySQL service before installing the new
+ version.
</para>
<para>
- Automatic upgrades are only available when upgrading between
+ Automatic upgrades are available only when upgrading between
installations that have the same major and minor version numbers.
For example, you can upgrade automatically from MySQL 4.1.5 to
MySQL 4.1.6, but not from MySQL 4.1 to MySQL 5.0.
</para>
<para>
- <emphasis>If you are upgrading MySQL version 4.1.4 or earlier to
- version 4.1.5 or later, you must first manually shut down and
- remove the older installation before upgrading. Be sure to back up
- your databases before performing such an upgrade, so that you can
- restore the databases after the upgrade is completed. <emphasis>It
- is always recommended that you back up your data before performing
- any upgrades</emphasis>.</emphasis>
- </para>
-
- <para>
See <xref linkend="windows-upgrading"/>.
</para>
@@ -3190,16 +3163,14 @@
</para>
<para>
- The MySQL Configuration Wizard is included with the MySQL server
- starting with MySQL version 4.1.5, but is designed to work with
- MySQL servers versions 4.1 and higher. The MySQL Configuration
- Wizard is currently available for Windows users only.
+ The MySQL Configuration Wizard is included with the MySQL 5.0
+ server, and is currently available for Windows users only.
</para>
<para>
- MySQL Configuration Wizard is to a large extent the result of
+ The MySQL Configuration Wizard 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
+ several years. However, if you find that it lacks some feature
important to you, or if you discover a bug, please use our
<ulink url="http://bugs.mysql.com">MySQL Bug System</ulink> to
request features or report problems.
@@ -3217,12 +3188,13 @@
The MySQL Configuration Wizard is typically launched from the MySQL
Installation Wizard, as the MySQL Installation Wizard exits. You
can also launch the MySQL Configuration Wizard by clicking the
- MySQL Server Instance Config Wizard entry in the MySQL section of
- the <literal>Start</literal> menu.
+ <guimenuitem>MySQL Server Instance Config Wizard</guimenuitem>
+ entry in the <guisubmenu>MySQL</guisubmenu> section of the Windows
+ <guimenu>Start</guimenu> menu.
</para>
<para>
- In addition, you can navigate to the <literal>bin</literal>
+ In addition, you can navigate to the <filename>bin</filename>
directory of your MySQL installation and launch the
<filename>MySQLInstanceConfig.exe</filename> file directly.
</para>
@@ -3244,30 +3216,32 @@
</para>
<para>
- To reconfigure an existing server, choose the <literal>Re-configure
- Instance</literal> option and click the Next button. Your existing
- <filename>my.ini</filename> file is renamed to <literal>my
- <replaceable>timestamp</replaceable>.ini.bak</literal>, where
- <replaceable>timestamp</replaceable> is the date and time the
+ To reconfigure an existing server, choose the
+ <guimenuitem>Re-configure Instance</guimenuitem> option and click
+ the <guibutton>Next</guibutton> button. Your existing
+ <filename>my.ini</filename> file is renamed to
+ <filename>my<replaceable>timestamp</replaceable>.ini.bak</filename>,
+ where <replaceable>timestamp</replaceable> is the date and time the
existing <filename>my.ini</filename> file was created. To remove
- the existing server instance, choose the <literal>Remove
- Instance</literal> option and click the Next button.
+ the existing server instance, choose the <guimenuitem>Remove
+ Instance</guimenuitem> option and click the
+ <guibutton>Next</guibutton> button.
</para>
<para>
- If you choose the <literal>Remove Instance</literal> option, you
- advance to a confirmation window. Click the Execute button and the
- MySQL Configuration Wizard stops and removes the MySQL service and
- deletes the <filename>my.ini</filename> file. The server
- installation and its <literal>data</literal> folder are not
- removed.
+ If you choose the <guimenuitem>Remove Instance</guimenuitem>
+ option, you advance to a confirmation window. Click the
+ <guibutton>Execute</guibutton> button: the MySQL Configuration
+ Wizard stops and removes the MySQL service, then deletes the
+ <filename>my.ini</filename> file. The server installation and its
+ <filename>data</filename> folder are not removed.
</para>
<para>
- If you choose the <literal>Re-configure Instance</literal> option,
- you advance to the <literal>Configuration Type</literal> dialog
- where you can choose the type of installation you wish to
- configure.
+ If you choose the <guimenuitem>Re-configure Instance</guimenuitem>
+ option, you advance to the <guimenu>Configuration Type</guimenu>
+ dialog where you can choose the type of installation you wish to
+ configure.
</para>
<!-- END MAINTENANCE -->
@@ -3280,46 +3254,51 @@
<para>
When you start the MySQL Configuration Wizard for a new MySQL
- installation, or choose the <literal>Re-configure
- Instance</literal> option for an existing installation, you advance
- to the <literal>Configuration Type</literal> dialog.
+ installation, or choose the <guimenuitem>Re-configure
+ Instance</guimenuitem> option for an existing installation, you
+ advance to the <guimenu>Configuration Type</guimenu> dialog.
</para>
<para>
- There are two configuration types available: <literal>Detailed
- Configuration</literal> and <literal>Standard
- Configuration</literal>. The <literal>Standard
- Configuration</literal> option is intended for new users who want
- to get started with MySQL quickly without having to make a lot of
- decisions in regards to server configuration. The <literal>Detailed
- Configuration</literal> option is intended for advanced users who
- want more fine-grained control of server configuration.
+ There are two configuration types available:
+ <guimenuitem>Detailed Configuration</guimenuitem> and
+ <guimenuitem>Standard Configuration</guimenuitem>. The
+ <guimenuitem>Standard Configuration</guimenuitem> option is
+ intended for new users who want to get started with MySQL quickly
+ without having to make many decisions in regards to server
+ configuration. The
+ <guimenuitem>Detailed Configuration</guimenuitem> option is
+ intended for advanced users who want more fine-grained control over
+ server configuration.
</para>
<para>
- If you are new to MySQL and need a server configured as a
- single-user developer machine the <literal>Standard
- Configuration</literal> should suit your needs. Choosing the
- <literal>Standard Configuration</literal> option causes the MySQL
- Configuration Wizard to automatically set all configuration options
- with the exception of the <literal>Service Options</literal> and
- <literal>Security Options</literal>.
+ If you are new to MySQL and need a server configured as a
+ single-user developer machine the <guimenuitem>Standard
+ Configuration</guimenuitem> should suit your needs. Choosing the
+ <guimenuitem>Standard Configuration</guimenuitem> option causes
+ the MySQL Configuration Wizard to set all configuration options
+ automatically with the exception of <guimenuitem>Service
+ Options</guimenuitem> and <guimenuitem>Security
+ Options</guimenuitem>.
</para>
<para>
- The <literal>Standard Configuration</literal> sets options that may
- be incompatible with systems where there are existing MySQL
- installations. If you have an existing MySQL installation on your
- system in addition to the installation you wish to configure, the
- <literal>Detailed Configuration</literal> option is recommended.
+ The <guimenuitem>Standard Configuration</guimenuitem> sets options
+ that may be incompatible with systems where there are existing
+ MySQL installations. If you have an existing MySQL installation on
+ your system in addition to the installation you wish to configure,
+ the <guimenuitem>Detailed Configuration</guimenuitem> option is
+ recommended.
</para>
<para>
- To complete the <literal>Standard Configuration</literal>, please
- refer to the sections on <literal>Service Options</literal> and
- <literal>Security Options</literal>, located at
+ To complete the <guimenuitem>Standard Configuration</guimenuitem>,
+ please refer to the sections on <guimenuitem>Service
+ Options</guimenuitem> and <guimenuitem>Security
+ Options</guimenuitem>, at
<xref linkend="mysql-config-wizard-service"/> and
- <xref linkend="mysql-config-wizard-security"/> respectively.
+ <xref linkend="mysql-config-wizard-security"/>, respectively.
</para>
<!-- END STANDARD CONFIGURATION -->
@@ -3342,25 +3321,27 @@
<itemizedlist>
<listitem><para>
- <literal>Developer Machine</literal>: Choose this option for a
- typical desktop workstation where MySQL is intended only for
+ <guimenuitem>Developer Machine</guimenuitem>: Choose this option
+ for a typical desktop workstation where MySQL is intended only for
personal use. It is assumed that many other desktop applications
are running. The MySQL server is configured to use minimal system
resources.
</para></listitem>
<listitem><para>
- <literal>Server Machine</literal>: Choose this option for a server
- machine where the MySQL server is running alongside other server
- applications such as FTP, email, and web servers. The MySQL server
- is configured to use a medium portion of the system resources.
+ <guimenuitem>Server Machine</guimenuitem>: Choose this option for
+ a server machine where the MySQL server is running alongside other
+ server applications such as FTP, email, and web servers. The MySQL
+ server is configured to use a moderate portion of the system
+ resources.
</para></listitem>
<listitem><para>
- <literal>Dedicated MySQL Server Machine</literal>: Choose this
- option for a server machine that is intended to run only the MySQL
- server. It is assumed that no other applications are running. The
- MySQL server is configured to use all available system resources.
+ <guimenuitem>Dedicated MySQL Server Machine</guimenuitem>: Choose
+ this option for a server machine that is intended to run only the
+ MySQL server. It is assumed that no other applications are
+ running. The MySQL server is configured to use all available
+ system resources.
</para></listitem>
</itemizedlist>
@@ -3374,35 +3355,40 @@
<title id='title-mysql-config-wizard-database-usage'>&title-mysql-config-wizard-database-usage;</title>
<para>
- The <literal>Database Usage</literal> dialog allows you to indicate
+ The <guimenu>Database Usage</guimenu> dialog allows you to indicate
the table handlers you expect to use when creating MySQL tables.
- The option you choose determines whether the InnoDB table handler
- is available and what percentage of the server resources are
- available to InnoDB.
+ The option you choose determines whether the
+ <literal>InnoDB</literal> storage engine is available and what
+ percentage of the server resources are available to
+ <literal>InnoDB</literal>.
</para>
<itemizedlist>
<listitem><para>
- <literal>Multifunctional Database</literal>: This option enables
- both the InnoDB and MyISAM table handlers and divides resources
+ <guimenuitem>Multifunctional Database</guimenuitem>: This option
+ enables both the <literal>InnoDB</literal> and
+ <literal>MyISAM</literal> storage engines and divides resources
evenly between the two. This option is recommended for users that
- use both table handlers on a regular basis.
+ use both storage engines on a regular basis.
</para></listitem>
<listitem><para>
- <literal>Transactional Database Only</literal>: This option
- enables both the InnoDB and MyISAM table handlers but dedicates
- most server resources toward the InnoDB table handler. This option
- is recommended for users that use InnoDB almost exclusively and
- make only minimal use of MyISAM.
+ <guimenuitem>Transactional Database Only</guimenuitem>: This
+ option enables both the <literal>InnoDB</literal> and
+ <literal>MyISAM</literal> storage engines, but dedicates most
+ server resources to the <literal>InnoDB</literal> storage engine.
+ This option is recommended for users that use
+ <literal>InnoDB</literal> almost exclusively and make only minimal
+ use of <literal>MyISAM</literal>.
</para></listitem>
<listitem><para>
- <literal>Non-Transactional Database Only</literal>: This option
- disables the InnoDB table handler completely and dedicates all
- server resources to the MyISAM table handler. This option is
- recommended for users who do not use InnoDB.
+ <guimenuitem>Non-Transactional Database Only</guimenuitem>: This
+ option disables the <literal>InnoDB</literal> storage engine
+ completely and dedicates all server resources to the
+ <literal>MyISAM</literal> storage engine. This option is
+ recommended for users who do not use <literal>InnoDB</literal>.
</para></listitem>
</itemizedlist>
@@ -3416,25 +3402,27 @@
<title id='title-mysql-config-wizard-tablespace'>&title-mysql-config-wizard-tablespace;</title>
<para>
- Some users may want to locate the InnoDB tablespace files in a
- different location than the MySQL server data directory. Placing
- the tablespace files in a separate location can be desirable if
- your system has a higher capacity or higher performance storage
- device available, such as a RAID storage system.
+ Some users may want to locate the <literal>InnoDB</literal>
+ tablespace files in a different location than the MySQL server data
+ directory. Placing the tablespace files in a separate location can
+ be desirable if your system has a higher capacity or higher
+ performance storage device available, such as a RAID storage system.
</para>
<para>
- To change the default location for the InnoDB tablespace files,
- choose a new drive from the drop-down list of drive letters and
- choose a new path from the drop-down list of paths. To create a
- custom path, click the ... button.
+ To change the default location for the <literal>InnoDB</literal>
+ tablespace files, choose a new drive from the drop-down list of
+ drive letters and choose a new path from the drop-down list of
+ paths. To create a custom path, click the
+ <guibutton>...</guibutton> button.
</para>
<para>
If you are modifying the configuration of an existing server, you
- must click the Modify button before you change the path. In this
- situation you have to manually move the existing tablespace files
- to the new location before starting the server.
+ must click the <guibutton>Modify</guibutton> button before you
+ change the path. In this situation you must move the existing
+ tablespace files to the new location manually before starting the
+ server.
</para>
<!-- END TABLESPACE DIALOG -->
@@ -3448,34 +3436,35 @@
<para>
It is important to set a limit to the number of concurrent
connections to the MySQL server that can be established to prevent
- the server from running out of resources. The <literal>Concurrent
- Connections</literal> dialog allows you to choose the expected
+ the server from running out of resources. The <guimenu>Concurrent
+ Connections</guimenu> dialog allows you to choose the expected
usage of your server, and sets the limit for concurrent connections
- accordingly. It is also possible to manually set the concurrent
- connection limit.
+ accordingly. It is also possible to set the concurrent
+ connection limit manually.
</para>
<itemizedlist>
<listitem><para>
- <literal>Decision Support (DSS)/OLAP</literal>: Choose this option
- if your server does not require a large number of concurrent
- connections. The maximum number of connections is set at 100, with
- an average of 20 concurrent connections assumed.
+ <guimenuitem>Decision Support (DSS)/OLAP</guimenuitem>: Choose
+ this option if your server does not require a large number of
+ concurrent connections. The maximum number of connections is set
+ at 100, with an average of 20 concurrent connections assumed.
</para></listitem>
<listitem><para>
- <literal>Online Transaction Processing (OLTP)</literal>: Choose
- this option if your server requires a large number of concurrent
- connections. The maximum number of connections is set at 500.
+ <guimenuitem>Online Transaction Processing (OLTP)</guimenuitem>:
+ Choose this option if your server requires a large number of
+ concurrent connections. The maximum number of connections is set
+ at 500.
</para></listitem>
<listitem><para>
- <literal>Manual Setting</literal>: Choose this option to manually
- set the maximum number of concurrent connections to the server.
- Choose the number of concurrent connections from the drop-down box
- provided, or type the maximum number of connections into the
- drop-down box if the number you desire is not listed.
+ <guimenuitem>Manual Setting</guimenuitem>: Choose this option to
+ set the maximum number of concurrent connections to the server
+ manually. Choose the number of concurrent connections from the
+ drop-down box provided, or enter the maximum number of connections
+ into the drop-down box if the number you desire is not listed.
</para></listitem>
</itemizedlist>
@@ -3489,15 +3478,15 @@
<title id='title-mysql-config-wizard-networking'>&title-mysql-config-wizard-networking;</title>
<para>
- Use the <literal>Networking Options</literal> dialog to enable or
+ Use the <guimenu>Networking Options</guimenu> dialog to enable or
disable TCP/IP networking and to configure the port number that is
used to connect to the MySQL server.
</para>
<para>
TCP/IP networking is enabled by default. To disable TCP/IP
- networking, uncheck the box next to the <literal>Enable TCP/IP
- Networking</literal> option.
+ networking, uncheck the box next to the <guimenuitem>Enable TCP/IP
+ Networking</guimenuitem> option.
</para>
<para>
@@ -3520,30 +3509,31 @@
The MySQL server supports multiple character sets and it is
possible to set a default server character set that is applied to
all tables, columns, and databases unless overridden. Use the
- <literal>Character Set</literal> dialog to change the default
+ <guimenu>Character Set</guimenu> dialog to change the default
character set of the MySQL server.
</para>
<itemizedlist>
<listitem><para>
- <literal>Standard Character Set</literal>: Choose this option if
- you want to use <literal>Latin1</literal> as the default server
- character set. <literal>Latin1</literal> is used for English and
- many Western European languages.
+ <guimenuitem>Standard Character Set</guimenuitem>: Choose this
+ option if you want to use <literal>Latin1</literal> as the default
+ server character set. <literal>Latin1</literal> is used for
+ English and many Western European languages.
</para></listitem>
<listitem><para>
- <literal>Best Support For Multilingualism</literal>: Choose this
- option if you want to use <literal>UTF8</literal> as the default
- server character set. <literal>UTF8</literal> can store characters
- from many different languages in a single character set.
+ <guimenuitem>Best Support For Multilingualism</guimenuitem>:
+ Choose this option if you want to use <literal>UTF8</literal> as
+ the default server character set. <literal>UTF8</literal> can
+ store characters from many different languages in a single
+ character set.
</para></listitem>
<listitem><para>
- <literal>Manual Selected Default Character Set /
- Collation</literal>: Choose this option if you want to pick the
- server's default character set manually. Choose the desired
+ <guimenuitem>Manual Selected Default Character Set /
+ Collation</guimenuitem>: Choose this option if you want to pick
+ the server's default character set manually. Choose the desired
character set from the provided drop-down list.
</para></listitem>
@@ -3568,16 +3558,17 @@
The MySQL Configuration Wizard installs the MySQL server as a
service by default, using the service name
<literal>MySQL</literal>. If you do not wish to install the
- service, un-check the box next to the <literal>Install As Windows
- Service</literal> option. You can change the service name by
- picking a new service name from the drop-down box provided or by
- typing a new service name into the drop-down box.
+ service, uncheck the box next to the <guimenuitem>Install As
+ Windows Service</guimenuitem> option. You can change the service
+ name by picking a new service name from the drop-down box provided
+ or by entering a new service name into the drop-down box.
</para>
<para>
To install the MySQL server as a service but not have it started
- automatically at startup, un-check the box next to the
- <literal>Launch the MySQL Server automatically</literal> option.
+ automatically at startup, uncheck the box next to the
+ <guimenuitem>Launch the MySQL Server Automatically</guimenuitem>
+ option.
</para>
<!-- END SERVICE OPTIONS -->
@@ -3592,32 +3583,33 @@
It is strongly recommended that you set a <literal>root</literal>
password for your MySQL server, and the MySQL Configuration Wizard
requires you set a <literal>root</literal> password by default. If
- you do not wish to set a <literal>root</literal> password, un-check
- the box next to the <literal>Modify Security Settings</literal>
- option.
+ you do not wish to set a <literal>root</literal> password, uncheck
+ the box next to the <guimenuitem>Modify Security
+ Settings</guimenuitem> option.
</para>
<para>
- To set the <literal>root</literal> password, type the desired
- password into both the <literal>New root password</literal> and
- <literal>Confirm</literal> boxes. If you are re-configuring an
- existing server, you also need to enter the existing
- <literal>root</literal> password into the <literal>Current root
- password</literal> box.
+ To set the <literal>root</literal> password, enter the desired
+ password into both the <guimenuitem>New root password</guimenuitem>
+ and <guimenuitem>Confirm</guimenuitem> boxes. If you are
+ reconfiguring an existing server, you also need to enter the
+ existing <literal>root</literal> password into the
+ <guimenuitem>Current root password</guimenuitem> box.
</para>
<para>
To prevent <literal>root</literal> logins from across the network,
- check the box next to the <literal>Root may only connect from
- localhost</literal> option. This increases the security of your
+ check the box next to the <guimenuitem>Root may only connect from
+ localhost</guimenuitem> option. This increases the security of your
<literal>root</literal> account.
</para>
<para>
To create an anonymous user account, check the box next to the
- <literal>Create An Anonymous Account</literal> option. Creating an
- anonymous account can decrease server security and cause login and
- permission difficulties and is not recommended.
+ <guimenuitem>Create An Anonymous Account</guimenuitem> option.
+ Creating an anonymous account can decrease server security and
+ cause login and permission difficulties. For this reason, it is not
+ recommended.
</para>
<!-- END SECURITY OPTIONS -->
@@ -3630,23 +3622,24 @@
<para>
The final dialog in the MySQL Configuration Wizard is the
- <literal>Confirmation Dialog</literal>. To start the configuration
- process, click the Execute button. To return to a previous dialog,
- click the Back button. To exit the MySQL Configuration Wizard
- without configuring the server, click the Cancel button.
+ <guimenu>Confirmation Dialog</guimenu>. To start the configuration
+ process, click the <guibutton>Execute</guibutton>. To return to a
+ previous dialog, click the <guibutton>Back</guibutton> button. To
+ exit the MySQL Configuration Wizard without configuring the server,
+ click the <guibutton>Cancel</guibutton> button.
</para>
<para>
- After you click the Execute button, the MySQL Configuration Wizard
- performs a series of tasks with progress displayed onscreen as the
- tasks are performed.
+ After you click the <guibutton>Execute</guibutton> button, the
+ MySQL Configuration Wizard performs a series of tasks whose
+ progress is displayed onscreen as the tasks are performed.
</para>
<para>
- The MySQL Configuration Wizard firsts determines various
- configuration file options based on your choices using a template
- prepared by MySQL AB developers and engineers. This template is
- named <filename>my-template.ini</filename> and is located in your
+ The MySQL Configuration Wizard first determines configuration file
+ options based on your choices using a template prepared by MySQL AB
+ developers and engineers. This template is named
+ <filename>my-template.ini</filename> and is located in your
server installation directory.
</para>
@@ -3654,7 +3647,7 @@
The MySQL Configuration Wizard then writes these options to a
<filename>my.ini</filename> file. The final location of the
<filename>my.ini</filename> file is displayed next to the
- <literal>Write configuration file</literal> task.
+ <guilabel>Write configuration file</guilabel> task.
</para>
<para>
@@ -3673,8 +3666,8 @@
<para>
After the MySQL Configuration Wizard has completed its tasks, a
- summary is shown. Click the Finish button to exit the MySQL
- Configuration Wizard.
+ summary is displayed. Click the <guibutton>Finish</guibutton>
+ button to exit the MySQL Configuration Wizard.
</para>
<!-- END CONFIRMATION DIALOG -->
@@ -3686,16 +3679,8 @@
<title id='title-mysql-config-wizard-file-location'>&title-mysql-config-wizard-file-location;</title>
<para>
- In MySQL installations prior to version 4.1.5 it was customary to
- name the server configuration file <filename>my.cnf</filename> or
- <filename>my.ini</filename> and locate the file either at
- <filename>c:\my.cnf</filename> or
- <filename>c:\Windows\my.ini</filename>.
- </para>
-
- <para>
- The new MySQL Configuration Wizard places the
- <filename>my.ini</filename> file in the installation directory of
+ The MySQL Configuration Wizard places the
+ <filename>my.ini</filename> file in the installation directory for
the MySQL server. This helps associate configuration files with
particular server instances.
</para>
@@ -3705,8 +3690,8 @@
<filename>my.ini</filename> file, an argument similar to this is
passed to the MySQL server as part of the service installation:
<literal>--defaults-file="<replaceable>C:\Program Files\MySQL\MySQL
- Server 4.1</replaceable>\my.ini"</literal>, where
- <replaceable>C:\Program Files\MySQL\MySQL Server 4.1</replaceable>
+ Server 5.0</replaceable>\my.ini"</literal>, where
+ <replaceable>C:\Program Files\MySQL\MySQL Server 5.0</replaceable>
is replaced with the installation path to the MySQL Server.
</para>
@@ -3737,7 +3722,8 @@
to locate the <filename>my.ini</filename> file located in the
server installation directory. To configure the client and utility
applications, create a new <filename>my.ini</filename> file in the
- <filename>c:\Windows</filename> directory.
+ <filename>C:\Windows</filename> or <filename>C:\WINNT</filename>
+ directory as is applicable to your Windows version.
</para>
</section>
@@ -3751,16 +3737,9 @@
<!-- This is a new section, the next few sections will once again be subsections. -->
<para>
- Users who are installing from the Noinstall package, or who are
- installing a version of MySQL prior to 4.1.5 can use the
- instructions in this section to manually install MySQL. If you are
- installing a version prior to 4.1.5 with an install package that
- includes a Setup program, substitute running the Setup program for
- extracting the archive.
- </para>
-
- <para>
- The process for installing MySQL from a Zip archive is as follows:
+ Users who are installing from the Noinstall package can use the
+ instructions in this section to manually install MySQL. The process
+ for installing MySQL from a Zip archive is as follows:
</para>
<orderedlist>
@@ -3818,7 +3797,7 @@
<listitem><para>
Choose an installation location. Traditionally the MySQL server is
- installed at <filename>C:\mysql</filename>, and the new MySQL
+ installed in <filename>C:\mysql</filename>, and the MySQL
Installation Wizard installs MySQL to <filename>C:\Program
Files\MySQL</filename>. If you do not install MySQL at
<filename>C:\mysql</filename>, you must specify the path to the
@@ -3828,7 +3807,7 @@
<listitem><para>
Extract the install archive to the chosen installation location
- using your preferred Zip archive tool. Some tools may extract the
+ using your preferred zip archive tool. Some tools may extract the
archive to a folder within your chosen installation location. If
this occurs you can move the contents of the subfolder into the
chosen installation location.
@@ -3855,19 +3834,14 @@
<listitem><para>
The installation or data directory locations are different from the
- default locations (<filename>C:\mysql</filename> and
- <filename>C:\mysql\data</filename>).
+ default locations (<filename>C:\Program Files\MySQL\MySQL Server 5.0</filename> and
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename>).
</para></listitem>
+<!-- TODO: Add an example here. -->
+
<listitem><para>
- You need to tune the server settings. For example, to use the
- <literal>InnoDB</literal> transactional tables in MySQL 3.23, you
- must manually add some extra lines to the option file, as described
- in <xref linkend="innodb-configuration"/>. (As of MySQL 4.0,
- <literal>InnoDB</literal> creates its data files and log files in
- the data directory by default. This means you need not configure
- <literal>InnoDB</literal> explicitly. You may still do so if you
- wish, and an option file is useful in this case, too.)
+ You need to tune the server settings.
</para></listitem>
</itemizedlist>
@@ -3877,7 +3851,7 @@
files: the <filename>my.ini</filename> file in the Windows
directory, and the <filename>C:\my.cnf</filename> file. The Windows
directory typically is named something like
- <filename>C:\WINDOWS</filename> or <filename>C:\WinNT</filename>.
+ <filename>C:\WINDOWS</filename> or <filename>C:\WINNT</filename>.
You can determine its exact location from the value of the
<literal>WINDIR</literal> environment variable using the following
command:
@@ -3891,27 +3865,28 @@
MySQL looks for options first in the <filename>my.ini</filename>
file, then in the <filename>my.cnf</filename> file. However, to
avoid confusion, it's best if you use only one file. If your PC uses
- a boot loader where the <literal>C:</literal> drive isn't the boot
- drive, your only option is to use the <filename>my.ini</filename>
- file. Whichever option file you use, it must be a plain text file.
+ a boot loader where <filename>C:</filename> is not the boot drive,
+ your only option is to use the <filename>my.ini</filename> file.
+ Whichever option file you use, it must be a plain text file.
</para>
<para>
You can also make use of the example option files included with your
MySQL distribution. Look in your install directory for files such as
- my-small.cnf, my-medium.cnf, my-large.cnf, etc., which you can
- rename and copy to the appropriate location for use as a base
- configuration file.
+ <filename>my-small.cnf</filename>, <filename>my-medium.cnf</filename>,
+ <filename></filename>my-large.cnf, and
+ <filename>my-huge.cnf</filename>, which you can rename and copy to
+ the appropriate location for use as a base configuration file.
</para>
<para>
An option file can be created and modified with any text editor,
- such as the <literal>Notepad</literal> program. For example, if
- MySQL is installed at <filename>E:\mysql</filename> and the data
- directory is located at <filename>E:\mydata\data</filename>, you can
- create the option file and set up a <literal>[mysqld]</literal>
- section to specify values for the <literal>basedir</literal> and
- <literal>datadir</literal> parameters:
+ such as Notepad. For example, if MySQL is installed in
+ <filename>E:\mysql</filename> and the data directory is in
+ <filename>E:\mydata\data</filename>, you can create an option file
+ containing a <literal>[mysqld]</literal> section to specify values
+ for the <literal>basedir</literal> and <literal>datadir</literal>
+ parameters:
</para>
<programlisting>
@@ -3924,7 +3899,7 @@
<para>
Note that Windows pathnames are specified in option files using
- forward slashes rather than backslashes. If you do use backslashes,
+ (forward) slashes rather than backslashes. If you do use backslashes,
you must double them:
</para>
@@ -3941,16 +3916,18 @@
under the directory where you install MySQL. If you would like to
use a data directory in a different location, you should copy the
entire contents of the <filename>data</filename> directory to the
- new location. For example, by default, the installer places MySQL in
- <filename>C:\mysql</filename> and the data directory in
- <filename>C:\mysql\data</filename>. If you want to use a data
- directory of <filename>E:\mydata</filename>, you must do two things:
+ new location. For example, if MySQL is installed in
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0</filename> the data directory is by default in
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename>. If you want to use
+ <filename>E:\mydata</filename> as the data directory instead, then
+ you must do two things:
</para>
- <itemizedlist>
+ <orderedlist>
<listitem><para>
- Move the data directory from <filename>C:\mysql\data</filename> to
+ Move the entire data directory and all of its contents from
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename> to
<filename>E:\mydata</filename>.
</para></listitem>
@@ -3959,7 +3936,7 @@
directory location each time you start the server.
</para></listitem>
- </itemizedlist>
+ </orderedlist>
</section>
@@ -3967,108 +3944,9 @@
<title id='title-windows-select-server'>&title-windows-select-server;</title>
-<!-- [MH] HOW LONG DO WE WANT TO SUPPORT DOCUMENTING THE INSTALLATION OF -->
-
-<!-- A DEPRECATED VERSION? CAN WE ASSSUME THAT WHEN OLDER VERSIONS ARE NO -->
-
-<!-- DOWNLOADABLE WE DROP THIS? -->
-
- <para>
- Starting with MySQL 3.23.38, the Windows distribution includes both
- the normal and the MySQL-Max server binaries.
- </para>
-
<para>
- Up through the early releases of MySQL 4.1, the servers included in
- Windows distributions are named like this:
- </para>
-
- <informaltable>
- <tgroup cols="2">
- <colspec colwidth="20*"/>
- <colspec colwidth="80*"/>
- <tbody>
- <row>
- <entry>
- <emphasis role="bold">Binary</emphasis>
- </entry>
- <entry>
- <emphasis role="bold">Description</emphasis>
- </entry>
- </row>
- <row>
- <entry>
- <command>mysqld</command>
- </entry>
- <entry>
- Compiled with full debugging and automatic memory allocation
- checking, and <literal>InnoDB</literal> and
- <literal>BDB</literal> tables.
- </entry>
- </row>
- <row>
- <entry>
- <command>mysqld-opt</command>
- </entry>
- <entry>
- Optimized binary. From version 4.0 on,
- <literal>InnoDB</literal> is enabled. Before 4.0, this
- server includes no transactional table support.
- </entry>
- </row>
- <row>
- <entry>
- <command>mysqld-nt</command>
- </entry>
- <entry>
- Optimized binary for Windows NT, 2000, and XP with support
- for named pipes.
- </entry>
- </row>
- <row>
- <entry>
- <command>mysqld-max</command>
- </entry>
- <entry>
- Optimized binary with support for <literal>InnoDB</literal>
- and <literal>BDB</literal> tables.
- </entry>
- </row>
- <row>
- <entry>
- <command>mysqld-max-nt</command>
- </entry>
- <entry>
- Like <command>mysqld-max</command>, but compiled with
- support for named pipes.
- </entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>
- We have found that the server with the most generic name
- (<command>mysqld</command>) is the one that many users are likely to
- choose by default. However, that is also the server that results in
- the highest memory and CPU use due to the inclusion of full
- debugging support. The server named <command>mysqld-opt</command> is
- a better general-use server choice to make instead if you don't need
- debugging support and don't want the maximal feature set offered by
- the <literal>-max</literal> servers or named pipe support offered by
- the <literal>-nt</literal> servers.
- </para>
-
- <para>
- To make it less likely that the debugging server would be chosen
- inadvertently, some name changes were made from MySQL 4.1.2 to
- 4.1.4: <command>mysqld</command> has been renamed to
- <command>mysqld-debug</command> and <command>mysqld-opt</command>
- has been renamed to <command>mysqld</command>. Thus, the server that
- includes debugging support indicates that in its name, and the
- server named <command>mysqld</command> is an efficient default
- choice. The other servers still have their same names. The resulting
- servers are named like this:
+ The following table shows the available MySQL 5.0 servers for
+ Windows:
</para>
<informaltable>
@@ -4090,7 +3968,7 @@
</entry>
<entry>
Compiled with full debugging and automatic memory allocation
- checking, and <literal>InnoDB</literal> and
+ checking, as well as <literal>InnoDB</literal> and
<literal>BDB</literal> tables.
</entry>
</row>
@@ -4134,25 +4012,14 @@
</informaltable>
<para>
- The name changes were not both instituted at the same time. If you
- have MySQL 4.1.2 or 4.1.3, it might be that you have a server named
- <command>mysqld-debug</command> but not one named
- <command>mysqld</command>. In this case, you should have a server
- <command>mysqld-opt</command>, which you should choose as your
- default server unless you need maximal features, named pipes, or
- debugging support.
- </para>
-
- <para>
All of the preceding binaries are optimized for modern Intel
processors, but should work on any Intel i386-class or higher
processor.
</para>
<para>
- As of MySQL 4.0, all Windows servers have support for symbolic
- linking of database directories. Before MySQL 4.0, only the
- debugging and Max server versions include this feature.
+ In MySQL 5.0, all Windows servers have support for symbolic linking
+ of database directories.
</para>
<indexterm type="concept">
@@ -4167,30 +4034,31 @@
MySQL supports TCP/IP on all Windows platforms. The
<command>mysqld-nt</command> and <literal>mysql-max-nt</literal>
servers support named pipes on Windows NT, 2000, XP, and 2003.
- However, the default is to use TCP/IP regardless of the platform.
- (Named pipes are slower than TCP/IP in many Windows configurations.)
-
-<!-- WHEN IS THIS TRUE? CAN WE BE MORE SPECIFIC ABOUT WHEN NAMED PIPES -->
+ However, the default is to use TCP/IP regardless of platform. (Named
+ pipes are slower than TCP/IP in many Windows configurations.)
</para>
-
-<!-- ARE SLOWER THAN TCP/IP? -->
+
+<!--
+ WHEN IS THIS TRUE? CAN WE BE MORE SPECIFIC ABOUT WHEN NAMED PIPES
+ ARE SLOWER THAN TCP/IP?
+-->
<para>
- Named pipe use is subject to these conditions:
+ Use of named pipes is subject to these conditions:
</para>
<itemizedlist>
<listitem><para>
- Starting from MySQL 3.23.50, named pipes are enabled only if you
- start the server with the <literal>--enable-named-pipe</literal>
- option. It is necessary to use this option explicitly because some
- users have experienced problems shutting down the MySQL server when
- named pipes were used.
+ Named pipes are enabled only if you start the server with the
+ <literal>--enable-named-pipe</literal> option. It is necessary to
+ use this option explicitly because some users have experienced
+ problems with shutting down the MySQL server when named pipes were
+ used.
</para></listitem>
<listitem><para>
- Named pipe connections are allowed only by the
+ Named pipe connections are allowed only by the
<command>mysqld-nt</command> or <command>mysqld-max-nt</command>
servers, and only if the server is run on a version of Windows that
supports named pipes (NT, 2000, XP, 2003).
@@ -4221,6 +4089,17 @@
<title id='title-windows-server-first-start'>&title-windows-server-first-start;</title>
+<!--
+ TODO: See if we can't drop the Win9x and NT4 stuff. How likely is
+ it that any of our users are going to be running one of these?
+-->
+ <para>
+ The informaiton in this section applies primarily if you installed
+ MySQL using the <literal>Noinstall</literal> version, or if you
+ wish to configure and test MySQL manually rather than with the GUI
+ tools.
+ </para>
+
<para>
On Windows 95, 98, or Me, MySQL clients always connect to the server
using TCP/IP. (This allows any machine on your network to connect to
@@ -4231,8 +4110,8 @@
<para>
Note that if you are using an old Windows 95 release (for example,
- OSR2), it's likely that you have an old Winsock package; MySQL
- requires Winsock 2! You can get the newest Winsock from
+ OSR2), it is likely that you have an old Winsock package; MySQL
+ requires Winsock 2. You can get the newest Winsock from
<ulink url="http://www.microsoft.com/"/>. Windows 98 has the new
Winsock 2 library, so it is unnecessary to update the library.
</para>
@@ -4246,10 +4125,9 @@
</para>
<para>
- In MySQL versions 4.1 and higher, Windows servers also support
- shared-memory connections if started with the
- <literal>--shared-memory</literal> option. Clients can connect
- through shared memory by using the
+ MySQL 5.0 for Windows also supports shared-memory connections if
+ started with the <literal>--shared-memory</literal> option. Clients
+ can connect through shared memory by using the
<literal>--protocol=memory</literal> option.
</para>
@@ -4267,17 +4145,17 @@
<para>
The examples in these sections assume that MySQL is installed under
- the default location of <filename>C:\mysql</filename>. Adjust the
+ the default location of <filename>C:\Program Files\MySQL\MySQL Server 5.0</filename>. Adjust the
pathnames shown in the examples if you have MySQL installed in a
different location.
</para>
<para>
- Testing is best done from a command prompt in a console window (a
- ``DOS window''). This way you can have the server display status
- messages in the window where they are easy to see. If something is
- wrong with your configuration, these messages make it easier for you
- to identify and fix any problems.
+ Testing is best done from a command prompt in a console window (or
+ <quote>DOS window</quote>). In this way you can have the server
+ display status messages in the window where they are easy to see. If
+ something is wrong with your configuration, these messages make it
+ easier for you to identify and fix any problems.
</para>
<para>
@@ -4285,7 +4163,7 @@
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqld --console
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --console
</programlisting>
<para>
@@ -4319,7 +4197,7 @@
<programlisting>
mysqld: ready for connections
-Version: '4.0.14-log' socket: '' port: 3306
+Version: '5.0.9-beta' socket: '' port: 3306
</programlisting>
<para>
@@ -4331,7 +4209,7 @@
<para>
If you omit the <literal>--console</literal> option, the server
writes diagnostic output to the error log in the data directory
- (<filename>C:\mysql\data</filename> by default). The error log is
+ (<filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename> by default). The error log is
the file with the <filename>.err</filename> extension.
</para>
@@ -4355,8 +4233,8 @@
<para>
To start the <command>mysqld</command> server from the command line,
- you should start a console window (a ``DOS window'') and enter this
- command:
+ you should start a console window (or <quote>DOS window</quote>) and
+ enter this command:
</para>
<programlisting>
@@ -4400,7 +4278,7 @@
If <command>mysqld</command> doesn't start, check the error log to
see whether the server wrote any messages there to indicate the
cause of the problem. The error log is located in the
- <filename>C:\mysql\data</filename> directory. It is the file with a
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename> directory. It is the file with a
suffix of <filename>.err</filename>. You can also try to start the
server as <command>mysqld --console</command>; in this case, you may
get some useful information on the screen that may help solve the
@@ -4418,8 +4296,7 @@
<para>
Use <command>mysqld --verbose --help</command> to display all the
- options that <command>mysqld</command> understands. (Prior to MySQL
- 4.1, omit the <literal>--verbose</literal> option.)
+ options that <command>mysqld</command> understands.
</para>
</section>
@@ -4430,23 +4307,21 @@
<para>
On the NT family (Windows NT, 2000, XP, 2003), the recommended way
- to run MySQL is to install it as a Windows service. With the MySQL
- server installed as a service, Windows starts and stops it server
- automatically when Windows starts and stops. A MySQL server
- installed as a service can also be controlled from the command line
- using <command>NET</command> commands, or with the graphical
- <literal>Services</literal> utility.
+ to run MySQL is to install it as a Windows service, whereby MySQL
+ starts and stops automatically when Windows starts and stops. A
+ MySQL server installed as a service can also be controlled from the
+ command line using <command>NET</command> commands, or with the
+ graphical <command>Services</command> utility.
</para>
<para>
- The <literal>Services</literal> utility (the Windows
- <literal>Service Control Manager</literal>) can be found in the
- Windows <literal>Control Panel</literal> (under
- <literal>Administrative Tools</literal> on Windows 2000, XP, and
- Server 2003). It is advisable to close the
- <literal>Services</literal> utility while performing server
- installation or removal operations from this command line. This
- prevents some odd errors.
+ The <command>Services</command> utility (the Windows
+ <command>Service Control Manager</command>) can be found in the
+ Windows Control Panel (under <guimenuitem>Administrative
+ Tools</guimenuitem> on Windows 2000, XP, and Server 2003). It is
+ advisable to close the <command>Services</command> utility while
+ performing server installation or removal operations from the
+ command line. This prevents a number of errors.
</para>
<para>
@@ -4455,13 +4330,19 @@
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqladmin -u root shutdown
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin -u root shutdown
</programlisting>
+ <para><emphasis role="bold">Note</emphasis>: If the MySQL
+ <literal>root</literal> user account has a password, then you need
+ to invoke this command as <command>C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin -u root
+ -p shutdown</command> and supply the password when prompted.
+ </para>
+
<para>
This invokes the MySQL administrative utility
- <command>mysqladmin</command> to connect to the server and tell it
- to shut down. The command connects as the MySQL
+ <command>mysqladmin</command>, which connects to the server and
+ tells it to shut down. The command connects as the MySQL
<literal>root</literal> user, which is the default administrative
account in the MySQL grant system. Note that users in the MySQL
grant system are wholly independent from any login users under
@@ -4483,16 +4364,76 @@
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqld --install
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --install
</programlisting>
-<!-- I commented this out because no instructions were given how to "fix" -->
-
-<!-- the path. - PD -->
-
-<!-- If that doesn't work, you can get @command{mysqld} to -->
-
-<!-- start properly by fixing the path in the registry! -->
+<!--
+ I commented this out because no instructions were given how to
+ "fix" the path. - PD
+-->
+
+ <para>
+ You can also add the path to the mysql <filename>bin</filename>
+ directory to your Windows system <literal>PATH</literal>
+ environment variable:
+ <itemizedlist>
+
+ <listitem><para>
+ On the Windows desktop, right-click on the <guiicon>My
+ Computer</guiicon> icon, and select
+ <guimenuitem>Properties</guimenuitem>
+ </para></listitem>
+
+ <listitem><para>
+ Next select, the <guimenuitem>Advanced</guimenuitem> tab
+ from the <guimenu>System Properties</guimenu> menu that
+ appears, and click the <guibutton>Environment
+ Variables</guibutton> button.
+ </para></listitem>
+
+ <listitem><para>
+ Under <guilabel>System Variables</guilabel>, select
+ <guimenuitem>Path</guimenuitem>, and then click the
+ <guibutton>Edit</guibutton> button. The <guimenu>Edit System
+ Variable</guimenu> dialogue should appear.
+ </para></listitem>
+
+ <listitem><para>
+ Place your cursor at the end of the text appearing in the
+ space marked <guilabel>Variable Value</guilabel>. (Use the
+ <keycap>End</keycap> key to ensure that your cursor is
+ positioned at the very end of the text in this space.) Then
+ enter the complete path to your MySQL
+ <filename>bin</filename> directory (for example,
+ <literal>C:\Program Files\MySQL\MySQL Server 5.0\bin</literal>), Note that there should be
+ a semicolon separating this path from any values present in
+ this field. Dismiss this dialogue, and each dialogue in
+ turn, by clicking <guibutton>OK</guibutton> until all of the
+ dialogues that were opened have been dismissed. You should
+ now be able to invoke any MySQL executable program by
+ typing its name at the DOS prompt from any directory on the
+ system, without having to supply the path. This includes the
+ servers, the <command>mysql</command> client,
+ and all MySQL command-line utilities such as
+ <command>mysqladmin</command> and
+ <command>mysqldump</command>.
+ </para></listitem>
+
+ <listitem><para>
+ Note that you should not add the MySQL
+ <filename>bin</filename> directory to your Windows
+ <literal>PATH</literal> if you are running multiple MySQL
+ servers on the same machine.
+ </para></listitem>
+
+ </itemizedlist>
+
+ <emphasis role="bold">Warning</emphasis>: You must exercise great
+ care when editing your system <literal>PATH</literal> by hand; the
+ accidentally deletion or modification of any portion of the
+ existing <literal>PATH</literal> value can leave you with a
+ malfunctioning or even unusable system.
+ </para>
<para>
The service-installation command does not start the server.
@@ -4500,9 +4441,8 @@
</para>
<para>
- Before MySQL 4.0.2, no command-line arguments can be given following
- the <literal>--install</literal> option. MySQL 4.0.2 and up offers
- limited support for additional arguments:
+ MySQL 5.0 offers limited support for additional arguments when
+ installing the service:
</para>
<itemizedlist>
@@ -4514,8 +4454,8 @@
</para></listitem>
<listitem><para>
- As of MySQL 4.0.3, if a service name is given, it can be followed
- by a single option. By convention, this should be
+ If a service name is given, it can be followed by a single option.
+ By convention, this should be
<literal>--defaults-file=<replaceable>file_name</replaceable></literal>
to specify the name of an option file from which the server should
read options when it starts.
@@ -4569,12 +4509,11 @@
</para>
<para>
- As of MySQL 4.0.17, the server also reads options from the
- <literal>[mysqld]</literal> group from the standard option files.
- This allows you to use the <literal>[mysqld]</literal> group for
- options that should be used by all MySQL services, and an option
- group with the same name as a service for use by the server
- installed with that service name.
+ The server also reads options from the <literal>[mysqld]</literal>
+ group from the standard option files. This allows you to use the
+ <literal>[mysqld]</literal> group for options that should be used
+ by all MySQL services, and an option group with the same name as a
+ service for use by the server installed with that service name.
</para></listitem>
<listitem><para>
@@ -4591,7 +4530,7 @@
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqld --install MySQL --defaults-file=C:\my-opts.cnf
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --install MySQL --defaults-file=C:\my-opts.cnf
</programlisting>
<para>
@@ -4607,24 +4546,15 @@
</para>
<para>
- You can also specify options as ``<literal>Start
- parameters</literal>'' in the Windows <literal>Services</literal>
- utility before you start the MySQL service.
- </para>
-
- <para>
- <emphasis role="bold">Note</emphasis>: Prior to MySQL 4.0.17, a
- server installed as a Windows service has problems starting if its
- pathname or the service name contains spaces. For this reason, with
- older versions, avoid installing MySQL in a directory such as
- <filename>C:\Program Files</filename> or using a service name
- containing spaces.
+ You can also specify options as Start parameters in the Windows
+ <command>Services</command> utility before you start the MySQL
+ service.
</para>
<para>
Once a MySQL server has been installed as a service, Windows starts
the service automatically whenever Windows starts. The service also
- can be started immediately from the <literal>Services</literal>
+ can be started immediately from the <command>Services</command>
utility, or by using the command <command>NET START MySQL</command>.
The <command>NET</command> command is not case sensitive.
</para>
@@ -4632,10 +4562,10 @@
<para>
When run as a service, <command>mysqld</command> has no access to a
console window, so no messages can be seen there. If
- <command>mysqld</command> doesn't start, check the error log to see
+ <command>mysqld</command> does not start, check the error log to see
whether the server wrote any messages there to indicate the cause of
the problem. The error log is located in the MySQL data directory
- (for example, <filename>C:\mysql\data</filename>). It is the file
+ (for example, <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename>). It is the file
with a suffix of <filename>.err</filename>.
</para>
@@ -4649,56 +4579,28 @@
</para>
<para>
- From MySQL 3.23.44 on, you have the choice of installing the server
- as a <literal>Manual</literal> service if you don't wish the service
- to be started automatically during the boot process. To do this, use
- the <literal>--install-manual</literal> option rather than the
+ You also have the choice of installing the server as a manual
+ service if you do not wish for the service to be started
+ automatically during the boot process. To do this, use the
+ <literal>--install-manual</literal> option rather than the
<literal>--install</literal> option:
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqld --install-manual
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --install-manual
</programlisting>
<para>
To remove a server that is installed as a service, first stop it if
- it is running. Then use the <literal>--remove</literal> option to
- remove it:
+ it is running by executing <command>NET STOP MYSQL</command>. Then
+ use the <literal>--remove</literal> option to remove it:
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqld --remove
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld --remove
</programlisting>
<para>
- For MySQL versions older than 3.23.49, one problem with automatic
- MySQL service shutdown is that Windows waited only for a few seconds
- for the shutdown to complete, then killed the database server
- process if the time limit was exceeded. This had the potential to
- cause problems. (For example, the <literal>InnoDB</literal> storage
- engine would have to perform crash recovery at the next startup.)
- Starting from MySQL 3.23.49, Windows waits longer for the MySQL
- server shutdown to complete. If you notice this still is not enough
- for your installation, it is safest not to run the MySQL server as a
- service. Instead, start it from the command-line prompt, and stop it
- with <command>mysqladmin shutdown</command>.
- </para>
-
- <para>
- This change to tell Windows to wait longer when stopping the MySQL
- server works for Windows 2000 and XP. It does not work for Windows
- NT, where Windows waits only 20 seconds for a service to shut down,
- and after that kills the service process. You can increase this
- default by opening the Registry Editor
- <filename>\winnt\system32\regedt32.exe</filename> and editing the
- value of <literal>WaitToKillServiceTimeout</literal> at
- <literal>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control</literal>
- in the Registry tree. Specify the new larger value in milliseconds.
- For example, the value 120000 tells Windows NT to wait up to 120
- seconds.
- </para>
-
- <para>
If <command>mysqld</command> is not running as a service, you can
start it from the command line. For instructions, see
<xref linkend="windows-start-command-line"/>.
@@ -4729,17 +4631,16 @@
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqlshow
-C:\> C:\mysql\bin\mysqlshow -u root mysql
-C:\> C:\mysql\bin\mysqladmin version status proc
-C:\> C:\mysql\bin\mysql test
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqlshow
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqlshow -u root mysql
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin version status proc
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysql test
</programlisting>
<para>
If <command>mysqld</command> is slow to respond to TCP/IP
- connections from client programs on Windows 9x/Me, there is probably
- a problem with your DNS. In this case, start
- <command>mysqld</command> with the
+ connections from client programs, there is probably a problem with
+ your DNS. In this case, start <command>mysqld</command> with the
<literal>--skip-name-resolve</literal> option and use only
<literal>localhost</literal> and IP numbers in the
<literal>Host</literal> column of the MySQL grant tables.
@@ -4747,79 +4648,12 @@
<para>
You can force a MySQL client to use a named pipe connection rather
- than TCP/IP by specifying the <literal>--pipe</literal> option or by
- specifying <literal>.</literal> (period) as the host name. Use the
+ than TCP/IP by specifying the <literal>--pipe</literal> or
+ <literal>--protocol=PIPE</literal> option, or by specifying
+ <literal>.</literal> (period) as the host name. Use the
<literal>--socket</literal> option to specify the name of the pipe.
- As of MySQL 4.1, you can use the <literal>--protocol=PIPE</literal>
- option instead.
</para>
- <para>
- There are two versions of the MySQL command-line tool on Windows:
- </para>
-
- <informaltable>
- <tgroup cols="2">
- <colspec colwidth="15*"/>
- <colspec colwidth="85*"/>
- <tbody>
- <row>
- <entry>
- <emphasis role="bold">Binary</emphasis>
- </entry>
- <entry>
- <emphasis role="bold">Description</emphasis>
- </entry>
- </row>
- <row>
- <entry>
- <command>mysql</command>
- </entry>
- <entry>
- Compiled on native Windows, offering limited text editing
- capabilities.
- </entry>
- </row>
- <row>
- <entry>
- <command>mysqlc</command>
- </entry>
- <entry>
- Compiled with the Cygnus GNU compiler and libraries, which
- offers <literal>readline</literal> editing.
- <command>mysqlc</command> was intended for use primarily
- with Windows 9x/Me. It does not support the updated
- authentication protocol used beginning with MySQL 4.1, and
- is not supported in MySQL 4.1 and above. Beginning with
- MySQL 4.1.8, it is no longer included in MySQL Windows
- distributions.
- </entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
-<!-- TODO: Remove or rewrite all references to mysqlc.exe after a -->
-
-<!-- suitable period of time has elapsed. Suggestion: Move this info to a -->
-
-<!-- separate 'legacy' page? -->
-
- <para>
- To use <command>mysqlc</command>, you must have a copy of the
- <filename>cygwinb19.dll</filename> library installed somewhere that
- <command>mysqlc</command> can find it. If your distribution does not
- have the <literal>cygwinb19.dll</literal> library in the
- <filename>bin</filename> directory under the base directory of your
- MySQL installation, look for it in the <literal>lib</literal>
- directory and copy it to your Windows system directory
- (<filename>\Windows\system</filename> or a similar place).
- </para>
-
-<!-- TODO: check whether it needs to be in the *system* directory, or if -->
-
-<!-- it can be in the Windows directory. -->
-
</section>
<section id="windows-troubleshooting">
@@ -4839,7 +4673,7 @@
relevant to the error that is preventing the server from starting.
The error log is located in the data directory specified in your
<filename>my.ini</filename> file. The default data directory
- location is <filename>C:\mysql\data</filename>. See
+ location is <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename>. See
<xref linkend="error-log"/>.
</para>
@@ -4871,7 +4705,8 @@
files. This error is often encountered when the MySQL base or data
directories are installed in different locations than the default
locations (<filename>C:\mysql</filename> and
- <filename>C:\mysql\data</filename>, respectively).
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename>,
+ respectively).
</para>
<para>
@@ -4884,11 +4719,11 @@
<para>
If you have installed MySQL to a directory other than
- <filename>C:\mysql</filename> you need to ensure that the MySQL
- server is aware of this through the use of a configuration
- (<literal>my.ini</literal>) file. The <literal>my.ini</literal>
- file needs to be located in your Windows directory, typically
- located at <filename>C:\WinNT</filename> or
+ <filename>C:\Program Files\MySQL\MySQL Server 5.0</filename> you
+ need to ensure that the MySQL server is aware of this through the
+ use of a configuration (<filename>my.ini</filename>) file. The
+ <filename>my.ini</filename> file needs to be located in your
+ Windows directory, typically <filename>C:\WINNT</filename> or
<filename>C:\WINDOWS</filename>. You can determine its exact
location from the value of the <literal>WINDIR</literal>
environment variable by issuing the following command from the
@@ -4901,8 +4736,8 @@
<para>
An option file can be created and modified with any text editor,
- such as the Notepad program. For example, if MySQL is installed at
- <filename>E:\mysql</filename> and the data directory is located at
+ such as Notepad. For example, if MySQL is installed in
+ <filename>E:\mysql</filename> and the data directory is
<filename>D:\MySQLdata</filename>, you can create the option file
and set up a <literal>[mysqld]</literal> section to specify values
for the basedir and datadir parameters:
@@ -4918,14 +4753,14 @@
<para>
Note that Windows pathnames are specified in option files using
- forward slashes rather than backslashes. If you do use backslashes,
- you must double them:
+ (forward) slashes rather than backslashes. If you do use
+ backslashes, you must double them:
</para>
<programlisting>
[mysqld]
# set basedir to your installation path
-basedir=C:\\Program Files\\mysql
+basedir=C:\\Program Files\\MySQL\\MySQL Server 5.0
# set datadir to the location of your data directory
datadir=D:\\MySQLdata
</programlisting>
@@ -4992,7 +4827,7 @@
<listitem><para>
Download the latest Windows distribution of MySQL from
- <ulink url="http://dev.mysql.com"/>.
+ <ulink url="http://dev.mysql.com/downloads"/>.
</para></listitem>
<listitem><para>
@@ -5004,7 +4839,7 @@
following command from the command prompt:
<programlisting>
-C:\> NET STOP MySQL
+C:\> NET STOP MYSQL
</programlisting>
</para>
@@ -5014,11 +4849,11 @@
</para>
<programlisting>
-C:\> C:\mysql\bin\mysqladmin -u root shutdown
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqladmin -u root shutdown
</programlisting></listitem>
<listitem><para>
- When upgrading to MySQL 4.1.5 or higher from a previous version, or
+ When upgrading to MySQL 5.0 from a version previous to 4.1.5, or
when upgrading from a version of MySQL installed from a Zip archive
to a version of MySQL installed with the MySQL Installation Wizard,
you must manually remove the previous installation and MySQL
@@ -5093,7 +4928,7 @@
</para>
<itemizedlist>
-
+<!-- TODO: See if we can drop the Win95 material. -->
<listitem><para>
<emphasis role="bold">Windows 95 and threads</emphasis>
</para>
@@ -5134,17 +4969,17 @@
<para>
MySQL depends on the <literal>pread()</literal> and
- <literal>pwrite()</literal> calls to be able to mix
+ <literal>pwrite()</literal> system calls to be able to mix
<literal>INSERT</literal> and <literal>SELECT</literal>. Currently
we use mutexes to emulate
- <literal>pread()</literal>/<literal>pwrite()</literal>. We will, in
- the long run, replace the file level interface with a virtual
- interface so that we can use the
+ <literal>pread()</literal> and <literal>pwrite()</literal>. We
+ intend to replace the file level interface with a virtual
+ interface in the future so that we can use the
<literal>readfile()</literal>/<literal>writefile()</literal>
interface on NT, 2000, and XP to get more speed. The current
- implementation limits the number of open files MySQL can use to
- 2,048 (1,024 before MySQL 4.0.19), which means that you cannot run
- as many concurrent threads on NT, 2000, XP, and 2003 as on Unix.
+ implementation limits the number of open files MySQL 5.0 can use to
+ 2,048, which means that you cannot run as many concurrent threads
+ on Windows NT, 2000, XP, and 2003 as on Unix.
</para></listitem>
<listitem><para>
@@ -5165,7 +5000,7 @@
</para></listitem>
<listitem><para>
- If a connection hangs, it's impossible to break it without
+ If a connection hangs, it is not possible to break it without
killing MySQL.
</para></listitem>
@@ -5175,7 +5010,7 @@
</para></listitem>
<listitem><para>
- <command>mysqladmin shutdown</command> can't abort as long as
+ <command>mysqladmin shutdown</command> cannot abort as long as
there are sleeping connections.
</para></listitem>
@@ -5183,8 +5018,7 @@
</para>
<para>
- We plan to fix this problem when our Windows developers have
- figured out a nice workaround.
+ We plan to fix this problem in the future.
</para></listitem>
<listitem><para>
@@ -5202,17 +5036,17 @@
<listitem><para>
<emphasis role="bold"><literal>DROP TABLE</literal></emphasis>
</para>
-
+<!-- TODO: We have views now, so is this fixed? -->
<para>
<literal>DROP TABLE</literal> on a table that is in use by a
<literal>MERGE</literal> table does not work on Windows because the
<literal>MERGE</literal> handler does the table mapping hidden from
- the upper layer of MySQL. Because Windows doesn't allow you to drop
+ the upper layer of MySQL. Because Windows does not allow dropping
files that are open, you first must flush all
<literal>MERGE</literal> tables (with <literal>FLUSH
TABLES</literal>) or drop the <literal>MERGE</literal> table before
- dropping the table. We will fix this at the same time we introduce
- views.
+ dropping the table.
+ <!-- We will fix this at the same time that we introduce views. -->
</para></listitem>
<listitem><para>
@@ -5240,7 +5074,7 @@
<emphasis role="bold">Killing MySQL from the Task
Manager</emphasis>
</para>
-
+<!-- TODO: Drop Win95 stuff? -->
<para>
You cannot kill MySQL from the Task Manager or with the shutdown
utility in Windows 95. You must stop it with <command>mysqladmin
@@ -5329,79 +5163,37 @@
<para>
The latter command also can be used to reliably read in any SQL
file that may contain binary data.
- </para>
-
- <para>
-<!-- Mike Hillyer - This is getting a little old, commenting out. -->
- </para>
-
- <para>
-<!-- @item @code{Can't open named pipe} error -->
- </para>
-
- <para>
-<!-- If you use a MySQL 3.22 server on Windows NT with the newest MySQL client -->
- </para>
-
- <para>
-<!-- programs, you get the following error: -->
- </para>
-
- <para>
-<!-- @example -->
- </para>
-
- <para>
-<!-- error 2017: can't open named pipe to host: . pipe... -->
- </para>
-
- <para>
-<!-- @end example -->
- </para>
-
- <para>
-<!-- @tindex .my.cnf file -->
- </para>
-
- <para>
-<!-- This happens because the release version of MySQL uses named pipes on NT -->
- </para>
-
- <para>
-<!-- by default. You can avoid this error by using the @code{-host=localhost} -->
- </para>
-
- <para>
-<!-- option to the new MySQL clients or by creating an option file -->
- </para>
-
- <para>
-<!-- @file{C:\my.cnf} that contains the following information: -->
- </para>
-
- <para>
-<!-- @example -->
- </para>
-
- <para>
-<!-- [client] -->
- </para>
-
- <para>
-<!-- host = localhost -->
- </para>
-
- <para>
-<!-- @end example -->
- </para>
-
- <para>
-<!-- Starting from 3.23.50, named pipes are enabled only if @command{mysqld-nt} or -->
- </para>
+ </para></listitem>
- <para>
-<!-- @command{mysqld-max-nt} is started with @code{-enable-named-pipe}. -->
- </para></listitem>
+<!--
+ Mike Hillyer - This is getting a little old, commenting out.
+
+ @item @code{Can't open named pipe} error
+ If you use a MySQL 3.22 server on Windows NT with the newest
+ MySQL client programs, you get the following error:
+
+ @example
+ error 2017: can't open named pipe to host: . pipe...
+ @end example
+
+ @tindex .my.cnf file
+
+
+ This happens because the release version of MySQL uses named pipes
+ on NT by default. You can avoid this error by using the
+ @code{-host=localhost} option to the new MySQL clients or by
+ creating an option file @file{C:\my.cnf} that contains the
+ following information:
+
+ @example
+ [client]
+ host = localhost
+ @end example
+
+ Starting from 3.23.50, named pipes are enabled only if
+ @command{mysqld-nt} or @command{mysqld-max-nt} is started with
+ @code{-enable-named-pipe}.
+-->
<listitem><para>
<emphasis role="bold"><literal>Access denied for user</literal>
@@ -5430,9 +5222,11 @@
</itemizedlist>
-<!-- MH - Does this to-do list even still have relevance? I would think we would -->
-
-<!-- now Task internal developers rather than ask the world for help. -->
+<!--
+ MH - Does this to-do list even still have relevance? I would think
+ we would now Task internal developers rather than ask the world
+ for help.
+-->
<para>
Here are some open issues for anyone who might want to help us
@@ -5446,18 +5240,6 @@
<itemizedlist>
-<!-- PD: Commented this one out as obsolete until I hear otherwise -->
-
-<!-- @item -->
-
-<!-- Make a single-user @code{MYSQL.DLL} server. This should include everything in -->
-
-<!-- a standard MySQL server, except thread creation. This makes -->
-
-<!-- MySQL much easier to use in applications that don't need a true -->
-
-<!-- client/server and don't need to access the server from other hosts. -->
-
<listitem><para>
Add macros to use the faster thread-safe increment/decrement
methods provided by Windows.
@@ -5486,6 +5268,8 @@
<secondary>Linux RPM packages</secondary>
</indexterm>
+<!-- TODO: We're not really still building on SuSE 7.3, are we? /JS -->
+
<para>
The recommended way to install MySQL on Linux is by using the RPM
packages. The MySQL RPMs are currently built on a SuSE Linux 7.3
@@ -5528,18 +5312,21 @@
<literal>MySQL-server</literal> RPM. See
<xref linkend="mysqld-max"/>.
</para>
-
+<!-- TODO: Probably also dated. /JS -->
<para>
- If you get a dependency failure when trying to install the MySQL 4.0
- packages (for example, ``<literal>error: removing these packages
+ If you get a dependency failure when trying to install MySQL packages
+ (for example, <quote><literal>error: removing these packages
would break dependencies: libmysqlclient.so.10 is needed by
- ...</literal>''), you should also install the package
+ ...</literal></quote>), you should also install the package
<literal>MySQL-shared-compat</literal>, which includes both the
shared libraries for backward compatibility
(<literal>libmysqlclient.so.12</literal> for MySQL 4.0 and
<literal>libmysqlclient.so.10</literal> for MySQL 3.23).
</para>
-
+<!--
+ TODO: Check currency of this info. I'd say that even Debian is
+ shipping 4.0 by now. /JS
+-->
<para>
Many Linux distributions still ship with MySQL 3.23 and they usually
link applications dynamically to save disk space. If these shared
@@ -5554,6 +5341,11 @@
instead.
</para>
+<!--
+ TODO: The RPMs section probably needs a rewrite. Check the rest
+ of the RefMan, and with the developers. /JS
+-->
+
<para>
The following RPM packages are available:
</para>
@@ -5759,11 +5551,11 @@
</indexterm>
<para>
- Beginning with MySQL 4.0.11, you can install MySQL on Mac OS X 10.2.x
- (``Jaguar'') and up using a Mac OS X binary package in PKG format
- instead of the binary tarball distribution. Please note that older
- versions of Mac OS X (for example, 10.1.x) are not supported by this
- package.
+ You can install MySQL on Mac OS X 10.2.x (<quote>Jaguar</quote>) and
+ up using a Mac OS X binary package in PKG format instead of the
+ binary tarball distribution. Please note that older versions of Mac
+ OS X (for example, 10.1.x) are <emphasis role="bold">not</emphasis>
+ supported by this package.
</para>
<para>
@@ -10513,7 +10305,7 @@
<para>
If the server fails to start up correctly, check the error log file
to see if you can find out why. Log files are located in the data
- directory (typically <filename>C:\mysql\data</filename> on Windows,
+ directory (typically <filename>C:\Program Files\MySQL\MySQL Server 5.0\data</filename> on Windows,
<filename>/usr/local/mysql/data</filename> for a Unix binary
distribution, and <filename>/usr/local/var</filename> for a Unix
source distribution). Look in the data directory for files with
@@ -11552,12 +11344,12 @@
distributions include a
<filename>mysql_fix_privilege_tables.sql</filename> SQL script that
you can run using the <command>mysql</command> client. If your MySQL
- installation is located at <filename>C:\mysql</filename>, the
+ installation is located at <filename>C:\Program Files\MySQL\MySQL Server 5.0</filename>, the
commands look like this:
</para>
<programlisting>
-C:\> C:\mysql\bin\mysql -u root -p mysql
+C:\> C:\Program Files\MySQL\MySQL Server 5.0\bin\mysql -u root -p mysql
mysql> SOURCE C:/mysql/scripts/mysql_fix_privilege_tables.sql
</programlisting>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (jon:1.3034) | jon | 15 Jul |
