Latest build: 20100831 (August 16, 2010) View release notes

Input sample data or initial database data when design database with Entity Relationship Diagram (ERD). The generated database initialization script includes insert sample data to the database.


You can use label to group your glossary terms. One term can have multiple labels and you can filter glossary terms by label.

Grid diagram gives another perspective of your project file. You can browse your design in tabular format and configure showing which columns.
Save diagramming time by create connecting objects with multiple turning points at once.

Reference to A³ Platform's activities, issues and requirements easily. Open the referenced A³ Platform resources by just a few mouse clicks.

Every element in VP project has a unique URL. You can send the URL to your colleagues to locate the target elements easily.

View sub-project diagrams in the master project without switching project back and forth.

Automatic copy reference project model elements to current project. All model element members and properties will be copied at the same time.

Reuse Visio diagram with UML diagrams by importing Visio Drawing to Stencil.

DB Visual ARCHITECT for NetBeans supports generating design blueprints to PDF files. The paper size, cover page design, TOC, page header and footer are all customizable. You may select to include/exclude diagrams and model elements, and reorder the content. There are various options to control the styles and formatting of the generated PDF. The PDF generation feature is available in Windows, Mac OSX, Linux and Unix platform.

Generate database schema (DDL) from entity relationship diagram (ERD). Both database creation and database patching script can be generated automatically. The following movie demonstrates the database generation feature.

Online training

Class diagram is the most widely used diagram in modeling object-oriented system. A class diagram shows a set of classes, interfaces, associations and generalizations. Package is commonly used model element for organizing elements in class diagram. Class diagrams are not just for visualizing and documenting structure models but also for constructing executable system with forward, reverse and round-trip engineering. There is also a synchronization engine for generating and updating entity relationship diagram from class diagram.
Online training

DB Visual ARCHITECT for NetBeans supports exporting and importing Microsoft Excel file. Excel is the best tool for mass editing of model element names and properties. You may export diagram to Excel file, edit their names and properties in tabular format, and then import the changes back to DB Visual ARCHITECT for NetBeans.

Line Jump Options:
When drawing a complex diagram with many shapes and connectors, connectors may intersect with each other. Line jump feature is design for decorating the intersection, which makes it easier to identify connection paths. DB Visual ARCHITECT for NetBeans supports arc, gap and square line jump options. The following screenshot shows all line jump options and you can try different line jump in left hand side pane.

Analysis diagram helps to identify full consequences of changes before you really make changes. Analysis diagram visualize all related model elements. You can further analyse specific model element by clicking the analyse resource icon. The following flash demo demonstrates how to use analysis diagram to do impact analysis.

DB Visual ARCHITECT for NetBeans's Report Writer is tailor made for building report from scratch, with both project data and your own written content. You can drag and drop diagrams and model elements information from diagram navigator to the report in-place, to show the content of project. Report Writer can only run on Windows platform.

Design report template with easy-to-use visual template designer. The latest version has added a lot of customizable elements and increased in usability.

Compare and generate differences between two diagrams automatically with visual diff. Identify differences between two databases by comparing two entity relationship diagrams.
Tell us what you think?