Skip to content

Configuring DbVisualizer

You set most settings in Tool Properties. Some settings are set elsewhere, depending on what they apply to.

Tool Properties

Your own settings, such as how grids look and how SQL is executed, are in Tools → Tool Properties. They are saved in the current workspace, so each workspace can have its own settings. For an overview of the categories, see Tool Properties.

Connection properties

Settings for a database type, such as Oracle or PostgreSQL, are in the Database tab of Tool Properties. You can override them for a single connection in the Properties tab of the connection. See Configuring Connection Properties.

Java VM options

Options for the Java VM that runs DbVisualizer, such as the maximum memory or the certificates to trust, are set in the Java VM Properties section of the General category in Tool Properties. They apply to all your workspaces, and you must restart DbVisualizer for them to take effect. See Java VM options.

Settings for all users

Administrators can set some settings for all users of an installation in the dbvis-custom.prefs file, in the resources folder of the installation folder. Its values are read when DbVisualizer starts, and override the defaults. Some of them, such as the audit log settings, can then not be changed in Tool Properties.

On macOS, changing a file inside the application breaks its code signature. Instead, create the dbvis-custom.prefs file in /Library/Application Support/DbVisualizer for all users, or in ~/Library/Application Support/DbVisualizer for your own user account. The file for all users overrides the one in the application, which overrides the one for your user account.

The following settings are described in other pages:

Command-line arguments

When you start DbVisualizer from a script, you can choose a workspace, open a connection or a script, and set the Java VM options using command-line arguments and environment variables. See Starting the GUI from the Command Line (dbvisgui).