DBeaver Blog

Database driver Google Cloud Spanner

Note: This driver is available in Lite, Enterprise, Ultimate and Team editions only.

Table of contents

Overview

This guide provides step-by-step instructions on how to set up and manage Google Cloud Spanner databases using DBeaver.

Before you can start managing your database, it’s essential to establish a connection in DBeaver. This involves selecting the

Google Cloud Spanner
option to connect to your database. If you have not yet created a connection in DBeaver, please refer to our Creating a Connection article for guidance.

Tip: Users with Ultimate and Team editions of DBeaver can connect to their Google Spanner databases using the Cloud Explorer.

Google Spanner specialty

Google Spanner is a distributed database system that combines features from both relational and NoSQL databases. It stands out for its large-scale capabilities, designed to manage extensive data across numerous nodes while maintaining high availability and global consistency.

In Google Spanner, the metadata types resemble those in traditional relational databases, with tables, columns, schemas, and key constraints, including primary keys, foreign keys, and unique constraints. A significant aspect of Google Spanner is its synchronization mechanism for nodes. It uses atomic clocks and GPS receivers to power its TrueTime system, ensuring precise synchronization across all nodes. This advanced timekeeping infrastructure is crucial for maintaining external consistency in distributed transactions and offers a robust solution for strong consistency on a global scale. For a more comprehensive understanding of Google Spanner, please refer to the official documentation.

Setting Up

This section provides an overview of DBeaver’s settings for establishing a direct connection and the configuration of secure connections using SSH, proxies, and Kubernetes.

Google Spanner connection settings

In this subsection, we will outline the settings for establishing a direct connection to a Google Spanner database using DBeaver. Correctly configuring your connection ensures seamless interaction between DBeaver and your Google Spanner database.

The page of the connection settings requires you to fill in specific fields to establish the initial connection.

Field Description
Project Enter the project name of your Google Spanner database here.
Instance For a direct connection to a Google Spanner instance, use the format
project:region:instance
. Here,
project
refers to your Google Cloud project ID,
region
denotes the geographical location of your instance, and
instance
is the unique ID of your Google Cloud SQL instance.
Database Enter the name of the Google Spanner database you want to connect to.
Authentication Choose the type of authentication you want to use for the connection. For detailed guides on authentication types, please refer to the following articles:

– Google Cloud IAM (Spanner)
– DBeaver Profile Authentication

You can also read about security in DBeaver PRO.
Connection Details Provide additional connection details if necessary.
Driver Name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

Connection details

The Connection Details section in DBeaver allows for further customization of your Google Spanner connection. This includes options for adjusting the Navigator View, setting up Security measures, applying Filters, configuring Connection Initialization settings, and setting up Shell Commands. Each of these settings can significantly impact your database operations and workflow. For detailed guides on these settings, please refer to the following articles:

Google Spanner driver properties

The settings for Google Spanner Driver properties enable you to adjust the performance of the Google Spanner JDBC driver. These adjustments can influence the efficiency, compatibility, and features of your Google Spanner database.

For a complete walkthrough on setting up Google Spanner JDBC driver properties, you can refer to the official Google Spanner JDBC documentation.

You can customize the Google Spanner driver in DBeaver via the Edit Driver page, accessible by clicking on the Driver Settings button on the first page of the driver settings. This page offers a range of settings that can influence your Google Spanner database connections. For a comprehensive guide on these settings, please refer to our Database drivers article.

Secure Connection Configurations

DBeaver supports secure connections to your Google Spanner database. Guidance on configuring such connections, specifically SSH, Proxy, Kubernetes and AWS SSM connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Powering Google Spanner with DBeaver

DBeaver provides a host of features designed for Google Spanner databases. This includes the ability to view and manage databases, along with numerous unique capabilities aimed at optimizing database operations.

Google Spanner database objects

DBeaver lets you view and manipulate a wide range of Google Spanner database objects. DBeaver has extensive support for various Google Spanner metadata types, allowing you to interact with a wide variety of database objects, such as:

  • Databases

    • Tables
      • Columns
      • Keys
      • Foreign Keys
      • Indexes
      • References
    • Views
    • Procedures

Google Spanner additional features in DBeaver

DBeaver provides additional features compatible with Google Spanner, but not exclusive to it:

Category Feature
Data Transfer Data Import
Data Export
Data Visualization ERD Guide
Data Generation Mock Data Generation
0 Comments

Database driver Greenplum

Table of contents

Overview

This guide provides instructions on how to set up and use Greenplum with DBeaver.

Before you can start managing your database, it’s essential to establish a connection in DBeaver. This involves selecting the

Greenplum
option to connect to the Greenplum database. If you have not yet created a connection in DBeaver, please refer to our Creating a Connection article for guidance.

Greenplum specialty

