If you want to test DBeaver features, you can create a demo database. There is a specialized database that can be created. You can create a sample SQLite database at the first launch. The database can be added at any time by the following sequence. Chinook is used as a reference database

Help -> Create Sample Base

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

Databases supporting schema comparison

———————–	———————–
Cockroach	Oracle
Databricks	PostgreSQL
DB2	Redshift
Derby	SAP HANA
EnterpriseDB	Snowflake
Firebird	SQLite
Greenplum	SQLServer
Informix	Teradata
MySQL/MariaDB	Vertica
Netezza	YugabyteDB
DB2i

How it works

You can compare two schema/database structures and generate a report in the following formats:

• DDL script (series of create/alter/drop statements)
• Diff diagram (sort of ER diagram)
• Liquibase changelog

• Liquibase change report (JSON, YAML, or plaintext)

What is possible to compare

In most cases, you can compare schemas, databases, or tables. However, some databases (such as SQLite and Firebird) do not have catalogs and schemes that can be compared. In this case (and only for these databases), it is possible to compare the entire datasources.

Usually, you can compare the following database objects: columns, primary keys, foreign keys, indexes, and so on (it depends on your database). If you want to compare more objects, such as check constraints, procedures, functions, triggers, you need to enable Liquibase PRO.

How to use schema compare

Step1. Select two entities to compare

1. Select the two objects (schemas, databases, or tables) you want to compare in the Database Navigator.
2. Open the context menu.
3. Open the sub-menu Compare/Migrate and click the Compare/Migrate Schema. You’ll see the comparison window.

Step 2. Check the selected entities

Re-validate that you have chosen the correct objects to compare. You can change target and source containers by clicking the Swap sources.

Note: You must select only those schemas/directories/containers that contain tables:

• Schemas – if the database supports schemas.
• Databases – if the database supports catalogs and does not support schemas.

• Datasources – if there is no support for schemas or catalogs.

If everything is correct, click Next. You’ll see the comparison settings.

Step 3. Specify compare settings

1. If you want to export the comparison result in a file, select Export result to the file option, then specify the folder and file name. You can use variables in the file name. Click on the field with a file name to see a list of available variables.

2. Select the report format in the Report Engine field.

3. You can simply exclude specific types of objects from comparison.
   For example, it is possible not to show sequences, views, or external keys in the final comparison result.

4. You can also specify which changes should be processed: create, drop, or alter. By default, all kinds of changes are enabled. If you do not want to compare objects with equal names but in different cases (like “test” and “TesT”), enable the Case insensitive compare. (Note: This settings section is unavailable for the generation changelog process.)

Tip: You can export the results of a schema compare operation to a remote file system via Cloud Storage using the Browser remote file system button . This feature is exclusively available to users of the Ultimate Edition, Team Edition, and CloudBeaver versions.

Step 4. Look at the comparison results and save the report

Click Proceed to generate a diff report.

Step 4. Comparison results

By default, DDL diff is generated. It contains a series of creating, altering, and/or dropping statements that will modify the schema on the right side. Thus, it will make it identical to the schema on the left side.

This comparison interface provides a suite of options to manage your results effectively:

Button/Option	Description
All	Enables all changes in the changes tree on the left side of the diff page.
None	Disables all changes in the changes tree on the left side of the diff page.
Refresh Report	Updates the comparison report to reflect any changes made to the selection or schema.
Show log	For detailed information about logs, refer to the section Compare logs.
Export	Exports the current diff report to a .txt file.
Save	Saves the current state of the report.
Copy	Copies the generated SQL or report text to the clipboard for easy pasting elsewhere.
Open in Editor	Opens the current diff report in the SQL Editor for further editing or review.
Migrate	Executes the generated SQL statements on the target database, applying all selected changes.

Quote objects names in the report

For the objects in the report to be dressed in quotation marks, select the

option in Preferences.

Compare logs

To get acquainted with the comparison logs, you first specify the logging level on the Preferences-> Editors-> Schema Compare preference page. Specify one of the logging levels and click on Apply. By default, the logging level is the OFF level. To get complete information, you can choose the DEBUG level.

After comparing operations, click the

button. A log will be open in the Editor, and the content of this log will depend on the logging level you choose in the settings. Log level changes from preferences will not be applied to the comparison wizard if it is already open in another window. Close and open the schema compare wizard in this case.

