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

Tableau is a leading data visualization and analytics platform that empowers you to connect, visualize, and share data in a way that makes it easier to understand. With its intuitive drag-and-drop interface, Tableau enables users to create interactive and shareable dashboards, providing insights into complex data sets.

Having a registered Tableau account is a prerequisite for those looking to leverage Tableau’s capabilities. This article explores how DBeaver integrates with Tableau, enhancing the data manipulation process.

DBeaver’s integration is compatible with both the On-premise and Cloud versions of Tableau, offering the following key features:

DBeaver’s integration with Tableau allows you to connect effortlessly to databases already present in Tableau. This seamless connection enables you to access and manage data without complex configurations or additional tools. Learn more about creating a connection.

A standout feature of DBeaver’s integration with Tableau is the ability to edit custom SQL queries stored in Tableau. You can modify these queries directly within DBeaver, providing a streamlined workflow for advanced data analysis. Learn more about editing custom SQL queries.

In addition to database management and query editing, DBeaver allows for the integration and manipulation of Tableau charts directly within its interface. Learn more about managing dashboards.

To configure Tableau credentials in DBeaver, follow these steps:

1. Navigate to Window -> Preferences -> General -> Tableau.

2. In the Tableau settings, you will find the following options:

Option	Description
Enable Tableau Integration	Enables Tableau in connections and in UI.
Tableau Profile	Manage Tableau profiles. User profiles are displayed here, and you can work with them using the buttons: – Add profile – Remove profile – Edit profile
Test Connection	Test the connection between DBeaver and Tableau.
Automatically associate Tableau connections	Automatically associate Tableau connections with DBeaver data sources. Learn more about associate connection.

When you click on Add Profile, a Create new Tableau profile window will appear. This is how you fill out the profile:

After filling out the profile details, you can test the connection to Tableau to ensure that everything is set up correctly. This step verifies that the provided information is accurate and that DBeaver can successfully communicate with Tableau.

Important: Before creating a connection in DBeaver, a connection must already be configured in Tableau. More details can be found in the official Tableau documentation.

Creating a connection between DBeaver and Tableau is a straightforward process:

1. In the DBeaver toolbar, click on the Show View (Tableau) button . The Tableau view will open in the lower part of DBeaver, displaying your profiles.

2. In your profile, select the desired database, right-click, and choose Create Database Connection.

3. DBeaver will prompt you to name the connection, and it will appear in the Database Navigator.

The Associate with connection button allows you to view a list of databases that can be associated with Tableau in DBeaver. It can automatically find the database based on the hosts.

Tip: If the Automatically associate Tableau connections option is selected in the preferences, clicking on a table will automatically open it in DBeaver.

To configure the database that is associated with Tableau, you can use the Open Tableau connections option or double-click the database in Tableau view. A window with connections that are associated with Tableau will appear. From this window, you can choose to Link database connection, Unlink connection, or Edit connection as needed.

Working with custom SQL queries in Tableau can be challenging, especially when it comes to complex data manipulation. DBeaver’s integration with Tableau offers a solution, allowing you to edit and manage custom SQL queries with ease. By connecting Tableau to DBeaver, you can leverage DBeaver’s robust SQL editing tools to enhance your data analysis workflow in Tableau.

Important: The custom SQL query must already be configured in Tableau. More details can be found in the official Tableau documentation.

This is how you can edit custom SQL queries using DBeaver:

1. In the Tableau view in DBeaver, select the Custom SQL query in your profile. You can double-click it, right-click and choose Open Custom SQL, or press the shortcut F4.

2. The SQL Editor will open, where you can work with the query just like any other query in DBeaver. You can make necessary changes, utilize grouping, filters, and other functionalities, and save and execute the query to see the changes reflected in Tableau.

Note: It is essential to save the query in DBeaver to ensure that the changes are also reflected and saved in Tableau.

This integration simplifies the process of working with custom SQL queries in Tableau, making it more efficient and user-friendly.

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

The task is a saved configuration of a database tool. It can be started from the task management view or from the menu by a single click. You can create tasks for frequently used tools.

You can save the tool configuration into a task and run your task later with a single click. For example, you can start the Data Transfer wizard and configure the data export from several tables in the SQLite database into CSV files:

Click on the

Now click on the

You can configure the Database Tasks View to see more or fewer View columns. Right-click inside the Database Tasks tab and choose the

Also, you can create a new task from the main menu

From the task view, you can add, edit, remove, and execute saved tasks. You can use the context menu or view tools for these actions.

