Setting up MySQL Control Center



  1. If you have access to AFS (at DESY or elsewhere), you can find a preinstalled copy of MySQL Control Center at /afs/desy.de/group/it/ilcsoft/mysqlcc/0.9.4 (accessible by any user).

  2. Otherwise, you may download MySQL Control Center from the MySQL product archives or try to find a copy with the help of Google. The latest and last version is 0.9.4, still called a beta release. You’ll probably get a gzipped tar file. Unpack it anywhere you like – you’ll need about 9 MB of disk space. The archive contains the excutable file called mysqlcc, the usual accompanying text files (such as readme, history, todo, and license), a collection of MySQL commands in a file called syntax.txt (used for syntax highlighting), some WAV sound files (warning and error notifications), and a subdirectory with translations of the user interface into several other languages. However, only the executable itself is indispensable to run MySQL Control Center.

  3. Start mysqlcc. After a second, you should see the main window and a configuration dialogue window which has already popped up automatically. You have to fill in the correct settings to connect to a MySQL server:

    1. The field “Name” may contain an arbitrary identifier for this connection.

    2. The field “Host Name“ has to contain the name of a MySQL server. This can either be localhost if you have a local MySQL database running on your computer, or the name or IP of any computer running a MySQL server, for example pollin1.in2p3.fr. If you choose localhost, the MySQL server daemon on your computer will be accessed via a socket file. In every other case, you will be connected via TCP/IP.

    3. The fields “User Name” and “Password” should contain a valid MySQL user/password pair for the selected server. On MySQL servers used for Mokka, one user is typically consult with the password consult. On your local computer, you may also want to have access as the MySQL root user. To do so, you can set up further connections later (not only to different servers, but also with different access rights).

    4. If you selected localhost as the MySQL server, you have to enter the location of the socket file which provides the access to your local MySQL server daemon into the field “Socket File”. You should find the socket in /tmp with a name like mysql-4.1.16.sock, typically (but not necessarily) reflecting the MySQL version you are currently running.

    5. The rest of the options should be rather self-explanatory. If you check “Prompt for Password”, you’ll have to enter the password for the selected user everytime you try to open the connection. However, this should only be useful if you want to connect as a MySQL user with high privileges, such as root.

    6. The whole setup dialogue consists of three more tabs. These tabs contain special settings which you usually should not have to change.

  4. After you have filled out all needed fields, you may click “Check” in order to test whether a connection can be established successfully with the given settings. If everything is okay, click “Add” and the dialogue window will be closed. Select “File > New” from the menubar to configure another connection with different settings, if desired.

  5. The connection which you just set up should appear in the list of “MySQL Servers” on the left side of the main window. (Otherwise, select “View > Show Tree” from the menubar.) Double-click on a list item to open the corresponding connection. Expand the “Databases” item to see a list of all available databases – further clicking will show you the tables and finally their data contents. Use the mouse (left and right button) and the menubar to perform any MySQL-related action.


This page is valid XHTML — Last change: 2007-03-31 by Adrian Vogel <adrian.vogel@desy.de>