We use cookies to ensure that we give you the best experience on our website. However you can change your cookie settings at any time in your browser settings. Please find our cookie policy here ↗
Please see the release notes for a detailed list of changes.
The collection of client-side commands has been extended with the new @import, @mail, and @open commands that allows importing table data, sending emails, and opening files in native tools from SQL scripts executed in the SQL Commander in the DbVisualizer UI and in the dbviscmd command-line interface. Client-side commands is a DbVisualizer extension allowing database independent processing in SQL scripts executed in the DbVisualizer UI and the dbviscmd command-line interface. A popular example is the @export command which is used to save result sets from SQL queries to file. With the addition of the new @mail command, SQL scripts processed in DbVisualizer can now both extract data and mail them without needing to setup external command files.
The new @import client-side command used to import files into tables is now available for execution in SQL scripts and then also in the command-line interface, dbviscmd. It supports importing CSV, Excel, and fixed width text files.
@import on; @import set ImportSource="fruits.csv"; @import parse; @import target Table="fruits"; @import execute; @import off;More details in the users guide for @import - Importing data.
The new @mail
command allows sending emails from SQL scripts executed in the SQL Commander
in the DbVisualizer UI and in the dbviscmd command-line interface. Client-side commands
is a DbVisualizer extension allowing database independent processing in
the DbVisualizer UI and the dbviscmd command-line interface. A popular example is
the @export command which is used to save the result set from any SQL query to file. With the addition
of the @mail command, scripts can run solely in DbVisualizer to both extract results from
queries and the mail them.
In the DbVisualizer UI, it is possible to define a mail server account that collects
information about a mail server and user credentials. This persists encrypted between DbVisualizer sessions.
The named account can then easily be referred in
SQL scripts only requiring basic information about to whom the email should be sent,
subject, body text, files, etc.
More details in the users guide for @mail - Send emails and attach files.
The @mail command supports a lot of customizations such as templates, statistics from the latest run, etc. The following example will send the content of a csv file as part of the body and addition it will be attached as a file. As with normal mail, multiple files can be attached or embedded in the body section.
The new @open client-side is really as it sounds, it opens the file specified as parameter in the associated native tool. For html files a web browser is opened, for xlsx files a spreadsheet tool such as Microsoft Excel is opened.
The new SQL formatter preview makes it a lot easier to see the impact of the various formatting settings.
SQL formats can now be saved in named SQL formatting profiles that can be used for all database connection associated with a specific database type (Oracle, MariaDB, Exasol, etc) or for individual database connections.
The Morph Selection with Dialog in the SQL editor allows the user to
convert a selection of text into a delimited list with the appropriate options.
More details in the users guide for: Morph Selection.
The export grid and open as spreadsheet commands has previously operated on the result set as fetched from the data source. Any grid sorting, filtering or rearranged columns was not considered in these functions. The new and default Export Visible and Open Visible as Spreadsheet actions now consider the visual appearance in the grid make it a lot more versatile. The old behavior is still available.
The annoying step of having to manually adjust column widths to fit the content in a newly exported xlsx is now elimated.
The database tab object filtering is a powerful tool to limit what objects should be displayed in the Databases tab. This version finally improves the content of the Database and Schema drop-downs in the SQL Commander to adjust automatically without needing to reconnect when a filter is applied or cleared in the Databases tab.
Having several hundreds of database connections defined in DbVisualizer is not very common albeit
those setups exists. The Edit Database Connections action in the Databases right-click
menu has been around for several years and enables editing common database connection settings
in a single run. The new version makes it easier to scope the database connections for
edit and is available in the improved Connections overview (the top node in the Databases tab).
It allows sorting and filtering making it a lot easier to select the database connections that should be included.
The very same tool is now also displayed for Folder objects which is also a level of filtering as it
will only show all Database Connections stored in that folder.
The new dbviscmd command-line setup generator makes it really easy creating the command-line for dbviscmd, either freely or by using the editor content in the SQL Commander along with current parameter settings as a base. Just click Copy and paste on the command-line to run the command-line interface for DbVisualizer.
Prompting of variables and parameters markers has been added in the command-line interface, dbviscmd. dbviscmd supports the exact same variable and parameter marker syntax, i.e. SQL scripts as the DbVisualizer UI does. Data types are prompted with default recommendation if applicable.
Support for the new @mail command in scripts. @mail will send result sets generated by SQL queries (or any file) by email as either embedded text or attached files. There are many options including a template engine which allows setting up custom emails easy.
The database profile framework in DbVisualizer is a used to define the characteristics of a supported database with database specific functionality that exceeds what JDBC offers. With this release we have added the capability to build dashboards presenting various database metrics as charts. Currently available only for Exasol.
To see all changes in DbVisualizer 11.0, please see the Release Notes.