The process of editing a task is similar to the process of creating a task.

By clicking on Edit or double-clicking on a task, the task edit wizard will be opened. In this wizard, you can:

• Change the task properties.
• Change the file format, either output for an export task or input for an import task.
• Alter the set of objects for data transfer.
• Adjust any export/import configuration.

After modifying the task settings, click the Save task button. This button is located on the left side of the task configuration wizard.

You can create a task from scratch using the tasks view. Open tasks view and click on the

For better structuring, you can store your tasks in the folders. Create folder can also be from the context menu Database Tasks View.

You can choose a project for the new task folder and add a new unique name.

You can change the task folder for an existing task in the task Edit dialog (use button

The task folder as a task can be deleted with the button

The Session Manager in DBeaver provides you with control and visibility into your sessions, allowing you to terminate, disconnect, view and search for sessions, as well as perform several other actions.

• Altibase
• AlloyDB
• Db2 for LUW
• Exasol
• Fujitsu Enterprise Postgres
• Greenplum
• MariaDB
• MongoDB
• MySQL
• MySQL on Google Cloud
• Netezza
• Oracle
• PostgreSQL
• PostgreSQL on Google Cloud
• Redshift
• Microsoft SQL Server

• Microsoft SQL Server on Google Cloud

To open the Session Manager:

1) In the Database Navigator, navigate to your desired database.

2) Go to the Administer section.

3) Double-click on Session Manager or right-click and select View Session Manager.

Once you have opened the Session Manager, you will have access to a variety of functionalities based on your database type. To access these functionalities, you must right-click on the desired session, or select the session and use the buttons in the bottom toolbar of the Editor. Here is a rundown of the buttons and their functionalities:

Button	Image	Description
Kill Session		Terminates the selected session forcefully.
Disconnect Session		Disconnects the selected session from the server.
Show Active/All Connections		Toggles between displaying only the active sessions and all sessions in your database.
Show Background		Reveals background processes that are running in the session.
Show Inactive		Shows the sessions that are currently inactive in your database.
Refresh		Updates the session list to reflect the current state of the database.
Configure Auto-Refresh		Allows you to set up automatic refreshing of the session list.
SQL Script		Calls a SQL script that will display sessions in a table format.

Here is a complete list of default hotkeys in DBeaver UI for Windows, Linux, and macOS users. It will help you work in DBeaver faster and more efficiently. Remember that you can always change the keyboard shortcut in the DBeaver settings. Go through: Window -> Preferences -> User Interface -> Keys. Select command and add a keyboard shortcut to the Binding row.

If you mostly use keyboard, to get more shortcuts you can switch default key scheme to DBeaver Keyboard Only key scheme in Window -> Preferences -> User Interface -> Keys settings.

See ER Diagrams documentation for a list of shortcuts.

Important: The shortcuts Alt+1 through Alt+6 are only effective in the DBeaver Keyboard Scheme.

The Database Navigator in DBeaver displays various database objects by default, including system objects, schemas, tables, indexes, utilities, and more.

To customize or simplify the Database Navigator’s contents, you may choose from three view modes:

• Simple: This mode offers a streamlined view, ideal for users who primarily interact with tables.
• Advanced: This mode provides a comprehensive view of all database objects that DBeaver can manage.
• Custom: This mode allows for a personalized configuration of the Database Navigator display.

To access these settings:

1. Right-click on the desired database within the Database Navigator.
2. Select Connection view.
3. Choose between Simple, Advanced, or Custom to suit your preferences.

For the Custom view:

1. After selecting Custom, an additional window will appear.
2. In this window, you can configure the custom settings for the Database Navigator view.

Important: Changing the view modes settings affects the currently selected database. To customize the display of objects in each database individually, you must select a specific view mode for each one.

Each view mode offers a unique set of features:

• Simple View: Tailored for ease of use, the Simple view offers a minimalist approach, displaying only schemas and tables. It is optimal for users who focus predominantly on these database objects.

• Advanced View: The Advanced view presents a comprehensive display of the database, showing all database objects, including system objects, all folders, and all supported objects. This mode is intended for users who require visibility across the entire database structure.

• Custom View: For those who prefer a personalized setup, the Custom view mode provides the ability to configure the Database Navigator.

Following is a detailed comparison of the features across the different view modes, along with descriptions for the configurable options available in the Custom View:

In addition to selecting a view mode, there are other settings accessible via the Connection view context menu. These settings provide additional information about the database objects and enhance your experience:

