DbVisualizer Screenshots

Supported Databases
DbVisualizer supports all major databases and JDBC drivers. Please check the following pages for up-to-date details about currently supported versions:

DbVisualizer is tested with an extensive collection of database products and JDBC drivers. Some of these databases are used more than others in the industry and so we have added support for database specific features in DbVisualizer. Some of these features are:

  • Management of database specific objects
  • Visual actions such as Create, Alter, Drop, Rename and so on
  • Create, Edit and Compile procedures, functions and triggers
  • Explain plan support
  • ...and much more

 

The database browser for an Oracle database

The database browser for a SQL Server database

The database browser for an Informix database

The database browser for a DB2 for LUW database
 

Database browser when connected in the generic mode


Database Connection
DbVisualizer is based on the JDBC toolkit and there are JDBC drivers for almost every database that is available on the market. DbVisualizer supports connecting to local, remote and embedded (Java based) databases and connection management is flexible with options to setup a connection via the Connection Wizard or by manually defining the connection data.
 
Defining a database connection is a simple task using the Connection Wizard in DbVisualizer. In the wizard choose what database you are connecting to, information about the JDBC driver and finally the details about the database server and user credentials. An option to the wizard is to setup the connection manually via conventional JDBC steps such as defining the JDBC URL.
Connection Wizard

JDBC Driver Manager

Connection Details

Connection Details with Variables
 

Extra JDBC Driver Properties

Qualify Object Names properties


Database Browser
The database browser is used to navigate the objects in the database. What types of objects that appear is database specific. Click an object in the objects tree to see more details about it in the object view.
 
The database browser in DbVisualizer is the place where you navigate the structure of objects available in the database server. The information in the tree depends on what database is being accessed.
Database Browser when connected to a Oracle DB
Every object (node) in the tree have an accompanying right click menu with actions specifically for that object. What actions that are available depends on the object type but are typically used to create, alter, rename and remove objects for that type.
Right click menu actions for a table in Oracle
You may search the database based on object names
Database Search
When selecting an object in the Database Browser, you will see a number of tabs in the left object details pane. What is displayed here depends on what database you are accessing and what object being selected.
Table Object Details


Table

Table objects are the most central objects in any RDBMS. DbVisualizer include support to visually create, alter, drop and rename tables while each of the supported databases adds even more database specific actions for table objects.

 
The Create Table feature is used to specify the definition of a database table in terms of columns, keys, indexes, foreign keys, constraints, etc. This screenshot show the Columns information.
Create Table
Specify foreign keys to other tables
Define Foreign Keys
The alter table feature enable visual editing of the table structure. This screenshot show the SQL Preview. This is the SQL that DbVisulizer will run when Execute is pressed.
Alter Table with SQL Preview

Create Index


Procedure, Function, Package and Trigger
DbVisualizer include support for PL (procedural language) objects such as procedure, function, package and triggers. This can be visually create, edited and compiled (when appropriate).
 
This screenshot show the action used to create a stored procedure in a SQL Server database.
Create Procedure
Click a procedure in the database browser and the procedure editor is activated in the object details pane.
Edit Procedure
The Create Trigger lets you visually define a new trigger
Create Trigger


Export Database/Schema
The Export Schema/Database feature is used to export the DDL for objects such as table, view, procedure, function, trigger, package and package body to a file.
(This is available for Oracle, DB2 for LUW, Mimer, PostgreSQL, Sybase ASE, SQL Server, MySQL, JavaDB/Derby and Informix)
 
The target destination can be any of file, clipboard or a SQL Commander editor. Either export all objects or a selection.
Export Database


References Graphs
References between tables can be graphed based on a single table or all/selected tables in a schema or database. The layout is automatically rendered for optimal appearance.
 
The references graph is a great feature as it automatically render all primary/foreign key mappings (also called referential integrity constraints) in a graph style. The layout of the table nodes and relations are done automatically with any of the layout modes that are available. The presented graph is unique as it displays all information in an optimal and readable layout. This screenshot shows the references for a specific table.
References for a single Table
The references graph is a great feature as it automatically render all primary/foreign key mappings (also called referential integrity constraints) in a graph style. The layout of the table nodes and relations are done automatically with any of the layout modes that are available. The presented graph is unique as it displays all information in an optimal and readable layout. This screenshot shows the references for a specific table.
References for Multiple Tables


Table Data Editor
Create tables using the table assistant and edit table data in the inline or the form based data editors. The Data Import feature is used to import CSV files into database tables.
 
