The following table shows the available servers for Windows in MySQL 5.1.20 and earlier.
Table 1.7. mysqld binary types for Microsoft Windows up to MySQL 5.1.20
|mysqld-nt||Optimized binary with named-pipe support|
|mysqld||Optimized binary without named-pipe support|
|mysqld-debug||Like mysqld-nt, but compiled with full debugging and automatic memory allocation checking|
The following table shows the available servers for Windows in MySQL 5.1.21 and later.
Table 1.8. mysqld binary types for Microsoft Windows MySQL 5.1.21 and later
|mysqld||Optimized binary with named-pipe support|
|mysqld-debug||Like mysqld, but compiled with full debugging and automatic memory allocation checking|
All of the preceding binaries are optimized for modern Intel processors, but should work on any Intel i386-class or higher processor.
Each of the servers in a distribution support the same set of
storage engines. The
statement displays which engines a given server supports.
All Windows MySQL 5.1 servers have support for symbolic linking of database directories.
MySQL supports TCP/IP on all Windows platforms. MySQL servers on Windows support named pipes as indicated in the following list. However, the default is to use TCP/IP regardless of platform. (Named pipes are slower than TCP/IP in many Windows configurations.)
Use of named pipes is subject to these conditions:
Named pipes are enabled only if you start the server with
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.
For MySQL 5.1.20 and earlier, named-pipe connections are permitted only by the mysqld-nt and mysqld-debug servers. For MySQL 5.1.21 and later, the mysqld and mysqld-debug servers both contain support for named-pipe connections.
Most of the examples in this manual use mysqld as the server name. If you choose to use a different server, such as mysqld-nt or mysqld-debug, make the appropriate substitutions in the commands that are shown in the examples.