Greenplum is a highly scalable, multi-node relational database system, primarily used for data warehousing and analytics. A key characteristic of Greenplum is its columnar data storage capabilities, making it particularly effective for analytics and large-scale data processing. Built on PostgreSQL, it supports rich metadata structures, including tables, views, indexes, sequences, and various data types. Its setup in DBeaver mostly replicates the PostgreSQL driver configuration. Greenplum includes support for SQL triggers, stored procedures, and user-defined functions, enhancing its utility for complex data operations. It also provides robust data partitioning options and supports diverse storage models like row and column store, optimizing performance for a variety of workloads. For a more comprehensive understanding of Greenplum, please refer to the official documentation.

Setting Up

This section provides an overview of DBeaver’s settings for establishing a direct connection and the configuration of secure connections using SSH, proxies, Kubernetes, SSL, and the setup of ODBC/JDBC drivers for Greenplum.

Greenplum connection settings

In this subsection, we will outline the settings for establishing a direct connection to a Greenplum database using DBeaver. Correctly configuring your connection ensures seamless interaction between DBeaver and your Greenplum database.

1) The first page of the connection settings requires you to fill in specific fields to establish the initial connection.

Field Description
Connect by (Host/URL) Choose whether you want to connect using a host or a URL.
Driver Type Select the appropriate driver for your Greenplum database.
URL If you are connecting via URL, enter the URL of your Greenplum database here. This field is hidden if you are connecting via the host.
Host If you are connecting via host, enter the host address of your Greenplum database here.
Database Enter the name of the Greenplum database you want to connect to.
Show all databases Displays all databases in the database navigator.
Note: This option works only when the Host connection type is selected. It does not work when connecting via URL.
Port Enter the port number for your Greenplum database. The default Greenplum port is
5432
.
Authentication Choose the type of authentication you want to use for the connection. For detailed guides on authentication types, please refer to the following articles:

– Native Database Authentication
– DBeaver Profile Authentication
– PostgreSQL Kerberos Authentication
– PostgreSQL PgPass Authentication
– PostgreSQL SSPI Authentication

You can also read about security in DBeaver PRO.
Local Client Specify the local client, see our article about Local client.
Connection Details Provide additional connection details if necessary.
Driver Name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

2) The second page of the connection settings offers additional options that allow you to customize your further connection to the Greenplum database.

Field Description
Show template databases Displays template databases. This option is available when Show all databases is checked.
Show databases unavailable for connection Show databases not available for connection in database list. This option is available when Show all databases is checked.
Show databases statistics Displays statistics for databases.
Read all data types Reads all data types from the server (including arrays).
Read table keys with columns Enable reading table constraints during the column reading stage to ensure accurate recognition of keys. Note that this setting may decrease metadata loading performance.
Show
$$
quote as 		Displays
$$
quotes as code blocks or strings.
Show
$tagName$
quote as 		Displays
$tagName$
quotes as code blocks or strings.
Use prepared statements Uses prepared statements for SQL execution.

Connection details

The Connection Details section in DBeaver allows for further customization of your Greenplum connection. This includes options for adjusting the Navigator View, setting up Security measures, applying Filters, configuring Connection Initialization settings, and setting up Shell Commands. Each of these settings can significantly impact your database operations and workflow. For detailed guides on these settings, please refer to the following articles:

Greenplum driver properties

The settings for Greenplum Driver properties enable you to adjust the performance of the Greenplum JDBC and ODBC driver. These adjustments can influence the efficiency, compatibility, and features of your Greenplum database.

For a complete walkthrough on setting up Greenplum JDBC and ODBC drivers properties, you can refer to the official Greenplum JDBC documentation and Greenplum ODBC documentation. These guides detail each driver’s properties and how they can be used to optimize Greenplum database connections.

You can customize the Greenplum driver in DBeaver via the Edit Driver page, accessible by clicking on the Driver Settings button on the first page of the driver settings. This page offers a range of settings that can influence your Greenplum database connections. For a comprehensive guide on these settings, please refer to our Database drivers article.

ODBC and JDBC Driver Configuration

DBeaver provides extensive capabilities for managing Greenplum database connections via ODBC/JDBC drivers. This functionality enables you to connect to your Greenplum database using native ODBC drivers, offering an alternative when specific DBeaver drivers are not available.

You can find a comprehensive, step-by-step guide on how to install the driver manager, set up drivers, configure data sources, and establish connections in DBeaver in our ODBC Driver Configuration article.

Secure Connection Configurations

DBeaver supports secure connections to your Greenplum database. Guidance on configuring such connections, specifically SSH, Proxy, Kubernetes, AWS SSM and SSL connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Powering Greenplum with DBeaver

DBeaver provides a host of features designed for Greenplum databases. This includes the ability to view schemas, along with numerous unique capabilities aimed at optimizing database operations.

Greenplum database objects

DBeaver lets you view and manipulate a wide range of Greenplum database objects. DBeaver has extensive support for various Greenplum metadata types, allowing you to interact with a wide variety of database objects, such as:

  • Databases
    • Schemas
      • Data types
      • Tables
        • Columns
        • Constraints
        • Indexes
        • Dependencies
        • References
        • Partitions
        • Triggers
        • Rules
        • Policies
      • External Tables
      • Views
      • Functions
      • Sequences
      • Data types
      • Aggregate functions
    • Event triggers
    • Storage
      • Tablespaces
    • Roles

  • Administer

    • Jobs
    • Session Manager
    • Lock Manager