Table objects are the core of any database and DbVisualizer have great support for managing table definitions and table data. Table data can be edited via the spreadsheet like editor or via the form editor, it supports management of binary/BLOB and CLOB data as well as interoperability with files in the file system.
Table Data
The inline data editor is a spreadsheet-like editor. Just open a table and modify the data you want. Modified cells are indicated to represent the type of edit. You may paste information into a multi row/cell selection and the pasted data will update the corresponding cells. Once you're ready all changes are propagated in the database table in a single transaction. In addition you may sort one or several columns, filter the data being presented and a lot more.
Inline Data Editor
The form data editor is useful when editing a row that is either composed of many columns and/or some fields contain much data. The data for a row is presented in a form with the column name to the left and the actual data in the right area. To launch the form editor either select Edit in Form or double click the row header. The form editor is also used to visualize binary data such as images, XML, etc.
Form Data Editor


Table Data Import
The Import Table Data feature is used to import files containing data organized as rows of columns with separator characters between them.
 
There are a number of options to control what data should be imported.
Data Delimiters
Data types are automatically recognized when the file is loaded. To change this click the first row cell and choose the appropriate type from the list.
Data Type Setup
Data types are automatically recognized when the file is loaded. To change this click the first row cell and choose the appropriate type from the list.
Import Column Mapping


Data Navigator
The navigator is used to follow foreign keys by data. Want to know what employees that works in "DEPT_ID = 56"? The navigator is all about this.
 
The navigator starts at the current table. The diagram at the top show the checked tables and their relationships. The lower grid show the actual data that is referred by the primary/foreign key mappings. Select the data in the grid and what constraint to follow in the "Related Table" drop down and the navigator will render the referenced table in the diagram. The linked data is displayed in the grid. You may jump back and forward by selecting table nodes in the tree. Nodes may be tagged with information from the table data to make it easier recognizing them.
The Table Data Navigator


SQL Editor
The SQL Commander supports multiple editors and result sets, bookmark feature, formatting, script execution and extensive customization. Result sets can be edited, viewed in text or chart format. Explain plan can be executed for Oracle, DB2 for LUW and SQL Server
 
The SQL Editor supports auto completion which is an aid used to complete sentences with either table or column names. Specify the beginning of a table name and then press Ctrl+SPACE to show a list of matching names. The screenshot show 3 select statements and their respective result as grid tabs in the lower part.
SQL Editor with Auto Completion and result sets in Grid format
A result set displayed with the Text output format.
Execution of selected SQL with result set in fixed width Text format
Any result set may be presented as a chart. There are numerous options to control the appearance.
Result set in Chart format
The data in a result set may be edited via the inline or form editors. Certaint conditions must apply in order for edit to be enabled.
Edit result set either inline or in the form editor


Query Builder
The Query Builder provides and easy way to develop database queries. The query builder uses a point and click interface and does not require in-depth knowledge about the SQL syntax. The generated SQL may be configured to use the standardized JOIN syntax or WHERE conditions, delimited identifiers and qualifiers.
 
The query builder is a very useful feature used to build SQL select statements graphically. Pick tables in the database browser and drag them into the query builder diagram area. Then draw lines between columns in one table node and attach to columns in another table node. These lines represent the joins in the generated SQL. The tabs below the diagram area are used to specify any COLUMNS, WHERE, ORDER BY and GROUP BY clauses.
Table Diagram and Join Properties
In addition to the previous screenshot the query builder supports loading an existing SQL statement so that it can be edited in the query builder.
Column Select list
Once you are satisfied with the query, just pass it on to the SQL Commander for test execution. If you need to make any refinements just switch to the query builder and continue editing the query.
Generated and test SQL


Explain Plan
 
The explain plan feature presents detailed information about how a specific SELECT statement will be processed by the database. The plan data gives a lot information and is a great tool improving select statements so that they perform at the best. This screenshot show the plan data in a multi column list. The explain plan feature is supported for Oracle, DB2 for LUW and SQL Server.
Explain Plan result as list
The explain plan feature presents detailed information about how a specific SELECT statement will be processed by the database. The plan data gives a lot information and is a great tool improving select statements so that they perform at the best. This screenshot show the plan data in a tree. The explain plan feature is supported for Oracle, DB2 for LUW and SQL Server.
Explain Plan result as tree


