Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Public Preview in the following regions: westus, westus2, eastus, eastus2, northeurope, westeurope, australiaeast, brazilsouth, canadacentral, centralindia, centralus, southcentralus, southeastasia, uksouth.
This page outlines the different ways to work with your Lakebase database instance and recommends how to optimize PostgreSQL queries.
Ways to access your Database
Here are the following methods to access your database instance to run PostgreSQL queries and manage identities. As a managed Postgres service, there are some limitations in functionality. See Postgres compatibility.
| Method | Description |
|---|---|
| SQL editor | Connect to and query your database from the Databricks SQL editor. |
| Azure Databricks notebooks | Connect to and query from your database from Azure Databricks notebooks. |
| SQL clients | Connect to and query from your database from external tools such as psql, DBeaver, and pgAdmin. |
If you query through a Databricks SQL endpoint, the query is federated to a database instance.
Run federated queries in Databricks SQL
Use federated queries via DBSQL to query your Postgres table without syncing your data.
Key considerations:
- Latency: Federated queries have higher latency than direct PostgreSQL queries.
- Throughput: Databricks SQL supports lower queries per second (QPS) compared to querying PostgreSQL directly.
- Query optimization: For best performance, write queries that filter on the primary key or an indexed column of the Postgres table.