Greenplum Features in DBeaver

DBeaver is not limited to typical SQL tasks. It also includes numerous additional features compatible with Greenplum, but not exclusive to it:

Category Feature
Data Transfer Data Import
Data Export
Session Management Session Manager
Lock Management Lock Manager
Backup and Restore How to Backup/Restore data
Schema Management Schema Compare
Data Visualization GIS Guide
ERD Guide
Query Execution plan
Data Generation Mock Data Generation
0 Comments

Database driver IBM Db2

Table of contents

Overview

This guide provides instructions on how to set up and use IBM DB2 with DBeaver.

Before you start, you must create a connection in DBeaver and select IBM DB2. If you have not done this, please refer to our Database Connection article.

DBeaver interacts with the IBM DB2 server using a specific driver, it supports all versions of IBM DB2, but the correct driver must be selected: use Db2 for LUW (Old 8.x) for versions below 8.x and Db2 for LUW for newer versions. DBeaver also supports various IBM DB2 databases such as Db2 for IBM i, and Db2 for z/OS. You must select the appropriate driver in the Connect to a database window for these databases.

Setting Up

This section provides an overview of DBeaver’s settings for establishing a direct connection and the configuration of secure connections using SSH, proxies, SSL, and the setup of ODBC/JDBC drivers for Db2.

Db2 connection settings

In this subsection, we will outline the settings for establishing a direct connection to a Db2 database using DBeaver. Correctly configuring your connection ensures seamless interaction between DBeaver and your Db2 database.

The page of the connection settings requires you to fill in specific fields to establish the initial connection.

Field Description
Connect by (Host/URL) Choose whether you want to connect using a host or a URL.
Driver Type Select the appropriate driver for your Db2 database.
URL If you are connecting via URL, enter the URL of your Db2 database here. This field is hidden if you are connecting via the host.
Host If you are connecting via host, enter the host address of your Db2 database here.
Database Enter the name of the Db2 database you want to connect to.
Port Enter the port number for your Db2 database.
Authentication Choose the type of authentication you want to use for the connection. For detailed guides on authentication types, please refer to the following articles:

– Native Database Authentication
– DBeaver Profile Authentication
Connection Details Provide additional connection details if necessary.
Driver Name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

Connection details

The Connection Details section in DBeaver allows for further customization of your Db2 connection. This includes options for adjusting the Navigator View, setting up Security measures, applying Filters, configuring Connection Initialization settings, and setting up Shell Commands. Each of these settings can significantly impact your database operations and workflow. For detailed guides on these settings, please refer to the following articles:

Trace Settings

In DBeaver, the trace settings feature allows you to monitor and record database operations in a detailed manner. To enable this feature, check the Enable trace box. You will need to specify a file where the traced information will be stored and formatted into a readable format.

The trace settings page allows you to configure various levels and settings to tailor the tracing process according to your preferences.

Setting Description
Folder/File name Specify the directory and file name where the trace data will be stored. This file will contain detailed information about the operations performed in the database.
Append This option allows you to add information to an existing trace file, instead of creating a new file each time the trace is enabled.
Connection Calls Records calls related to database connections.
Result Set Calls Records calls pertaining to the result sets.
Connects Records information about database connects.
Result Set Metadata Records metadata information from the result sets.
Diagnostics Records diagnostic information about database operations.
XA Calls Records information on XA distributed transactions.
Statement Calls Records calls related to SQL statements.
Driver Configuration Records configuration details of the database driver.
DRDA Flows Records information on DRDA data flows.
Parameter Metadata Records metadata about SQL parameters.
SQL J Records information on SQL J operations.

For more detailed information on these settings, please refer to the IBM documentation.

Db2 driver properties

The settings for Db2 Driver properties enable you to adjust the performance of the Db2 JDBC and ODBC driver. These adjustments can influence the efficiency, compatibility, and features of your Db2 database.

For a complete walkthrough on setting up Db2 JDBC and ODBC drivers properties, you can refer to the official Db2 JDBC documentation and Db2 ODBC documentation. These guides detail each driver’s properties and how they can be used to optimize Db2 database connections.

You can customize the Db2 driver in DBeaver via the Edit Driver page, accessible by clicking on the Driver Settings button on the first page of the driver settings. This page offers a range of settings that can influence your Db2 database connections. For a comprehensive guide on these settings, please refer to our Database drivers article.

ODBC and JDBC Driver Configuration

DBeaver provides extensive capabilities for managing Db2 database connections via ODBC/JDBC drivers. This functionality enables you to connect to your Db2 database using native ODBC drivers, offering an alternative when specific DBeaver drivers are not available.

You can find a comprehensive, step-by-step guide on how to install the driver manager, set up drivers, configure data sources, and establish connections in DBeaver in our ODBC Driver Configuration article.

Secure Connection Configurations

