DBeaver Documentation

Command Line

Command line parameters

Command line parameters might be passed directly to dbeaver[.exe] executable.
In Windows you can also use dbeaver-cli.exe executable (it does not spawn a new window so you can see the output messages).

Also, you can add parameters in the dbeaver.ini configuration file - in the beginning of the file and each parameter on its own line.

DBeaver control

-helpPrints help message
-stopQuits DBeaver
-dumpPrints DBeaver thread dump
-fOpens file in DBeaver UI-f c:\some-path\some-file.sql
-conOpens database connection in DBeaver UISee connection parameters table
-closeTabsCloses all open editor tabs
-disconnectAllCloses all open connections
-reuseWorkspaceForce reuse of single workspace by multiple DBeaver instances
-newInstanceForce new DBeaver instance creation (do not try to reuse already running one)
-var Custom variables for runTask. You can change existing variables in the task. You cannot add new task variables with this parameter. You can add several parameters at once to the command line, each starting with "-var". Used right before -runTask. Template: "-var variableName=variableValue"-var film=sakila.film
-var actor=sakila.actor
-runTask "exportFromSakila"
EE version only.
-runTask Executes specified task-runTask "@projectName:taskName".
EE version only. See task scheduler.
-license Path to the EE license file-license "/etc/licenses/dbeaver.txt".
EE version only.

System parameters

-dataWorkspace pathc:\ProgramData\MyWorkspace
-nosplashOmits splash screentrue
-cleanClears all Eclipse caches. Use it if DBeaver fails to start after a version upgrade.
-vmargsVM parametersSee VM arguments table

VM arguments

You can pass any advanced Java parameters supported by your local JVM (Oracle, OpenJDK, IBM, etc).
Parameters supported by Oracle JVM (11): https://docs.oracle.com/en/java/javase/11/tools/java.html

Parameters supported by all JVMs:

-XmsSets initial memory available for DBeaver-Xmx1000m
-XmxSets maximum memory available for DBeaver-Xmx4000m

Connection parameters

All connection parameters must be supplied as a single command line argument, parameters are divided by pipe (|). Parameter name and value are divided by =.
Example: -con driver=sqlite|database=C:\db\SQLite\Chinook.db|name=SQLiteChin|openConsole=true|folder=SQLite

nameConnection nameTest connection
driverDriver name or IDdriver=sqlite, driver=mysql, etc
urlConnection URL. Optional (JDBC URL may be constructed by driver from other parameters)url=jdbc:sqlite:C:\db\SQLite\Chinook.db
hostDatabase host name (optional)host=localhost
portDatabase port number (optional)port=1534
serverDatabase server name (optional)server=myserver
databaseDatabase name or path (optional)database=db-name
userUser name (optional)user=root
passwordUser password (optional)password=mysecret
authAuthentication model ID. See Auth models auth=postgres_pgpass
authProp.propNameCustom authentication parameters (depends on driver and auth model)authProp.oracle.net.wallet_location=C:/temp/ora-wallet
savePasswordDo not ask user for a password on connectionsavePassword=true
showSystemObjectsShow/hide system schemas, tables ,etcshowSystemObjects=true
showUtilityObjectsShow/hide utility schemas, tables ,etcshowUtilityObjects=true
folderPut new connection in a folderfolder=FolderName
autoCommitSets connection auto commit flag (default value depends on driver)autoCommit=true
prop.propNameAdvanced connection parameters (depend on driver)prop.connectTimeout=30
idConnection idoracle_thin-16a88e815bd-70598e648cedd28c (useful in conjunction with create=false)
connectConnect to this databaseconnect=false
openConsoleOpen SQL console for this database (sets connect to true)openConsole=true
createCreate new connectioncreate=false (true by default). If set to false then an existing connection configuration will be used. The name or id parameter must be specified.