Liquibase Changelog generation

Suppose you want to create a report about the objects in your table container (similar to the metadata dump operation). In that case, you can select in the navigator tree on your container Compare/Migrate -> Liquibase changelog command.

One or several table containers can be chosen. The report will contain creation statements of tables/views/keys/sequences – metadata from the table containers. But without data from tables/views. You can use this report in the future to restore the structure of your database.

Save operation as a task

If you plan to constantly use the comparison or generation changelog/schema comparison, exporting the result as a file, you can save this as a task. The task can be completed anytime and put on the schedule.

Also, generating a changelog or schema comparison can be part of the composite task. For example, if you keep the log as a script with a certain name, then the implementation of this script can be set by the second operation of the composite task.

Using schema compare with Liquibase PRO key

With a Liquibase Pro key, you can unlock advanced schema comparison features in DBeaver, including support for functions, procedures, and extended Pro objects.

For steps to set up Liquibase, see the Liquibase setup guide.

Overview

Templates let you quickly insert commonly used SQL statements into an SQL script.

To view available templates, press Ctrl+Alt+SPACE (⌃+⌥+SPACE on macOS) or right-click within the script panel and select SQL Template from the context menu. A list of available templates will appear:

To apply a template in the SQL Editor, in the script pane:

• Type the template name and press Tab.
• Right-click where you want to insert a template, select SQL Template from the context menu, and double-click the template name from the list.
  The SQL statement will be inserted into the script.

To edit, add, or remove templates, click the Configure icon in the bottom toolbar, then go to Preferences -> SQL Editor -> Templates.

Tip: For more information on managing templates, see Eclipse documentation.

Standard Eclipse templates

Variable	Description
${cursor}	Specifies the cursor position when the template edit mode is left. This is useful when the cursor should jump to a different place than to the end of the template upon leaving the template edit mode.
${year}	Takes the current year value.
${date}	Takes the current date value.
${time}	Takes the current time value.
${dollar}	Takes the dollar sign $. Alternatively, two dollar signs can be used: $$.
${user}	Takes the user name.
${word_selection}	Takes the content of the current text selection.
${line_selection}	Takes content of all currently selected lines.

DBeaver specific templates

Variable	Description
${schema}	Takes the current schema name.
${catalog}	Takes the catalog name.
${table}	Takes the current table name (from the active catalog/schema).
${column}	Takes the column name (from the current table).

Overview

SQL Terminal allows you to display the results of executed SQL queries in a text-based format within the SQL Editor.

SQL Terminal

To open the SQL Terminal, press the corresponding button on the SQL Editor toolbar.

Note: The toolbar is customizable. See Toolbar customization article.

In the SQL Terminal, you can view the result set, including data, errors, and statistical information along with the text of the executed query.

Context menu

A context menu is available by right-clicking within the SQL Terminal area. This menu provides quick access to various commands.

Command	Description
Copy	Copies the selected text to the clipboard.
Select All	Selects all text in the SQL Terminal.
Toggle Word Wrap	Toggles wrapping of long lines of text.
Find/Replace…	Opens the find/replace dialog.
Clear	Clears the contents of the SQL Terminal.

Preferences

To configure SQL Terminal settings, go to Window -> Preferences -> Editors -> SQL Editor -> SQL Terminal.

Setting	Description
Use SQL Terminal by default	SQL Terminal will open for every new script.
Show query text	Displays the text of the executed query in the terminal.
Show server output	Shows output messages from the server in the terminal.

Overview

Sometimes the database cannot be accessed directly, in such cases you can use the SSH tunnel. The SSH or Secure Shell is a network communication protocol that allows two computers to communicate and encrypts the shared data.

DBeaver supports the following SSH authentication methods:

• Username/password
• Public key authentication
• Agent authentication

Available agent authentication implementations:

• pageant (Windows only)
• ssh-agent

Note: You have to run the agent first before connecting to the database in DBeaver.

Configuring SSH Tunnels

SSH can either be configured individually for each connection in Connection settings -> SSH or as a network profile which can be selected from the drop-down menu on the same page mentioned earlier:

In order to use SSH, you have to enable it first. After that, configure it for your needs, then click on Test tunnel configuration to test whether all parameters are valid or not.

It is often required to set the hostname to