DBeaver supports secure connections to your Db2 database. Guidance on configuring such connections, specifically SSH, Proxy, SSL, Kubernetes and AWS SSM connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Powering Db2 with DBeaver

DBeaver provides a host of features designed for Db2 databases. This includes the ability to view schemas, along with numerous unique capabilities aimed at optimizing database operations.

Db2 database objects

DBeaver lets you view and manipulate a wide range of Db2 database objects. DBeaver has extensive support for various Db2 metadata types, allowing you to interact with a wide variety of database objects, such as:

  • Schemas
    • Tables
      • Columns
      • Unique Constraints
      • Foreign Keys
      • Indexes
      • References
      • Check Constraints
      • Partitions
      • Periods
      • Triggers
      • Columns Masks
    • Views
    • MQTs
    • Indexes
    • Sequences
    • Aliases
    • Nicknames
    • Triggers
    • XML Schemas
    • Application Objects
      • Functions
      • Modules
      • Packages
      • Procedures
      • User Defined Types
  • Federation
    • Wrappers
    • Remote Servers
    • User Mappings
  • Global metadata
    • Types
    • Variables
    • XML Strings
  • Storage
    • Bufferpools
    • Tablespaces
    • Storage Groups
  • Administer
    • Session Manager

  • Security

    • Roles
    • Groups
    • Users

Db2 features in DBeaver

DBeaver is not limited to typical SQL tasks. It also includes numerous unique features specifically for DB2. Beyond regular SQL operations, DBeaver provides a range of Db2-specific capabilities, such as:

Category Feature
Schemas Unique Constraints
Periods
Column Masks
Views MQTs
Federation Wrappers
Remote Servers
Global Metadata XML Strings
Storage Bufferpools
Tablespaces
Security Roles
Groups

Additional features compatible with Db2, but not exclusive to it:

Category Feature
Data Transfer Data Import
Data Export
Session Management Session Manager
Lock Management Lock Manager
Schema Management Schema Compare
Data Visualization GIS Guide
ERD Guide
0 Comments

Database driver Azure Databricks

Table of contents

Overview

This guide provides instructions on how to set up and use Databricks with DBeaver.

Before you can start managing your database, it’s essential to establish a connection in DBeaver. This involves selecting the

Databricks
option to connect to the Databricks database. If you have not yet created a connection in DBeaver, please refer to our Creating a Connection article for guidance.

Databricks specialty

Azure Databricks, based on Apache Spark, is a distributed computing system primarily used for machine learning and big data analytics. Its architecture is specially optimized for handling large-scale data processing and advanced analytics tasks. Azure Databricks integrates with MLlib in Apache Spark, offering scalable algorithms and utilities for machine learning tasks. It also facilitates collaborative work through its notebooks, allowing teams to share code, visualizations, and insights effectively. For more detailed information and a comprehensive understanding of Azure Databricks, please refer to the official documentation.

Setting up

This section provides an overview of DBeaver’s settings for establishing a direct connection and the configuration of secure connections using SSH and proxies for Databricks.

Databricks connection settings

In this subsection, we will outline the settings for establishing a direct connection to a Databricks database using DBeaver. Correctly configuring your connection ensures seamless interaction between DBeaver and your Databricks database.

The page of the connection settings requires you to fill in specific fields to establish the initial connection.

Field Description
JDBC URL Enter the URL of your Databricks database here.
Authentication Choose the type of authentication you want to use for the connection. For detailed guides on authentication types, please refer to the following articles:

– Native Database Authentication
– DBeaver Profile Authentication

You can also read about security in DBeaver PRO.
Connection Details Provide additional connection details if necessary.
Driver Name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

Connection details

The Connection Details section in DBeaver allows you to customize your experience while working with a Databricks database. This includes options for adjusting the Navigator View, setting up Security measures, applying Filters, configuring Connection Initialization settings, and setting up Shell Commands. Each of these settings can significantly impact your database operations and workflow. For detailed guides on these settings, please refer to the following articles:

Databricks driver properties

The settings for Databricks Driver properties enable you to adjust the performance of Databricks JDBC driver. These adjustments can influence the efficiency, compatibility, and features of your Databricks database.

For a complete walkthrough on setting up Databricks JDBC driver properties, you can refer to the official Databricks JDBC documentation. These guides detail each driver’s properties and how they can be used to optimize Databricks database connections.

You can customize the Databricks driver in DBeaver via the Edit Driver page, accessible by clicking on the Driver Settings button on the first page of the driver settings. This page offers a range of settings that can influence your Databricks database connections. For a comprehensive guide on these settings, please refer to our Database drivers article.

Secure connection configurations

DBeaver supports secure connections to your Databricks database. Guidance on configuring such connections, specifically SSH, Proxy, Kubernetes and AWS SSM connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Powering Databricks with DBeaver

DBeaver provides a host of features designed for Databricks databases. This includes the ability to view and manage databases, along with numerous unique capabilities aimed at optimizing database operations.

Databricks database objects

DBeaver lets you view and manipulate a wide range of Databricks database objects. DBeaver has extensive support for various Databricks metadata types, allowing you to interact with a wide variety of database objects, such as:

  • Databases

    • Tables
      • Columns
      • Keys
      • Foreign keys
      • References
    • Views
    • Procedures

