Skip to content Skip to sidebar Skip to footer

Data And Sql Script Files Are Missing While Using Wbexport In Command Line

I am facing one issue while running a sql script which contains WbExport (using Select statement) from command line. The txt file and import sql script is missing from the destinat

Solution 1:

This has been cross posted to the SQL Workbench/J support group

The problem is that the new Microsoft JDBC driver treats parameters to some JDBC API calls incorrectly and does not support wildcards any more. SQL Workbench/J escapes standard SQL wildcard characters before calling e.g. DatabaseMetaData.getColumns(). Apparently the Microsoft JDBC driver starting with version 7.4 does not use a LIKE statement anymore and thus the method call (using escaped wildcards) does not return anything.

Escaping wildcard characters can be disabled inside SQL Workbench/J by setting a configuration property. Either by editing workbench.settings manually and adding:

workbench.microsoft_sql_server.metadata.retrieval.wildcards=false

Before editing the file, make sure SQL Workbench/J is closed.


This can also be configured without restaring the application.

When being connected to a SQL Server database, this can also be done from within SQL Workbench/J by running the following Workbench command:

WbSetDBconfig metadata.retrieval.wildcards=false;

Post a Comment for "Data And Sql Script Files Are Missing While Using Wbexport In Command Line"