in Connection settings -> Main. SSH establishes a connection between two machines, authenticating each side to the other, and passing commands and output back and forth. After connecting to remote machine, all commands you execute are executed on that remote machine, so by having the host set to you are opening a connection to the database on this remote machine, not on your local machine, and just redirect I/O to the latter.

Configuring Jump servers

DBeaver allows the use of Jump servers, also known as Gateway hosts. This feature is essential when the direct access to a target machine is not possible from your local machine, and a gateway server is required for connection.

To add a jump server:

1. Ensure Use SSH Tunnel is checked.
2. Expand the Jump servers group.
3. Specify your target in the Settings section.
4. Click on the Create new jump host button to add your first jump server configuration.

Repeat step 3 for each additional jump host you need to add, configuring each one within the Settings section.

Practical use

Imagine you have the following situation: your database is located on remote machine with IP address

and which is accessible through SSH. You cannot access this IP directly from your machine because of your network settings or firewall, but you can access other machines with the IP address through SSH and which is able to access the desired remote machine. You will need to specify as a host in regular SSH configuration and as a host in a gateway configuration to achieve such a “connection order”: → → .

Advanced settings

Setting	Description
Implementation	Specifies the SSH library used for the connection.
Bypass host verification	If checked, disables verification of the server’s identity by not checking the remote host’s fingerprint, which may lead to security risks such as Man-In-The-Middle attacks.
Share this tunnel with other connections	If checked, allows multiple connections to share the same SSH tunnel. This can improve connection speed and reduce server load. Sessions remain open until all connections using the tunnel are closed, even if the initiating connection is terminated.
Keep-Alive interval (ms)	Sets the interval in milliseconds for sending a keep-alive packet to keep the connection active. A value of 0 disables keep-alive packets.
Tunnel connect timeout (ms)	Sets the maximum time in milliseconds to establish a tunnel connection before timing out.

Port Forwarding

Port forwarding is used to expose a socket sitting on a remote port to your local port, allowing you to communicate with it. After the SSH connection to the remote machine is established, you need to connect to the database on that machine. You must pass the port on which the database is listening from that remote machine to your local machine. This is when port forwarding becomes handy.

By default, it randomly chooses the local port and forwards it to the destination port set in Connection settings -> Main

It is not usually required to change this configuration, but it can be useful, for example, when you want to use a particular local port.

SSH and URL based connections

By default DBeaver opens random local port and forwards it to a target database port. It then implicitly replaces port configured in the connection with this random port.
So technically DBeaver will connect to something like

(random port on localhost) instead of (default PostgreSQL server port).
But if you use URL instead of manual connection configuration then you connect to . DBeaver cannot replace port number automatically because you can use any type of sophisticated URLs. DBeaver just don’t know how to change this URL.

If you use URL connection then you must configure port forwarding manually. In the Advanced Settings set both Local Port and Remote Port to 5432 (database server port, 5432 is the default value for PostgreSQL). It will work in most cases.
But it will fail if you have PostgreSQL server on your local machine because port 5432 is already occupied. In this case you can use any random port number for Loca Port (e.g. 15432). Use the same 5432 for Remote Port because it is real port number for remote PostgreSQL server.

SSH shared tunnels

By default, DBeaver shares SSH tunnels across connections when the same SSH settings are used. This is particularly useful when connecting to several databases on the same remote server, as it avoids the need to establish a separate SSH tunnel for each connection.

To view the active SSH tunnels and the databases utilizing a shared tunnel, use the SSH tunnel explorer. This feature provides a comprehensive overview of your SSH tunnel usage, including detailed information on each tunnel and the databases it serves. Here is how to access SSH tunnel explorer:

1. Navigate to Window -> Show View -> Other…
2. In the window that appears, expand the Database category.
3. Select SSH tunnel explorer and click Open.

In the SSH tunnel explorer view, you will find information about each active tunnel. This includes:

Field	Description
Destination	The remote server to which the tunnel connects.
Used by	A list of databases that are currently using the tunnel.
Port Forwards	The local and remote ports involved in the tunneling process.

SSH tunnel sharing criteria

DBeaver shares SSH tunnels across connections if SSH settings are identical. The application compares the following parameters to determine if the SSH settings match:

• Hostname: The address of the SSH server.
• Host port: The port number used for the SSH connection.
• Username: The username required for SSH authentication.

Depending on the authentication method selected, DBeaver also compares:

• For password authentication:
  • Password: The SSH account password.