Databricks features in DBeaver

DBeaver is not limited to typical SQL tasks. It also includes numerous additional features compatible with Databricks, but not exclusive to it:

Category Feature
Data Transfer Data Import
Data Export
Data Visualization ERD Guide
Data Generation Mock Data Generation
0 Comments

Database driver BigQuery

Table of contents

Overview

This documentation details the steps for configuring and utilizing BigQuery with DBeaver. The integration in DBeaver supports distinctive BigQuery functionalities, accommodating its serverless infrastructure, robust scalability, and compatibility with multi-cloud data analytics.

Before you can start managing your database, it’s essential to establish a connection in DBeaver. This involves selecting the

BigQuery
option to connect to the BigQuery. If you have not yet created a connection in DBeaver, please refer to our Creating a Connection article for guidance.

Feature highlights

DBeaver’s database management capabilities include support for various data types tailored for complex data operations, such as:

  • BIGNUMERIC: Handles large-scale or high-precision decimal numbers.
  • GEOGRAPHY: Manages spatial information.
  • INTERVAL: Tracks durations with precision.

Additionally, DBeaver provides tools for database schema customization and task automation:

  • Views: Enables the creation of virtual tables based on SQL queries.

  • Procedures: Allows for the definition and execution of stored procedures for routine database tasks.

Setting up

This section provides an overview of DBeaver’s settings for establishing a direct connection and the configuration of secure connections using SSH, Proxies, and Kubernetes.

BigQuery connection settings

In this subsection, we will outline the settings for establishing a direct connection to a BigQuery database using DBeaver. Correctly configuring your connection ensures seamless interaction between DBeaver and your BigQuery database.

The page of the connection settings requires you to fill in specific fields to establish the initial connection.

Field Description
Project Enter the project ID for the Google Cloud Project where the BigQuery service is located.
Additional project(s) Specify any additional project IDs if applicable.
Host Set the host URL to the BigQuery API endpoint.
Port Enter the port number for your BigQuery database. The default BigQuery port is
443
.
Authentication Choose the type of authentication you want to use for the connection. For detailed guides on authentication types, please refer to the following articles:

– Google Cloud IAM
– DBeaver Profile Authentication

You can also read about security in DBeaver PRO.
Connection Details Provide additional connection details if necessary.
Driver Name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

Connection details

The Connection Details section in DBeaver allows for further customization of your BigQuery connection. This includes options for adjusting the Navigator View, setting up Security measures, applying Filters, configuring Connection Initialization settings, and setting up Shell Commands. Each of these settings can significantly impact your database operations and workflow. For detailed guides on these settings, please refer to the following articles:

Secure connection configurations

DBeaver supports secure connections to your BigQuery database. Guidance on configuring such connections, specifically SSH, Proxy, Kubernetes and AWS SSM connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Powering BigQuery with DBeaver

DBeaver provides a host of features designed for BigQuery databases. This includes the ability to view schemas, along with numerous unique capabilities aimed at optimizing database operations.

BigQuery database objects

DBeaver lets you view and manipulate a range of BigQuery database objects, such as:

  • Schemas

    • Tables
      • Columns
      • Keys
      • Foreign keys
      • Indexes
      • References
    • Views
    • Procedures

BigQuery additional features in DBeaver

DBeaver provides additional features compatible with BigQuery, but not exclusive to it:

Category Feature
Data Transfer Data Import
Data Export
Schema Management Schema Compare
ERD Guide
Data Generation Mock Data Generation
Query insights Result details
Disable metadata queries
Dashboards Bytes Processed for Project
0 Comments

Database driver CSV

Table of contents

Overview

This guide provides instructions on how to set up and use CSV files with DBeaver. The CSV Pro driver allows you to work with CSV data as if it were in a database. You can retrieve data and apply filters, sorting, and other operations, even combining data from multiple files.

Before you start, you need to create a connection in DBeaver and select the CSV Pro driver. If you haven’t done this, see our Database Connection article.

Tip: You can open and work with CSV files stored in your cloud storage directly in DBeaver. For setup instructions, see Cloud Storage.

Important: When using the CSV Pro driver, all connected CSV files are read-only. To make changes, you need to update the original files outside DBeaver.

Legacy CSV driver

In the Community Edition, a legacy CSV Basic driver is available. It supports only simple operations.

CSV Files driver connection settings

This section describes how to set up a connection using the CSV Pro driver. The connection settings page requires the following fields:

Field Description
Connect by (Host/URL) Choose whether to connect using a local host path or a URL.
File paths Specify the location of the CSV file(s). You can:
– File: Select a single CSV file.
– Folder: Choose a directory containing multiple CSV files.
– Remote: Access a remote folder via Cloud Storage. This feature is available only in Ultimate and Team Editions.
Driver name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

Tip: When using the Folder option, DBeaver scans the directory up to two levels deep for CSV files. For more information, see folder structure. If you select a folder, DBeaver organizes files in schemas based on their directory structure.