Setting	Description
Show connection host name	Displays the host name or tunnel of the current database next to the connection name.
Show objects description	Shows object (table, column, etc.) description next to it.
Show statistics info	Provides statistical information on objects (e.g. table size), on the right side of the Database Navigator.
Show action icons	Shows action icons for database elements. For example, you can see a read-only icon on the right side of the Database Navigator, indicating that a particular connection is in a read-only state.

These settings can be toggled on or off based on your preference, allowing for a customized Database Navigator. To access and modify these settings:

1. Right-click on the desired database within the Database Navigator.
2. Navigate to the relevant options.
3. Select or deselect the options to show or hide the desired information.

Note: These settings alter the display for the entire Database Navigator, affecting how all database objects are presented.

For install dbeaver-ce snap package with stable release (stable by default):

## Connect interfaces:



You can find list of all _dbeaver-ce_ snap connections:



```snap connections dbeaver-ce```



And connect what you need. For example:



```snap connect dbeaver-ce:ssh-keys``` for access to private keys



Or you can do it in Ubuntu Software (dbeaver-ce - Permissions):



![image](https://user-images.githubusercontent.com/46003534/172124852-bee2766f-fcee-4deb-9cab-7d132dc02aae.png)





  

### Problems with dbeaver-ce snap package:



At the moment there is a well-known problem with opening the browser and gis maps via _dbeaver-ce_ snap package. Application crashes with an error:



`SWT WebKitGDBus: error creating DBus server Error binding to address (GUnixSocketAddress): Permission denied`

`SWT WebKit: error initializing DBus server, dBusServer == 0`





Snapcraft forum topic: https://forum.snapcraft.io/t/classic-confinement-for-dbeaver-ce/27502



  

### Workaround



While the problem is being fixed, you can use the **workaround**:



Run _dbeaver-ce_ snap package from: ```/snap/dbeaver-ce/current/usr/share/dbeaver-ce/dbeaver```

You can save scripts to a predefined space in the currently active project or somewhere in the file system.

To save a script to the current project space, just press Ctrl+S or right-click the script and click Save on the context menu:

You can find the script saved this way in the Project Explorer view in the Scripts folder.

To save a script to the file system, right-click the script, click File -> Export SQL script on the context menu and then select the folder in the file system. You can also click SQL Editor -> Export SQL script on the main menu:

Unsaved data is highlighted in color on the left side of the editor, in addition to having an asterisk in the name of the script.

To load a script stored in the file system to the SQL Editor, press CTRL+SHIFT+O, or click SQL Editor -> Import SQL script on the main menu, or right-click the script panel and click File -> Import SQL script on the context menu:

To rename a script, right-click anywhere in the script panel, click File -> Rename SQL Script on the context menu or press CTRL+F2:

Then enter the new name in the Rename SQL script dialog box and click OK:

If you want to revert all changes made to the current SQL script and return it to its initial state (reload from disk), right-click anywhere in the script panel and click File -> Revert on the context menu.

By default all of the scripts are saved to a “Scripts” folder located in your project inside the workspace directory. This can be changed by clicking the Configure button in Project Explorer view. There you can click on a folder’s name an pick any other folder inside the Project.

You can also link an external directory to your project to either save your scripts into it, or to access scripts that were created outside of DBeaver.
To link an External directory right-click anywhere in the Project Explorer and pick Create -> Link Folder. There you can link any directory on your drive to a project. This will allow you to open any externally created scripts through Project explorer and to set this folder as default to save new scripts into.

In some cases you might want to execute a query and not save it in a script. For example, when you read table data using “Read data in SQL console” or open procedure/function source from DDL editor. SQL console does not have an associated .sql file. Its contents will be lost when you close it.

To use search, click the Search button on the main toolbar:

Please see the dedicated articles for information about searching for different types. This article describes common features of the three search types.

Search results for any of the search types appear in a separate Search view. The following image shows the Search view for the database full text search:

The view contains a toolbar that provides common tools for all types of search as well as specific tools for the File Search type. The following are common tools:

Button	Name	Description
	Run the Current Search Again	Refreshes the search results
/	Cancel Current Search	– Active state (red) indicates that the search is still in progress and appears if the search takes some time to complete. Clicking the button in this state stops the current search. – Inactive state (grey) indicates that the search is complete. The button in this state is non-actionable.
	Show Previous Searches	– Clicking the button itself opens the Previous Searches window. – Clicking the arrow next to the button opens a dropdown menu. See the Search History section further in this article.
	Pin the Search View	Ties the current search results to the Search view. If you click this button, the current results stay in the view while the results of the next search appear in a new Search view. Otherwise, every new search replaces the previous results with new results.

For information about specific tools of File search, see the File Search article.

If the search is short, the results appear almost instantly. But if it takes some time, the Search view indicates the progress in the following ways:

• The Cancel Current Search button in the toolbar has the Active state ()
• The progress bar appears in the bottom-right corner of the view indicating the process:
• The button to show the search progress in a separate view () appears in the bottom-right corner of the view next to the search progress bar. Clicking the button opens the Background Tasks view:

DBeaver stores the history of search queries made during the current session. You can reopen the Search view with results of a previous search query. You can also remove individual queries and clear the history. To manage the search history, use the Show Previous Searches button in the toolbar ().
To open the results of a previous search query, do one of the following:

• Click the arrow next to the Show Previous Searches button in the toolbar and then click the query in the dropdown list:

  

• Click the Show Previous Searches button itself or the arrow next to it and then History on the dropdown menu to open the Previous Searches window. Then, in the window, click the query and then either click Open to open it in the active Search view or click Open in New to open it in a new view:

  

To remove one or more of the previous search queries:

1. Click the Show Previous Searches button in the toolbar or click the arrow next to it and then History on the dropdown menu. The Previous Searches window opens.
2. Click the query to remove or select several of them by clicking and simultaneously holding the Ctrl key.
3. Click Remove.

To clear the history by removing all previous queries, click the arrow next to the Show Previous Searches button on the toolbar and then click Clear History on the dropdown menu.

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

The level of security is one of the key questions for enterprises, and the DBeaver team pays a lot of attention to it. One of the best reasons to use PRO versions is to take advantage of its security tools and features, such as password protection, SSO authentication, teams and roles in Team Edition.

This article briefly describes the most important security options available in DBeaver PRO.

You can enhance security in DBeaver with the Master Password, which encrypts credentials and sensitive data using a secure storage system. This feature ensures that each user’s credentials are individually protected by their own Master Password, tying the encryption specifically to their local environment.

For more details, refer to the Managing Master Password article.

Users can change the current database password directly in DBeaver in the following databases:

• Cockroach
• Exasol
• Greenplum
• Netezza
• Oracle
• PostgreSQL
• Redshift
• Snowflake
• SQL Server
• Vertica.

Oracle, PostgreSQL, and Netezza allow changing an expired password in DBeaver as well.

• How to change the user password

You can protect all Projects in your local workspace with a Master password.

You can set this password and store it in DBeaver password provider or use a generated password from your local password provider (for instance, OS X Keystore Integration or Windows integration provider).

Learn more about the Master password for Projects

You can specify a password for any project to protect all the project’s configurations.

Learn more about project password

You can connect to databases using secure authentication via Kerberos or GCP, AWS, and Azure cloud services.

Kerberos is an authentication protocol, the default authentication technology used in Microsoft Windows.

You can connect via Kerberos using keytab, kinit, or a password. Open the connection settings, choose one of the supported databases and select Kerberos as the authentication method.

Learn more about authentication via Kerberos

Users can connect to all company services using only one login and password. This is possible if you use SSO – Single Sign-On authentication service.

You do not need to manage, store, and transfer user credentials. When a user connects to the database, DBeaver opens a web browser with SSO authentication.

DBeaver supports the following SSO authentication services:

• AWS SSO
• GCP SSO

• Azure

You can describe all available database connections in configuration files (in JSON format) or import from CSV or XML DBeaver.

If you want to restrict users from editing connection parameters, you can protect them with passwords.

You can customize users preferences before they run DBeaver. For example, you can set the default simple mode for all connections (to show only schemas and tables and hide all system and service objects).

How to manage preferences

The best way to manage user access, restrictions, and permissions is to use Team Edition.

Team Edition allows you to create users and assign them appropriate roles with predefined capabilities.

You can add Viewers and Editors to work with prepared data, Managers to prepare data for them, Developers to work with scripts and connections, and administrators to manage everything.

If your team works on Microsoft Windows, you can organize DBeaver mass updates in silent mode, without user input, using the Windows Installer command line options.

Learn more about silent install

You can place the license file in the user’s workspace or store it elsewhere, and specify the license path on the command line or in the DBeaver configuration file.

• Learn more about lisense management automation
• How to specify license path in config