Chapter 2 Starting the Server for the First Time on Windows
This section gives a general overview of starting the MySQL server. The follow sections provide more specific information for starting the MySQL server from the control trace or as a Windows military service. The information here applies chiefly if you installed MySQL using the
noinstall version, or if you wish to configure and test MySQL manually preferably than with the MySQL Installer. The examples in these sections assume that MySQL is installed under the default option location of
C:\Program. Adjust the path names shown in the examples if you have MySQL installed in a different localization. Clients have two options. They can use TCP/IP, or they can use a named pipe if the server supports named-pipe connections.
Files\MySQL\MySQL Server 8.0
MySQL for Windows besides supports shared-memory connections if the waiter is started with the
shared_memory system variable enabled. Clients can connect through shared memory by using the
--protocol=MEMORY option. For information about which server binary to run, see Selecting a MySQL Server Type. Testing is best done from a command prompt in a console window ( or “ DOS window ” ). In this way you can have the server display condition 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 .
The database must be initialized before MySQL can be started. For extra information about the low-level formatting process, see Initializing the Data Directory.
To start the server, accede this command :
C:\> "C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqld" --console
For a server that includes
InnoDB support, you should see the messages similar to those following as it starts ( the way names and sizes may differ ) :
InnoDB: The first specified datafile c:\ibdata\ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file c:\ibdata\ibdata1 size to 209715200 InnoDB: Database physically writes the file full: wait... InnoDB: Log file c:\iblogs\ib_logfile0 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile0 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile1 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile1 size to 31457280 InnoDB: Log file c:\iblogs\ib_logfile2 did not exist: new to be created InnoDB: Setting log file c:\iblogs\ib_logfile2 size to 31457280 InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: creating foreign key constraint system tables InnoDB: foreign key constraint system tables created 011024 10:58:25 InnoDB: Started
When the server finishes its startup succession, you should see something like this, which indicates that the server is ready to service node connections :
mysqld: ready for connections Version: '8.0.28' socket: '' port: 3306
The server continues to write to the console any farther diagnostic output it produces. You can open a new console window in which to run client programs.
Read more: Best Free Karaoke Software for Windows
If you omit the
--console choice, the server writes diagnostic output to the erroneousness log in the data directory (
C:\Program Files\MySQL\MySQL Server by default ). The error log is the file with the
.err extension, and may be set using the
--log-error choice .
root account in the MySQL allow tables has no password. After starting the waiter, you should set up a password for it using the instructions in Securing the Initial MySQL Account .