Features and capabilities

Advanced SQL query capabilities

The CSV Pro driver supports the full range of SQL queries:

  • Simple queries (e.g.,
    SELECT * FROM table
    ): Data is read directly from the CSV file.

  • Complex queries (e.g., using

    WHERE
    ,
    JOIN
    ,
    ORDER BY
    ,
    GROUP BY
    ): When a complex query is executed for the first time, the driver imports the entire CSV file into an internal database to enable advanced SQL functions. Subsequent queries run faster because the data is already imported into internal database.

Structuring CSV files with a schema

CSV files don’t include metadata about their structure, such as column names or data types. To enhance how DBeaver interprets these files, you can define a schema using a DDL (Data Definition Language) file.

Why use a DDL file

A DDL file helps DBeaver interpret your data more accurately by defining:

  • Column names
  • Data types

  • Optional indexes for better performance

How to create a DDL file
  1. Create a
    .ddl
    file with the same name as your CSV file, placing it in the same directory (e.g.,
    employees.csv
    and
    employees.csv.ddl
    ).
  2. Write a schema using the
    CREATE TABLE
    statement:


CREATE TABLE employees (

  id INTEGER,

  name TEXT NOT NULL,

  age INTEGER,

  department TEXT

  );

  CREATE INDEX idx_employees_id ON employees (id);

Important: If the DDL file contains errors, DBeaver will ignore it. You can still query the file, but column types will be inferred from the data.

Folder structure

When working with a folder containing multiple CSV files, DBeaver organizes them as follows:

Folder structure Schema in DBeaver
Root files
Default
schema
Subfolder files Schema named after the subfolder
Files in deeper folders Ignored

If your folder looks like this:



Data/

├── employees.csv

├── sales.csv

└── Reports/

    └── monthly.csv

    └── yearly.csv

DBeaver will create:

  • Default
    schema:
    employees
    ,
    sales
  • Reports
    schema:
    monthly
    ,
    yearly

Tip: To focus on specific files, consider selecting individual files or folders when configuring the connection.

Internal database

When you execute a complex query (such as

WHERE
,
JOIN
,
GROUP BY
, or
ORDER BY
.), on an CSV file for the first time, the CSV Pro driver processes the data by importing it into a temporary internal SQLite database.

By default, this internal database stores data temporarily on the disk during your session and is cleared when DBeaver restarts. To speed up queries on the same file in future sessions, you can specify the

internalDbFilePath
option in the Driver properties tab (e.g.,
C:\User\database.db
) to reuse the processed data.

Additional features

DBeaver provides additional features compatible with CSV Pro driver, but not exclusive to it:

Category Feature
Data Transfer Data Export
Data Visualization Visual Query Builder
Charts
0 Comments

Database driver CosmosDB

Note: This driver is available in Lite, Enterprise, Ultimate and Team editions only.

Table of contents

Overview

DBeaver offers extensive support for CosmosDB, a globally distributed, multimodel database service provided by Microsoft Azure.

Before you start, you must create a connection in DBeaver and select CosmosDB. If you have not done this, please refer to our Database Connection article.

CosmosDB is similar to MongoDB in many ways, and DBeaver’s support for CosmosDB includes collections browsing, data viewing, and SQL queries execution. For a detailed guide, refer to the MongoDB article.

Setting Up

Setting up CosmosDB in DBeaver is also similar to setting up MongoDB.

Secure Connection Configurations

DBeaver supports secure connections to your CosmosDB database. Guidance on configuring such connections, specifically SSH, Proxy, Kubernetes and AWS SSM connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Differences between CosmosDB and MongoDB in DBeaver

Session Manager

Unlike MongoDB, CosmosDB does not have a Session Manager in DBeaver. This means that you would not be able to manage server sessions directly within DBeaver when using CosmosDB.

Azure Connection

Unique to CosmosDB, DBeaver provides the option to connect through the Cloud Explorer feature, specifically for Azure. This feature allows you to browse and manage your Azure resources directly from DBeaver. You can view your CosmosDB instances, along with other Azure resources, in a structured tree view.

0 Comments

Database driver Firestore

Note: This driver is available in Enterprise, Ultimate and Team editions only.

Table of contents

Overview

This guide provides instructions on how to set up and use Firestore with DBeaver.

Before you can start managing your database, it’s essential to establish a connection in DBeaver. This involves selecting the

Firestore
option to connect to the Firestore database. If you have not yet created a connection in DBeaver, please refer to our Creating a Connection article for guidance.

Tip: Users with Ultimate and Team editions of DBeaver can connect to their Firestore databases using the Cloud Explorer.

Firestore specialty

Firestore is a flexible, scalable database for mobile, web, and server development from Firebase and Google Cloud Platform. Firestore is a NoSQL database that stores data in documents, which are organized into collections. Each document contains a set of key-value pairs and is identified by a unique identifier. Firestore’s real-time data synchronization capabilities allow developers to build collaborative applications by enabling real-time updates to data across all connected clients. It supports offline data access, enabling applications to function seamlessly without an internet connection. Security and data validation are enforced through Firestore Security Rules, allowing developers to control access to documents and collections. Firestore is designed to scale automatically, handling large datasets with ease. It supports powerful query capabilities, allowing efficient data retrieval and filtering. For more details, refer to the official Firestore documentation.