• For public key authentication:
  • Private Key: The file path to the SSH private key.
  • Passphrase: The passphrase for decrypting the private key, if set.
• For agent authentication:
  • Agents: DBeaver treats all agent authentication configurations as identical, ignoring specific agent settings and focusing only on the method’s selection.

Overview

DBeaver supports the ability to establish connections using Secure Socket Layer (SSL), a protocol for creating authenticated and encrypted links between networked computers.

Note: SSL parameters are optional and should only be specified if required by your server configuration.

Setting up SSL configuration

To set up SSL, you need to configure the following settings:

1. Navigate to the SSL tab within the Connection settings.

2. Enable the Use SSL option to activate SSL for your connection.

   

3. Enter the necessary SSL configuration details (optional):

   Parameter	Description
   CA Certificate	Path to the Certificate Authority (CA) certificate.
   Client Certificate	Path to the client’s public key certificate.
   Client Private Key	Path to the client’s private key.
   Keystore	Path to the keystore file.
   Keystore Password	Password for the keystore.
   Certificate hostname	Expected hostname in the certificate.
   SSL Mode	Desired security level for SSL.
   SSL Factory	Provide SSLSocketFactory factory class name.
   Cipher suites (optional)	Specific cipher suites to use.
   Skip host name validation	Whether to bypass hostname validation.
   Use self signed certificate (non-secure)	Acceptance of self-signed certificates.
   Force TLS 1.2	Enforce using TLS version 1.2.
   Verify server certificate	Ensures the server certificate is valid.
   Allow public key retrieval	Allows the retrieval of the server’s public key.

   Note: The availability of these parameters can vary depending on the database. Check the SSL tab for your database within the Connection settings for any specific options.

4. If all other necessary connection settings are configured, complete the setup by clicking Finish, or test the configuration by clicking Test Connection to ensure that SSL is functioning correctly.

Setting up SSL configuration via Driver properties

For some databases, an alternative method to configure SSL settings is available through the Driver properties tab. This approach allows access to additional or driver-specific SSL options that may not be present in the main SSL tab:

1. Select the Driver properties tab within the Connection settings.

   

2. Look for properties prefixed with

   ssl
   , such as
   sslResponseTime
   ,
   sslfactoryarg
   ,
   sslhostnameverifier
   , etc. Configure the necessary properties according to your database and server requirements.

3. If all other necessary connection settings are configured, complete the setup by clicking Finish, or test the configuration by clicking Test Connection to ensure that SSL is functioning correctly.

Import SSL certificates on startup

DBeaver can import certificates from a predefined folder at startup. This method is useful for databases protected by self-signed certificates. It ensures secure connections without manual setup, especially when a firewall or internal security policies require specific certificates.

To add a certificate, place the file in the

folder. DBeaver will detect and import it on startup. For more details on location, see Workspace location

Note: Only certificates are imported, not private keys.

Setting up SSL configuration for Oracle connections

Prerequisites:

• Oracle Client installed.
• An Oracle Database Server that supports SSL.
• Access rights to create directories and files.
• A valid SSL certificate from a trusted CA.
• Oracle Wallet Manager for wallet management.

To set up SSL configuration for Oracle connections, follow these steps:

1) Create a Wallet Folder:

First, you need to create a directory that will serve as a wallet folder. This wallet stores your security credentials. Execute the following command to create this folder:

mkdir /opt/oracle/wallet

2) Generate Key:

Use the

utility to create a new wallet and generate a self-signed certificate. Create the wallet:

$ORACLE_HOME/bin/orapki wallet create -wallet /opt/oracle/wallet -pwd YourWalletPassword -auto_login

Replace

with a secure password for accessing the wallet.

3) Add a self-signed certificate to the wallet:

When setting up your Oracle wallet, you may need to add a certificate. There are two main scenarios for this:

1. Creating and adding a self-signed certificate: If you do not have a certificate, you can create a self-signed certificate and add it to your wallet using the following command:

$ORACLE_HOME/bin/orapki wallet add -wallet /opt/oracle/wallet -pwd YourWalletPassword -dn "CN=example.com" -keysize 1024 -self_signed -validity 365

2. Adding a certificate signed by a certificate authority (CA): If you use a certificate signed by a Certificate Authority (CA), you need to add the Root Certificate Authority (RootCA) certificate to your wallet as well. This is done using the following command:

$ORACLE_HOME/bin/orapki wallet add -wallet /opt/oracle/wallet -pwd YourWalletPassword -trusted_cert -cert path_to_root_ca_cert

Replace the following placeholders:

: Use the same wallet password as before.
: Replace this with your server’s fully qualified domain name (FQDN) or the hostname.
: This is the actual path to your certificate file:

4) Generate JKS File:

Convert the wallet to Java Keystore format.

$ORACLE_HOME/bin/orapki wallet pkcs12_to_jks -wallet /opt/oracle/wallet -pwd YourWalletPassword -jksKeyStoreLoc /opt/oracle/wallet/oracle_keystore.jks -jksKeyStorepwd YourJKSPassword -jksTrustStoreLoc /opt/oracle/wallet/oracle_truststore.jks -jksTrustStorepwd YourJKSPassword

Replace the following placeholders:

: Use the same wallet password as before. : This is a new password for the Java Keystore files. Choose a secure password.

5) Modify configuration files for SSL in Oracle

: Configure the listener to recognize SSL connections. For instance:

SSL_CLIENT_AUTHENTICATION = FALSE



WALLET_LOCATION =

   (SOURCE =

    (METHOD = FILE)

    (METHOD_DATA =

     (DIRECTORY = /opt/oracle/wallet)

   )

  )



LISTENER =

(DESCRIPTION_LIST =

   (DESCRIPTION=

    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))

    (ADDRESS = (PROTOCOL = TCP)(HOST = 0.0.0.0)(PORT = 1521))

   )

  (DESCRIPTION=

     (ADDRESS = (PROTOCOL = TCPS)(HOST = 0.0.0.0)(PORT = 2484))

   )

)



DEDICATED_THROUGH_BROKER_LISTENER=ON

DIAG_ADR_ENABLED = off

: Configure SSL parameters and wallet location. Example:

WALLET_LOCATION =

   (SOURCE =

     (METHOD = FILE)

     (METHOD_DATA =

       (DIRECTORY = /opt/oracle/wallet)

     )

   )



SQLNET.AUTHENTICATION_SERVICES = (TCPS,NTS,BEQ)

SSL_CLIENT_AUTHENTICATION = FALSE

SSL_CIPHER_SUITES = (SSL_RSA_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA)

: Defines connection aliases. Example:

SSL=

(DESCRIPTION=

  (ADDRESS = (PROTOCOL = TCPS)(HOST = 0.0.0.0)(PORT = 2484))

  (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = XE)

  )

)



XE=

 (DESCRIPTION=

 (ADDRESS = (PROTOCOL = TCP)(HOST = 0.0.0.0)(PORT = 1521))

 (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = XE)

  )

)

Replace placeholders like

, , and with your actual server , port, and .

6) Restart listener To apply the changes made to the

file, you need to restart the Oracle listener. Use the following commands:

$ORACLE_HOME/bin/lsnrctl stop

$ORACLE_HOME/bin/lsnrctl start

7) Restart Oracle database.

After updating the SSL configuration, restart the Oracle Database to ensure all settings are applied:

$ORACLE_HOME/bin/sqlplus / as sysdba

shutdown

startup

This sequence shuts down the database and then starts it up again.

Tip: If your Oracle Database runs in a Docker container, you can restart the container to apply the configuration changes –

docker restart oracle_container_name

. Replace

oracle_container_name

with the name of your Oracle Docker container.

8) Open DBeaver and initiate the process to create a new database connection. If unsure how to start, refer to the article on creating a connection.

9) Specify the Custom JDBC URL:

In the Main tab, construct the JDBC URL using the SSL configuration.

Example:

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=0.0.0.0)(PORT=2484))(CONNECT_DATA=(SERVICE_NAME=XE)))

Replace

, , and with your actual server’s hostname/IP, SSL port, and service name as specified in your .

10) Move to the Driver properties tab within the connection setup and fill in the following properties:

: Enter the password for your truststore. This property secures access to the truststore.

: Set this to to indicate the type of your truststore.

: Provide the location of your Oracle wallet. This is the directory path where your wallet is stored, as specified in your configuration files.

11) After configuring all these properties, you can test the connection to verify that the SSL setup is correct and that you can successfully connect to your Oracle database over SSL.

Troubleshooting SSL issues

If you encounter a

