MySQL Workbench is a graphical client for working with MySQL databases; it is not the database server itself. To follow this tutorial, first make sure a MySQL Server instance is installed, running, and reachable. Then create and test a connection in Workbench, open the SQL editor, and run a simple read-only query.
This walkthrough follows the Oracle MySQL Workbench Manual, whose documented scope is Workbench 8.0 through 8.0.47. The manual says Workbench is developed and tested with MySQL Server 8.0; it may connect to Server 8.4 and later, but some features may not work with those versions.
What MySQL Workbench does—and what it does not do
Think of MySQL Workbench as a desktop control panel for a MySQL Server. Workbench provides a graphical place to connect to a server, write and run SQL, inspect data, administer server features, design database models, and work with migrations. The server is a separate program that stores and serves the databases. Installing Workbench alone does not create a live database or start a server.
A connection is a saved set of details Workbench uses to reach a particular server. You might save more than one connection if, for example, you use a local development server and a separate server supplied by a class or workplace. Each connection points to a server endpoint and may use different credentials or connection settings.
#1 Best Overall
Choose an edition and check compatibility
The MySQL Workbench Community Edition is free, and the manual lists downloads for Windows, macOS, and Linux. Commercial Edition adds enterprise features; a beginner following the connection, query, and basic modeling steps here does not need to buy it simply to use those core workflows.
Check the version caveat before relying on advanced features: the Oracle MySQL Workbench Manual says Workbench is developed and tested with MySQL Server 8.0. It may connect to MySQL Server 8.4 and higher, but some features may not function with those later server versions. The manual covers Workbench 8.0 through 8.0.47; consult the official MySQL Workbench manual and download page for current release and platform details rather than assuming a particular installer or system requirement.
Before you create a connection
Have these details from your local installation, administrator, course, or hosting provider:
- The host name or IP address of the MySQL Server. A local server is often addressed as
localhostor127.0.0.1, but use the value configured for your installation. - The port, if you have been given one. Do not assume that a remote server uses the same port as a local setup.
- A MySQL user name and its password, if password authentication is configured.
- Any required SSL, SSH, or other network settings provided by the server administrator. These are not necessary for every local connection.
Workbench’s server-management settings are optional for a simple SQL connection. Do not guess credentials or change a server’s security settings just to make the connection form pass; confirm the correct values with whoever manages the server.
Recommended Free Tools
Create and test your first connection
- Open the Workbench home screen. Find the area for saved MySQL connections.
- Create a connection. Use the add-connection control and give the connection a recognizable name, such as “Local practice” or “Course server.” The name is a label in Workbench, not a database name.
- Enter the connection parameters. Choose the connection method and fill in the host, port, user name, and any other values supplied for your server. For a local setup, use the actual local server values; for a remote setup, use the endpoint and access instructions provided to you.
- Use Test Connection. Workbench’s connection walkthrough recommends checking the parameters and testing the connection before relying on a saved setup. Enter the password when prompted, if required. A successful test means Workbench could reach the server using the supplied settings at that time.
- Save and open the connection. Return to the home screen and open the saved connection to enter the SQL editor.
A successful test is not a guarantee that every database or permission is available to your user. It confirms the connection itself; access to a particular schema or operation still depends on the account’s grants and the server’s state.
Find your way around the SQL editor
The SQL editor is the main workspace for a first query. Its exact arrangement can vary, but the key areas are:
- Query tab: the text area where you type SQL statements.
- Schema navigator: a sidebar listing schemas and database objects available to the connected account. A schema is MySQL’s term commonly used for a database.
- Result grid: the tabular area where rows from a query such as
SELECTappear. - Output or action area: messages about executed statements, including whether a query succeeded or produced an error.
The editor also supports data editing, export workflows, basic administration, completion and context aids, and EXPLAIN plans. You do not need to learn all of those features before running a first query; start by distinguishing the query text from its results and execution messages.
Run a safe first query
Click inside a query tab and enter a read-only statement. If your connected account has a schema named sakila, this checks that the schema is visible:
Free tools Windows power users keep installed
One-click scans. No signup required.
SHOW DATABASES;
Run the current statement using the editor’s execute control. Workbench’s SQL editor displays returned rows in the result grid and execution feedback in its output area. If the query succeeds, inspect the list for schemas the account can access. The server may show different results for different users.
To examine a table only after selecting a schema you are authorized to use, try a read-only query such as:
SELECT * FROM sakila.actor LIMIT 10;
This example assumes the Sakila sample database is installed and that the connected user can read its actor table. If it is not present, the query will fail; that does not by itself indicate that Workbench or the connection is broken. Substitute a table and schema that actually exist for your account. The LIMIT 10 clause restricts the number of returned rows, which makes the example easier to inspect.
For a first session, avoid statements that change data or structure—such as UPDATE, DELETE, DROP, or ALTER—unless you understand their effects and have permission. A query tab is not a safety barrier: a statement that changes the database will do so if the server accepts it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
Try visual modeling after the first query
Modeling is useful when you want to plan tables and relationships visually rather than begin with an existing database. Workbench’s modeling tutorials cover creating a new model, basic modeling, and importing a SQL definition. An EER diagram (enhanced entity-relationship diagram) lets you represent tables and their relationships, including foreign keys.
Start with a new model
Create a new model and add a diagram. For a small practice exercise, define two related tables—for example, a customer table and an order table—and represent the relationship with a foreign key. Modeling helps you reason about structure before building it on a server; a diagram is not automatically the same thing as a deployed database.
Explore an existing SQL definition or Sakila
If you have a SQL definition file, the Workbench tutorials describe importing a SQL script into a model. The manual also uses the Sakila sample database for exploration. These are optional follow-on exercises, not prerequisites for creating a connection or executing a query. Use the official manual’s modeling tutorials for the current interface details.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot a connection or query
Test Connection cannot reach the server
First verify that the MySQL Server instance is installed and running. Workbench is only the client; opening it does not start a missing or stopped server. If the server is running, compare the host and port in the saved connection with the values actually configured for it. For a remote server, confirm that your network and account are permitted to reach it.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallThe server rejects the user name or password
Re-enter the credentials supplied for this server and confirm the user is authorized to connect from your location. Do not assume a Workbench saved connection creates a MySQL account; account creation and permissions belong to the server.
The connection works but a schema or table is missing
The connected account may not have permission to see or read that object, or the object may not exist on that server. Check the schema navigator and confirm the database name with the person or documentation that supplied the server. A sample query using Sakila will not work unless that sample database is available.
A query returns an error
Read the execution message in the output area and check the statement for spelling, selected schema, and object names. If a query targets a newer or different database setup, verify that the server version and feature are compatible with the Workbench version in use. For access errors, ask the server administrator about the account’s grants rather than repeatedly changing unrelated connection settings.
A feature behaves differently on a newer server
Compare your server version with the manual’s compatibility note. Workbench may connect to MySQL Server 8.4 or higher, but the Oracle manual does not promise that every feature will function with those versions. A connection succeeding does not establish full feature compatibility.
Or skip the browser setup
MySQL Workbench is for interacting with MySQL servers; ScreenshotNeo is a separate website screenshot API, not a replacement for a database client. If you need a screenshot of a web page—for example, a page documenting a database setup—one GET request can return an image or PDF. See the ScreenshotNeo documentation for its API details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://dev.mysql.com/doc/ -o shot.webp
- Cookie and consent banners, newsletter popups, and chat widgets are removed before capture; each cleanup step can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Response headers report the page verdict and billing status.
- An MCP server provides
take_screenshot,get_page_info, andcapture_pdftools for AI agents and MCP clients. - The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Every feature is available on every plan.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