Setting Up

This section provides an overview of DBeaver’s settings for establishing a direct connection and the configuration of secure connections using SSH, proxies, and Kubernetes.

Firestore connection settings

In this subsection, we will outline the settings for establishing a direct connection to a Firestore database using DBeaver. Correctly configuring your connection ensures seamless interaction between DBeaver and your Firestore database.

The connection settings page requires you to fill in specific fields to establish the initial connection.

Field Description
Project Choose the name of the Project you want to connect to.
Database Enter the name of the Firestore database you want to connect to.
Authentication Choose the type of authentication you want to use for the connection. For detailed guides on authentication types, please refer to the following articles:

– DBeaver Profile Authentication
– Google Cloud IAM (coming soon)

You can also read about security in DBeaver PRO.
Connection Details Provide additional connection details if necessary.
Driver Name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

Connection details

The Connection Details section in DBeaver allows for further customization of your Firestore connection. This includes options for adjusting the Navigator View, setting up Security measures, applying Filters, configuring Connection Initialization settings, and setting up Shell Commands. Each of these settings can significantly impact your database operations and workflow. For detailed guides on these settings, please refer to the following articles:

Secure Connection Configurations

DBeaver supports secure connections to your Firestore database. Guidance on configuring such connections, specifically SSH, Proxy, Kubernetes and AWS SSM connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Powering Firestore with DBeaver

DBeaver provides support for Firestore, focusing on facilitating the management of collections and subcollections.

Working with Collections and Subcollections

Firestore organizes data into collections, which are containers for documents. Additionally, collections can contain subcollections, enabling a hierarchical structure for data organization.

The process for managing Firestore collections mirrors the familiar experience of creating and handling objects in the Database Navigator.

Creating a Subcollection

To work with Firestore subcollections, follow these instructions:

1) Open the collection in Data Editor and click the Subcollections button located in the right sidebar to access the management interface for Firestore’s subcollections. 2) In the Subcollections window, you will find options to create new subcollections, delete the existing ones, or refresh the list to view the latest data. 3) To add a Subcollection, click the Create collection button . You will be prompted to enter a name for the new collection. 4) After setting up the subcollection’s name, it is ready to be filled with data, structured according to your application’s requirements.

Viewing Subcollections

To view subcollections:

1) Navigate to the collection in Data Editor. 2) Select the object (collection) for which you wish to view the subcollections. 3) Click the Subcollections button .

Tip: To view data in

JSON
format, click the corresponding button in the left sidebar.

Firestore features in DBeaver

In addition to facilitating the management of collections and subcollections, DBeaver’s integration with Firestore includes a range of features designed to enhance the user experience and efficiency when working with Firestore databases. Here are some of the key features:

Category Feature
Data Transfer Data Export
0 Comments

Database driver AlloyDB for PostgreSQL

Note: This driver is available in Lite, Enterprise, Ultimate and Team editions only.

Table of contents

Overview

AlloyDB for PostgreSQL is a fully managed database service, tailored for demanding enterprise workloads. It blends the reliability and familiarity of PostgreSQL with Google’s advanced technology. This service delivers enhanced performance, scalability, and high availability, making it an ideal choice for critical business applications.

For more detailed information, visit Google AlloyDB webpage.

Before you can start managing your database, it’s essential to establish a connection in DBeaver. This involves selecting the

AlloyDB
option to connect to the AlloyDB database. If you have not yet created a connection in DBeaver, please refer to our Creating a Connection article for guidance.

AlloyDB specialty

AlloyDB for PostgreSQL is a fully managed database service, tailored for demanding enterprise workloads. It blends the reliability and familiarity of PostgreSQL with Google’s advanced technology and supports rich metadata structures, including tables, views, indexes, sequences, and various data types. Its setup in DBeaver mostly replicates the PostgreSQL driver configuration. AlloyDB includes support for SQL triggers, stored procedures, and user-defined functions, enhancing its utility for complex data operations. For a more comprehensive understanding of AlloyDB, please refer to the official documentation.

Setting Up

This section provides an overview of DBeaver’s settings for establishing a direct connection and the configuration of secure connections using SSH, proxies, SSL, and the setup of ODBC/JDBC drivers for AlloyDB.

Note: The connection process in DBeaver utilizes the standard PostgreSQL driver, tailored to interact with the AlloyDB service, highlighting its cloud-based characteristics.

AlloyDB connection settings

In this subsection, we will outline the settings for establishing a direct connection to an AlloyDB database using DBeaver. Correctly configuring your connection ensures seamless interaction between DBeaver and your AlloyDB database.

1) The first page of the connection settings requires you to fill in specific fields to establish the initial connection.