error, it may be due to incorrect SSL configurations. A common resolution is to consider ignoring host name validation, an option available for some databases in the SSL tab of the Connection settings, which can help bypass common SSL errors.

To format an SQL text, select it and press Ctrl+Shift+F or right-click the selected text and click Format -> Format SQL on the context menu.

To format a script to upper or lower case, highlight the SQL text, then right-click it and click Format -> To Upper Case / To Lower Case, respectively, on the context menu.

To comment out an SQL line, press Ctrl+/ or right-click the line and click Format -> Toggle Line Comment on the context menu. To uncomment a commented line, manually remove the commenting syntax, or press the same button combination, or right-click the line and click the same item on the context menu.

To comment out a block of text, select the text, then press Ctrl+Shift+/ or right-click it and click Format -> Toggle Block Comment on the context menu. To uncomment a commented block of text, you can either manually remove the commenting syntax or select the same block of text, right-click it and click the same item on the context menu or press the same button combination.

To trim spaces (leading and trailing) SQL text right-click the selected text or end of string and click Format -> Trim spaces on the context menu.

You can choose a part of the text

or put the cursor at the end of the row you want to trim

You will get the following result:

Or you can choose a part of the text from many lines

Then each of the selected rows will trim, and the final result will be like this:

Overview

DBeaver provides the functionality to automatically generate SQL scripts, streamlining your SQL scripting process. This feature is accessible from two main areas within the application: the Data Editor and the Database Navigator.

Generate SQL Scripts

From Data Editor

You can automatically generate SQL statements based on the selected database object in the Data Editor. To do this:

1. Right-click on the selected database object.

2. Click Generate SQL.

3. Choose one of the SQL commands from the context menu that appears.

4. The generated SQL statement will appear in a new window for you to review and copy.

From Database Navigator

You can also generate SQL scripts directly from the Database Navigator. To do this:

1. Right-click on a database object in the Database Navigator.

2. Navigate to Generate SQL.

3. Choose the type of SQL statement you want to generate.

4. The generated SQL statement will appear in a new window for you to review and copy.

Additional Settings

In the opened window, you have options to further customize your generated SQL script.

Option	Description
Use the fully qualified names	Includes [schema name].[table name] in table references.
Compact SQL	Condenses SQL script into a single line.
Separate foreign keys	Isolates foreign key definitions in the script.
Exclude auto-generated columns	Omits automatically generated columns from the script.
Use custom data/time format	Customizes date and time formats in the script.
Show comments	Adds comments to the script for readability.
Show permissions	Includes permission settings in the script.
Show full DDL	Adds a comprehensive Data Definition Language section to the script.
Show partitions DDL	Incorporates partitioning information into the DDL section of the script.
Use explicit type cast	Adds explicit type casting for SQL values in the script.
Add CAST to parameters definition	Adds explicit data type conversion to parameter definitions in the script.

Note: The availability of these settings may vary depending on the database you are using.

Read Data in SQL Console

DBeaver streamlines your database navigation tasks with its capability to automatically generate and execute

statements. This functionality is especially useful when you are working in the Database Navigator.

To read data in SQL Console:

1. Navigate to the Database Navigator and identify the database object you want to read.
2. Right-click on the chosen database object.
3. Select Read data in SQL console.
4. A SQL console opens, executing the query and fetching all relevant rows.

Save Your Scripts

DBeaver offers two methods for saving the SQL queries you’ve executed:

• Save As: Accessible through the SQL console‘s context menu, this option allows you to save the SQL query after specifying a file name.

• Save as Script: Also found in the SQL console‘s context menu, this function saves the query immediately as a numbered script, without prompting you for a file name.

Tip: Pressing Ctrl+S will transform the SQL console into a SQL editor, enabling more extensive modifications.

Overview

For Oracle database users, DBeaver supports script execution through Oracle SQL Plus.

To use this feature:

• Ensure SQL Plus is installed on your system and properly configured to connect to your Oracle database. For more details on configuring SQL Plus, see official Oracle documentation.
• Configure your Oracle database connection.

• Ensure your local client configuration is correct to avoid connection issues. For more information on a Local client, see Local client configuration.

Executing scripts

1. In the Database Navigator, select a schema within your Oracle database.
2. Right-click to open the context menu and choose Tools -> Execute in SQL Plus.
3. A wizard opens, prompting you to select the path to your script.
4. After selecting your script, click Start and wait for the script execution to complete.