Installation MySQL Workbench Manual In Linux

 System Requirements

MySQL Workbench is available on a number of operating systems and platforms. For information about those platforms that are officially supported, see http://www.mysql.com/support/supportedplatforms/workbench.htmlon the MySQL website.

General Requirements

General requirements and considerations that apply to all operating systems.

• MySQL server: Although it is not required, MySQL Workbench is designed to have either a remote or local MySQL server connection. For additional information about connecting to a MySQL server, see Chapter 5, Connections in MySQL Workbench. For additional information about installing a MySQL server, see Installing and Upgrading MySQL..

Data modeling does not require a MySQL server connection.

Some features take advantage of MySQL server features, and as such, they require more recent versions of MySQL Server. For example, the Performance Dashboard requires MySQL Server 5.6 or higher.

• Simultaneous client connections: Opening a MySQL connection from the MySQL Workbench home page opens a new connection tab in MySQL Workbench for that connection. Each of these tabs requires two MySQL connections to perform basic tasks, such schema discovery and SQL execution. Additionally, performing management related tasks, such as Server Status, requires two additional MySQL connections. Essentially, this means that each MySQL connection tab in MySQL Workbench requires four available connections to MySQL. For additional information about "Too many connection" related errors, see Too many connections.
  This connection requirement doubles with each connection tab opened in MySQL Workbench, even if the two connection tabs point to the same MySQL server. SQL editor tabs share their connections, so having multiple SQL editor and SQL results tabs does not affect the number of required connections.

Note

On startup, the application checks the OpenGL version and chooses between software and hardware rendering. To determine which rendering method is being used, open the Helpmenu and choose the System Info item.

Requirements for Linux

• The requirements for Linux are embedded within their respective packages. Use the platform specific tool (for example, yum or apt) to install the package and their dependencies.
• The "Save password in keychain" functionality requires gnome-keyring to store the passwords. Note that on KDE systems, the gnome-keyring daemon is not started by default.
• For Linux and macOS, the MySQL server administration features require sudo privileges to execute several commands. The sudo user must be capable of executing the following system commands:

  /usr/bin/sudo
  /usr/bin/nohup
  /usr/bin/uptime
  /usr/bin/which
  /usr/bin/stat
  
  /bin/bash
  /bin/mkdir
  /bin/rm
  /bin/rmdir
  /bin/dd
  /bin/cp
  /bin/ls

  Additionally, the sudo user must keep the HOME environment variable when executing system commands, which means adding the following to /etc/sudoers:

  env_keep +="HOME"

  For MySQL Workbench to execute MySQL Enterprise Backup commands, the sudo user must also be able to execute the MySQL Enterprise Backup binary.

Requirements for Windows

• Microsoft .NET Framework 4.5
• Microsoft Visual C++ 2015 Redistributable Package
  Note

  The 2013 version was changed to 2015 with MySQL Workbench 6.3.9.
• Windows 7 and above
  Note

  MySQL Workbench 6.1 supports earlier versions of Windows, including Vista.

• Command-Line Options

In addition to platform-specific command-line options, MySQL Workbench has the following command-line options:

Note

On Microsoft Windows, the command-line options contain one leading dash instead of two. For example, use -log-level for Microsoft Windows and --log-level for Linux and macOS.

• --log-level level: Controls the verbosity level for logging output from Workbench.
  With increasingly levels of verbosity, the valid values for level are: error, warning, info, debug1, debug2, and debug3.
  The location of the generated log files, such as wb.log, are as follows:
  Table 2.1 Default location of generated MySQL Workbench log files

  Platform	Default location
  Linux	~/.mysql/workbench/log/
  macOS	~/Library/Application Support/Workbench/log/
  Microsoft Windows	C:\Users\user_nameAppData\Roaming\MySQL\Workbench\log\

• --admin instance: Open an administration tab to the named MySQL instance.
• --upgrade-mysql-dbs: Open the Migration Wizard tab.
• --migration: Open the Migration Wizard tab.
• --log-to-stderr: Also log to stderr.
• --version: Show MySQL Workbench version number and exit.
• --verbose, -v: Enable diagnostics output.
• --query [connection|connection_string]:
  • Empty: Open a query tab and prompts for a connection.
  • Connection: Open a named connection.
  • Connection_string: Create a connection based on the entered connection string, which should be in the form $USER@$HOST:$PORT.
• --model modelfile: open the given EER model file.
• --script script: Open the given SQL file in a connection, typically used with the --query parameter.
• --run code: Execute the given code using the default language for GRT shell.
• --run-python script: Execute the given code in Python.
• --run-script file: Execute Python code from a file.
• --open file: Open the given file at startup. Deprecated, so instead use specific types such as --script or --model.
• --quit-when-done: Quits MySQL Workbench after --script or --run finishes.