Installing SQL — Getting Started with SQL Tools

A teacher opens a SQL editor and sees a connection error. The editor is ready, but no database connection has been configured.

A database engine stores and processes data; a client or editor sends SQL to that engine. Installing an editor and connecting to a running database are separate steps.

Choose the database engine used by your project, then install a compatible client. MySQL Workbench connects to a MySQL server; SQLite can operate on a local file without a separate server. A connection needs the correct server address, account and database. The command-line login example belongs to a shell, rather than to the SQL statement editor.

Related concepts: SQL Syntax and Users and Permissions.

If you're just stepping into the world of databases, this guide will help you get your environment ready. By the end of this tutorial, you'll have SQL installed, your tools set up, and you'll be writing your first query against a student database.

There are multiple options for relational database systems, but the most beginner-friendly are:

• MySQL – Widely used in web development
• PostgreSQL – Known for reliability and features
• SQLite – Lightweight and doesn’t need installation

We’ll walk through setting up MySQL and PostgreSQL.

Step-by-Step (Windows)

1. Download the MySQL Installer.
2. Run the installer and choose Developer Default.
3. Set root password (e.g., admin123) and remember it.
4. Once installed, launch MySQL Workbench.

Step-by-Step (Windows)

1. Download from postgresql.org.
2. Run the installer, set the password for the postgres user (e.g., admin123).
3. Install pgAdmin as GUI client.
4. Open pgAdmin and connect using your password.

• MySQL Workbench: Clean interface, easy to run scripts and visualize schemas
• pgAdmin: PostgreSQL’s official GUI client with powerful features
• DB Browser for SQLite: If you're learning SQL offline

Use a disposable school database for these exercises. Keep passwords out of saved query files and do not use an administrative account for routine application work. Installer screens and available connectors depend on platform and product version.

After connecting, run this small query. What does a successful result tell you, and what does it leave untested?

This practice uses a separate, fresh fixture named practice_students. It does not continue the changing table state of the earlier examples.

SQL · create only these practice tables in a disposable database:

CREATE TABLE practice_students (roll_no INTEGER PRIMARY KEY, name VARCHAR(50), class VARCHAR(10), marks INTEGER, city VARCHAR(30));
INSERT INTO practice_students VALUES
(1, 'Aarav', '10A', 85, 'Pune'),
(2, 'Diya', '9B', 70, 'Chennai'),
(3, 'Sneha', '10A', 85, 'Pune');

This practice uses a separate, fresh fixture named practice_students. It does not continue the changing table state of the earlier examples.

SQL · create only these practice tables in a disposable database:

CREATE TABLE practice_students (roll_no INTEGER PRIMARY KEY, name VARCHAR(50), class VARCHAR(10), marks INTEGER, city VARCHAR(30));
INSERT INTO practice_students VALUES
(1, 'Aarav', '10A', 85, 'Pune'),
(2, 'Diya', '9B', 70, 'Chennai'),
(3, 'Sneha', '10A', 85, 'Pune');

SQL · this practice variation runs with SQLite 3; the preserved examples retain their stated dialect

SELECT 1 AS connection_check;

The client can submit a statement and receive a result. This does not prove that a school table exists or that the account can modify it.

A database engine stores and processes data; a client or editor sends SQL to that engine. Installing an editor and connecting to a running database are separate steps.

The client can submit a statement and receive a result. This does not prove that a school table exists or that the account can modify it.

Continue your understanding with SQL Syntax and Users and Permissions.

Source for the engine-specific behavior: MySQL 8.4 reference documentation.