SQL Bookmarks
The bookmark feature is primarily used to organize and save commonly used SQL statements so that these are accessible for future use. The boomark feature is also tracking every SQL that is executed in the SQL Commander so that you may walk back and forth in the history.
 
The bookmark feature is used to save and organize SQL statements that are executed frequently. SQL Bookmarks are saved between DbVisualizer sessions.
Bookmark Editor


Monitor & Charts
The monitor feature is used to execute any select statement at specified interval and present the result in grid, text or charts. Perfect for real time monitoring of the database.
 
The monitor tool is used to periodically execute select statements and present the result in various formats. The chart format is really useful as it in combination with the monitor feature can present a number of live charts based on actual data.
The Monitor Tool


Grid Component
The Grid component is a very central component in DbVisualizer and it includes depending on context a lot of convenient features that are highlighted below.
 
Here are two columns, "Type (DB)" and "Size" sorted in ascending order. To sort one column just click the column header, one click will sort the column in ascendinging, click again and it will be sorted in reverse order, a third click will reset to the original ordering. To sort more than one column, keep the Ctrl key (Command on Mac OS X) pressed while clicking the column headers. <br> The screenshot also show filtering of the "Name" column. All matches in the grid are highlighted with yellow color.
Grid with multi column sorting and filtering
The right click menu lists all actions that may be performed on the grid and its data. Note that some actions are context sensitive and may be disabled.
Grid right click menu choices
The "Browse Row in Window" action shows the selected row in a separate window. The data is presented in a form with the left most column in the original grid being presented at the top. <br> The form window is also a grid with the same capabilities as the grid component.
Row Form Window
Sometimes it is convenient to select some data and perform various calculations on it such as telling max, min, avg, sum, etc. The right click menu choice "Calculate Selection" is used for this.
Data Calculations
 
The export functionality is used to export the content of any grid to a file. The output can be written in CSV, XML, MS Excel or as SQL INSERT format. Data formats can be specified and fake test data can be generated with the builtin data generators. The export functionality can also be used in the SQL Commander, this is typically used when exporting large result sets directly to file without first presenting them in DbVisualizer.
The Export feature


Command Line
DbVisualizer supports a number of command line options used to start DbVisualizer without the GUI ever being displayed, opening a SQL file, run it and then finally quit.
 
Passing command line options to the DbVisualizer executable makes it possible to create new database connection, connect (or an existing one), load SQL file and run it.
Command Line options


OS Integration
DbVisualizer integrates seamless with the supported operating systems, Windows, Mac OS X and Linux/UNIX. Key bindings are configurable and the appearance of the application is highly customizable.
 
DbVisualizer runs smoothly on the Windows platform, here with the Windows look and feel
DbVisualizer on Windows
DbVisualizer on Mac OS X with the Aqua look and feel
DbVisualizer on Mac OS X
DbVisualizer on Linux with the Alloy cross platform look and feel
Cross Platform Look and Feel
DbVisualizer on Linux with the Java cross platform look and feel
Cross Platform Look and Feel


Configurable
DbVisualizer is highly configurable. Settings can be defined on the application level or per database connection. All settings are saved between invocations.
 
The key binding support in DbVisualizer is extensive as it supports setting key bindings for lots of operations. There are pre-defined key maps specifically for Windows, Linux/UNIX and Mac OS X users. This is really important for key bindings such as those used for editing since these key strokes are different in each OS. In addition there are key maps for users coming from other database tools such as TOAD and SQL Server's Query Analyzer.
Key Binding setup
There are many settings used to control the appearance and behavior of DbVisualizer. One great feature is to set connection mode for a database connection. It can be set to one of Development (default), Test or Production. Depending on what mode is set a border will indicate in DbVisualizer what mode it is. For production systems it is severe if executing SQLs that are aimed for a test system. The connection mode is also used in combination with the permission subsystem to control what commands need attention, are accepted or are denied for execution.
Connection mode
The grid colors can be defined so that every second row is presented in an alternate color.
Grid colors
The permission feature simply controls every action and SQL that are about to be executed. For SQLs that are executed in the SQL Commander the permission is set per individual SQLs such as DELETE, DROP, UPDATE, etc. The response can be any of "Allow", "Ask" or "Deny". Permissions are also available when editing in the table data editor. Permissions can be defined for Insert, Update or Delete operations. The response for each command is any of "Confirm" or "No Confirm". Permissions are grouped based on the connection modes, "Development", "Test" and "Production".
Permission control setup