DBeaver is useful for this because one application can work with several database systems, including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, and others.

In this guide, we'll set up a local database connection in DBeaver, test it, and run a simple SQL query.

What You Need

Before starting, make sure you have:

• DBeaver installed on Windows

• A local database server or SQLite database file

• The database name

• Username and password, if authentication is required

• The correct port for a server-based database

If DBeaver is not installed yet, this DBeaver Download for Windows 11 & 10 guide covers the Windows installation, available packages, and initial setup.

Step 1: Open the New Database Connection Wizard

Launch DBeaver.

From the main interface, select:

Database → New Database Connection

You can also use the New Connection button from the toolbar.

DBeaver will display a list of available database drivers. Its official documentation confirms that the connection wizard lets you search for and select the appropriate driver before configuring the connection.

Step 2: Select Your Database

Choose the database engine you want to connect to.

For example:

• PostgreSQL

• MySQL

• MariaDB

• Microsoft SQL Server

• SQLite

For this tutorial, imagine that PostgreSQL is running locally.

Select PostgreSQL and click Next.

DBeaver may need to download the appropriate driver the first time you use a particular database type. Allow it to complete before continuing.

Step 3: Enter the Connection Details

For a typical local server, you will need several pieces of information.

Host

For a database running directly on the same Windows PC, this is commonly:

localhost

You may also see:

127.0.0.1

Port

The port depends on the database server.

Common defaults include:

Your installation may use a different port, so check the database configuration rather than assuming the default.

Database

Enter the database you want to access.

For example:

sampledb

Username and Password

Enter the credentials configured for your database server.

DBeaver's connection settings normally use the host, port, database name and authentication information for server-based databases.

Step 4: Test the Connection

Before saving anything, click:

Test Connection

If everything is configured correctly, DBeaver should report that the connection succeeded.

Then click Finish.

The new connection should appear in the connection tree.

Testing first is useful because it separates connection problems from problems you might encounter later while running queries.

Step 5: Explore the Database

Expand your new connection from the navigator.

Depending on the database system, you may see objects such as:

• Databases

• Schemas

• Tables

• Views

• Procedures

• Indexes

Expand a schema and then its Tables section.

This is one of the advantages of using a graphical database client: you can inspect the database structure before writing SQL against it.

Step 6: Run Your First Query

Open an SQL Editor for the active connection.

Try a simple query such as:

SELECT *
FROM customers;

If your database does not contain a customers table, replace it with one of your actual table names.

For a quick connection test, you can also run something simple that your database supports.

The important thing is to make sure the SQL Editor is attached to the correct connection before executing anything.

Connecting to SQLite Is Slightly Different

SQLite does not normally require a separate database server listening on a network port.

Instead, the database is stored in a file.

In DBeaver:

1. Create a new connection.

2. Select SQLite.

3. Browse to your .db or .sqlite file.

4. Test the connection.

5. Finish the setup.

This makes SQLite particularly convenient for local development, testing, and small applications.

What If DBeaver Cannot Connect?

A failed connection does not necessarily mean DBeaver itself is broken.

Check these common causes first.

Database Server Is Not Running

For PostgreSQL, MySQL, MariaDB, or SQL Server, confirm that the database service is actually running.

A perfectly configured client cannot connect to a stopped server.

Wrong Port

Make sure the port entered in DBeaver matches the port your database is listening on.

This is especially important when multiple database instances are installed.

Incorrect Credentials

Double-check the username and password.

Authentication errors and network errors are different problems, so pay attention to the message DBeaver displays.

Wrong Database Name

The server may be reachable while the requested database does not exist or the account does not have permission to access it.

Docker Port Is Not Exposed

If your database is running in Docker, exposing the database port is essential before a normal Windows application can connect to it.

For example, a PostgreSQL container might map its internal port to a Windows host port.

Your DBeaver connection then needs to use that exposed host port.

Be Careful With Production Databases

DBeaver makes browsing and editing data convenient, but convenience can also make accidental changes easier.

When working with an important database:

• Check which connection is active.

• Avoid using administrator credentials unnecessarily.

• Review UPDATE and DELETE statements carefully.

• Use transactions where appropriate.

• Keep backups.

• Consider read-only access when you only need to inspect data.

DBeaver also provides connection security controls that can restrict data editing, structural changes, script execution, and other operations.

A Simple Local Development Workflow

Once your connection works, a straightforward workflow is:

Start database → Open DBeaver → Connect → Browse schema → Open SQL Editor → Run queries → Review results

You do not need a complicated setup for everyday local database work.

The most important part is understanding which server, port, database, and user your DBeaver connection actually represents.

Final Thoughts

Connecting DBeaver to a local database on Windows is mostly about getting four things right: the database driver, server address, connection settings, and authentication.

Once the connection is established, DBeaver gives you a convenient workspace for exploring database objects, running SQL, reviewing results, and working across different database engines without constantly switching tools.

For someone learning SQL or maintaining several local development databases, that can make day-to-day database work considerably easier.

Installing Python on Windows is usually straightforward, but completing the installer does not always mean everything is configured correctly. Windows may have multiple Python installations, the PATH variable may not be configured, or the python command may point somewhere unexpected.

A few quick checks can confirm that Python and pip are ready to use before you start working on projects.

1. Check Python from Command Prompt

Open Command Prompt by pressing Windows + R, typing cmd, and pressing Enter.

Run:

python --version

If Python is installed and available through PATH, Windows should display the installed Python version.

You can also try:

py --version

The py command uses the Python Launcher for Windows and can be useful when more than one Python version is installed.

1. Confirm Python Can Run Code

Checking the version confirms that Windows recognizes Python, but it is also useful to make sure the interpreter actually runs.

Enter:

python

You should enter the interactive Python interpreter. Then try:

print("Python is working")

If the message appears correctly, the interpreter is functioning.

Type:

exit()

to return to Command Prompt.

1. Check Whether pip Is Available

Most Windows users will also need pip for installing Python packages.

Run:

pip --version

or:

python -m pip --version

If pip is configured correctly, the command should show its version and installation location.

The second command can be particularly useful because it explicitly runs pip through the Python interpreter you selected.

1. Find Which Python Installation Windows Is Using

If you have installed Python more than once, check which executable Windows finds.

Run:

where python

Windows may return one or several paths.

This is useful when an older Python installation is being selected instead of the version you intended to use.

1. What If “Python Is Not Recognized” Appears?

If Command Prompt says that Python is not recognized as a command, one common reason is that Python was not added to PATH during installation.

You can check your installation and PATH configuration before reinstalling anything.

If you still need Python or want to review the Windows installation process, the Python Download for Windows guide on ABDNOVA covers the download source, installation steps, and PATH setup.

1. Test pip with a Package

Once Python and pip are working, you can perform another simple check:

python -m pip list

This displays the packages available in the current Python environment.

You do not need to install random packages just to test Python. If the command works and displays the package list, pip is responding correctly.

Final Check

A working Python setup on Windows should pass these basic tests:

python --version returns a version Python can open the interactive interpreter python -m pip --version works where python points to the expected installation Simple Python code runs without errors

Taking a minute to verify these items can prevent confusing PATH, pip, and interpreter problems later.