DbVisualizer
Open-knowledge reference entry
DbVisualizer is a multi-platform database tool, founded in 2003 by DbVis Software AB, based in Stockholm, Sweden. It is a database management tool that connects to databases via a standardized protocol. The software connects to many relational and NoSQL database systems through JDBC. It runs on the Java Virtual Machine and works on Windows, macOS, and Linux. It is partly built on open-source technologies.
History
Roger Bjärevall, the founder of DbVisualizer, started working on it in 1998. He released the first public version 1.0 in 1999. The tool received positive user feedback and high engagement, which led to the launch of DbVisualizer Pro in 2002, followed by the establishment of DbVis Software in 2003.
DbVis Software is currently led by Martin Engdahl, former director at Salesforce Sweden. In April 2020, Industrifonden and Fairpoint Capital invested €5.3 million in DbVis Software.
Features
DbVisualizer has the following features:
SQL Editor: Autocompletion, Syntax highlighting, Query formatting
Database Object Navigation & Editing: Browse, view, and manage database objects like tables, schemas, etc
Integrated AI Assistant: Optional access to external AI models via a simple chat interface for asking questions, writing and analyzing SQL, exploring schemas, and explaining errors
Version control with Git: Integrated version control for scripts and connections using Git repositories such as GitHub
Advanced Query Tools: Administrative capabilities for query analysis
Import/Export: Facilitates data migration with built-in tools
Command-Line Integration: Automation and Scripted Operations
Supported Databases and Platforms
DbVisualizer works on Windows, Linux and macOS with identical functionality.
“DbVisualizer” enters the record as open-knowledge reference entry. Crown Archives preserves that source wording while asking what DbVisualizer, Open-knowledge and entry can confirm, complicate or overturn.
Why this record matters
“DbVisualizer” is worth following because a concise public description often conceals a longer documentary argument. Here, DbVisualizer, Open-knowledge and entry provides the most credible route into that argument.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Mar 16, 2026. The linked authority identifier is Q104404504. None of the 0 selected statements returned an explicit reference. The first chronological checks are 2003, 1998, 1999 and 2002.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “DbVisualizer”, its source revision and the description used here.
- Expand the search: follow DbVisualizer primary sources, DbVisualizer archive and DbVisualizer research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “DbVisualizer”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “DbVisualizer” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.