Field Description
Connect by (Host/URL) Choose whether you want to connect using a host or a URL.
Driver Type Select the appropriate driver for your AlloyDB database.
URL If you are connecting via URL, enter the URL of your AlloyDB database here. This field is hidden if you are connecting via the host.
Host If you are connecting via host, enter the host address of your AlloyDB database here.
Database Enter the name of the AlloyDB database you want to connect to.
Show all databases Displays all databases in the database navigator.
Note: This option works only when the Host connection type is selected. It does not work when connecting via URL.
Authentication Choose the type of authentication you want to use for the connection. For detailed guides on authentication types, please refer to the following articles:

– Native Database Authentication
– DBeaver Profile Authentication
– PostgreSQL Kerberos Authentication
– PostgreSQL PgPass Authentication
– PostgreSQL SSPI Authentication (Windows SSO)

You can also read about security in DBeaver PRO.
Local Client Specify the local client, see our article about local client configuration.
Session role This option allows you to define a specific role that your database session assumes upon connection. Setting a session role can be useful for managing permissions and access control within your AlloyDB database.
Connection Details Provide additional connection details if necessary.
Driver Name This field will be auto-filled based on your selected driver type.
Driver Settings If there are any specific driver settings, configure them here.

2) The second page of the connection settings offers additional options that allow you to customize your further connection to the AlloyDB database.

Field Description
Show template databases Displays template databases. This option is available when Show all databases is checked.
Show databases unavailable for connection Show databases not available for connection in database list. This option is available when Show all databases is checked.
Show databases statistics Displays statistics for databases.
Read all data types Reads all data types from the server (including arrays).
Read table keys with columns Enable reading table constraints during the column reading stage to ensure accurate recognition of keys. Note that this setting may decrease metadata loading performance.
Show
$$
quote as 		Displays
$$
quotes as code blocks or strings.
Show
$tagName$
quote as 		Displays
$tagName$
quotes as code blocks or strings.
Use prepared statements Uses prepared statements for SQL execution.

Connection details

The Connection Details section in DBeaver allows for further customization of your AlloyDB connection. This includes options for adjusting the Navigator View, setting up Security measures, applying Filters, configuring Connection Initialization settings, and setting up Shell Commands. Each of these settings can significantly impact your database operations and workflow. For detailed guides on these settings, please refer to the following articles:

Driver properties

While managing AlloyDB with DBeaver, it’s important to understand that the underlying driver is the standard PostgreSQL JDBC and ODBC driver.

The settings for AlloyDB Driver properties enable you to adjust the performance of the JDBC and ODBC driver. These adjustments can influence the efficiency, compatibility, and features of your AlloyDB database.

For a complete walkthrough on setting up JDBC and ODBC drivers properties, you can refer to the official JDBC documentation and ODBC documentation. These guides detail each driver’s properties and how they can be used to optimize AlloyDB database connections.

You can customize the driver in DBeaver via the Edit Driver page, accessible by clicking on the Driver Settings button on the first page of the driver settings. This page offers a range of settings that can influence your AlloyDB database connections. For a comprehensive guide on these settings, please refer to our Database drivers article.

ODBC and JDBC driver configuration

DBeaver provides extensive capabilities for managing AlloyDB database connections via ODBC/JDBC drivers. This functionality enables you to connect to your AlloyDB database using native ODBC drivers, offering an alternative when specific DBeaver drivers are not available.

You can find a comprehensive, step-by-step guide on how to install the driver manager, set up drivers, configure data sources, and establish connections in DBeaver in our ODBC Driver Configuration article.

Secure connection configurations

DBeaver supports secure connections to your AlloyDB database. Guidance on configuring such connections, specifically SSH, Proxy, Kubernetes, AWS SSM and SSL connections, can be found in various referenced articles. For a comprehensive understanding, please refer to these articles:

Powering AlloyDB with DBeaver

DBeaver provides a host of features designed for AlloyDB databases. This includes the ability to view schemas, along with numerous unique capabilities aimed at optimizing database operations.

AlloyDB database objects

DBeaver lets you view and manipulate a wide range of AlloyDB database objects. DBeaver has extensive support for various AlloyDB metadata types, allowing you to interact with a wide variety of database objects, such as:

  • Databases
    • Schemas
      • Data types
      • Tables
        • Columns
        • Constraints
        • Indexes
        • Foreign Keys
        • Dependencies
        • References
        • Partitions
        • Triggers
        • Rules
        • Policies
      • Foreign Tables
      • Views
      • Materialized Views
      • Functions
      • Sequences
      • Data types
      • Aggregate functions
    • Event Triggers
    • Extensions
    • Storage
      • Tablespaces
    • Roles

  • Administer

    • Jobs
    • Session Manager
    • Lock Manager

AlloyDB additional features in DBeaver

DBeaver provides additional features compatible with AlloyDB, but not exclusive to it:

Category Feature
Data Transfer Data Import
Data Export
Session Management Session Manager
Lock Management Lock Manager
Backup and Restore How to Backup/Restore data
Schema Management Schema Compare
Data Visualization GIS Guide
ERD Guide
Query Execution plan
0 Comments
Posts pagination