(mysql.info.gz) Windows select server

Info Catalog

(mysql.info.gz) Windows create option file

(mysql.info.gz) Windows installation

(mysql.info.gz) Windows server first start

 
 2.3.9 Selecting a MySQL Server type
 -----------------------------------
 
 Starting with MySQL 3.23.38, the Windows distribution includes both the
 normal and the MySQL-Max server binaries.
 
 Up through the early releases of MySQL 4.1, the servers included in
 Windows distributions are named like this:
 
 *Binary*       *Description*
 `mysqld'       Compiled with full debugging and automatic memory
                allocation checking, symbolic links, and `InnoDB' and
                `BDB' tables.
 `mysqld-opt'   Optimized binary.  From version 4.0 on, `InnoDB' is
                enabled.  Before 4.0, this server includes no
                transactional table support.
 `mysqld-nt'    Optimized binary for Windows NT, 2000, and XP with
                support for named pipes.
 `mysqld-max'   Optimized binary with support for symbolic links, and
                `InnoDB' and `BDB' tables.
 `mysqld-max-nt'Like `mysqld-max', but compiled with support for named
                pipes.
 
 We have found that the server with the most generic name (`mysqld') 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
 `mysqld-opt' 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 `-max' servers or named pipe support offered by the
 `-nt' servers.
 
 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:
 `mysqld' has been renamed to `mysqld-debug' and `mysqld-opt' has been
 renamed to `mysqld'.  Thus, the server that includes debugging support
 indicates that in its name, and the server named `mysqld' is an
 efficient default choice. The other servers still have their same
 names. The resulting servers are named like this:
 
 *Binary*       *Description*
 `mysqld-debug' Compiled with full debugging and automatic memory
                allocation checking, symbolic links, and `InnoDB' and
                `BDB' tables.
 `mysqld'       Optimized binary with `InnoDB' support.
 `mysqld-nt'    Optimized binary for Windows NT, 2000, and XP with
                support for named pipes.
 `mysqld-max'   Optimized binary with support for symbolic links, and
                `InnoDB' and `BDB' tables.
 `mysqld-max-nt'Like `mysqld-max', but compiled with support for named
                pipes.
 
 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
 `mysqld-debug' but not one named `mysqld'. In this case, you should
 have a server `mysqld-opt', which you should choose as your default
 server unless you need maximal features, named pipes, or debugging
 support.
 
 All of the preceding binaries are optimized for modern Intel processors,
 but should work on any Intel i386-class or higher processor.
 
 MySQL supports TCP/IP on all Windows platforms. The `mysqld-nt' and
 `mysql-max-nt' 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.)
 Named pipe use is subject to these conditions:
 
    * Starting from MySQL 3.23.50, named pipes are enabled only if you
      start the server with the `--enable-named-pipe' 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 pipe connections are allowed only by the `mysqld-nt' or
      `mysqld-max-nt' servers, and only if the server is run on a version
      of Windows that supports named pipes (NT, 2000, XP, 2003).
 
    * These servers can be run on Windows 98 or Me, but only if TCP/IP
      is installed; named pipe connections cannot be used.
 
    * These servers can not be run on Windows 95.
 
 
 * Most of the examples in reference manual use `mysqld' as the
 server name. If you choose to use a different server, such as
 `mysqld-nt', make the appropriate substitutions in the commands that
 are shown in the examples.
 

Info Catalog

(mysql.info.gz) Windows create option file

(mysql.info.gz) Windows installation

(mysql.info.gz) Windows server first start