---
title: "Using Drizzle Studio"
description: "Drizzle Studio is a visual database manager designed to help you interact with your database directly through a web browser. It provides a user-friendly interface to view your tables, inspect data,..."
last_updated: "2026-07-02T09:37:14.238413+00:00"
canonical_url: "https://www.doc0.dev/docs/e1b68fed-3c4e-4c95-b2ba-ebf050f78025/guide/how-to-guides/using-drizzle-studio"
---

Drizzle Studio is a visual database manager designed to help you interact with your database directly through a web browser. It provides a user-friendly interface to view your tables, inspect data, and manage relationships without needing to write manual queries.

By connecting to your database, Drizzle Studio automatically detects your data structure and presents it in an organized dashboard, making it easier to navigate and understand your information.

## Getting Started

To use Drizzle Studio, you typically run a command in your terminal that initializes the connection between the tool and your database.

1.  **Initialize the connection:** Ensure your project is configured with the necessary database credentials.
2.  **Launch the interface:** Use the appropriate command provided by your project's toolkit to start the Drizzle Studio server.
3.  **Open in Browser:** Once the server is running, it will output a local address (usually `localhost` followed by a port number). Open this address in your web browser to access the dashboard.
4.  **Explore your data:** Use the sidebar to select tables and view your data rows.

> [!NOTE]
> Drizzle Studio needs access to your database connection details to display your schema. Ensure your project environment variables or configuration settings are correctly set up before starting the tool.

## Key Concepts

*   **Dialect:** This refers to the type of database you are using (e.g., PostgreSQL, MySQL, SQLite, or SingleStore). Drizzle Studio adapts its interface based on the specific requirements of your chosen database technology.
*   **Schema:** The organization or structure of your database, including tables, columns, and the relationships between them.
*   **Proxy:** A bridge that allows the Drizzle Studio web interface to communicate with your live database securely.
*   **Custom Defaults:** If your columns have special functions that generate default values (like timestamps or unique identifiers), Drizzle Studio identifies and triggers these functions when necessary.

## Tips and Warnings

> [!TIP]
> If you have complex relationships defined between your tables, ensure they are correctly set up in your schema. Drizzle Studio uses these definitions to help you navigate linked data easily.

> [!WARNING]
> If you encounter an error regarding "ambiguous relations," check your schema definitions. Misconfigured relationships can prevent the dashboard from correctly displaying how your data connects.

> [!CAUTION]
> Drizzle Studio performs live operations on your database. Always ensure you have a backup of your data if you are performing bulk edits or deletions through the interface.

## Troubleshooting Common Issues

| Issue | Potential Cause | Action |
| :--- | :--- | :--- |
| Cannot connect | Invalid credentials | Check your database connection string and environment variables. |
| Missing tables | Schema not detected | Ensure your database files are correctly exported/referenced in your setup. |
| UI not loading | Server offline | Verify that the terminal window running the command is still active. |
| Relation errors | Ambiguous schema | Review your schema file to ensure relationships are explicitly defined. |

## Workflow Diagram

```mermaid
graph LR
    User[User] -->|Run Command| CLI[CLI Tool]
    CLI -->|Connect| DB["(Database)"]
    CLI -->|Launch| Web[Web Browser Interface]
    Web -->|Query| Proxy[Proxy Server]
    Proxy -->|Execute| DB
```

## Related

- [Configuration File Reference](https://www.doc0.dev/docs/e1b68fed-3c4e-4c95-b2ba-ebf050f78025/guide/configuration/configuration-file-reference)


## Sitemap

See the full [sitemap](https://www.doc0.dev/docs/e1b68fed-3c4e-4c95-b2ba-ebf050f78025/llms.txt) for all pages in this wiki.