(gs):Connect with MySQL Workbench

  • This page was last modified on February 24, 2011, at 10:11.
The (mt) Community Wiki is a collaborative project. Any (mt) Media Temple customer or employee may contribute. Not all articles and/or content have been tested for accuracy by (mt) Media Temple.

For officially moderated and tested articles, be sure to visit our KnowledgeBase.

From (mt) Community Wiki

Contents

Overview

MySQL Workbench is a cross-platform, visual database design tool developed by MySQL. It is the highly anticipated successor application of the DBDesigner4 project. MySQL Workbench is available as a native GUI tool on Windows, Linux and OS X in different editions.

Results

After following this article, you will be able to connect to MySQL Workbench.

Requirements

  • Download and install MySQL Workbench for your operating system.
  • You have added the IP address of your location to your Currently Allowed IPs list in your AccountCenter.
  • host: external-db.s00000.gridserver.com
  • username: db00000
  • password: Your password.
  • database: db00000_db

If you are unfamiliar with any of the above, please read the following articles before proceeding with this article:

Instructions

Let's begin!

1. Open MySQL Workbench.

2. If this is the first connection you are adding to MySQL Workbench, click on New Connection. See Figure 1 for the location.

Figure 1: New Connection will open a new screen.

3. In the new window, enter your MySQL login credentials. See Figure 2 as an example.

Figure 2: Click on "Test Connection" to verify your settings.

That's it! You are now connected to your MySQL for your (gs) Grid-Service.

NOTE: Media Temple may have customized the MySQL installation in such a way that a couple scripts or commands are not found where the Workbench templates expect them to be. For instance, you may get an error stating that the start script could not be found. Since the MySQL server is shared among several users, it is appropriate that Workbench is unable to start and stop the server. If you don't need to manage the sever running status then simply ignore the error about the start/stop scripts. If you need that however then you have to contact someone at Media Temple who can tell you where these scripts are installed or what else would be appropriate instead if they don't exist.


Notes/Supplemental