Dbvi going strong since 20 years.
Use Cases and Deployment Scope
We use dbvis to test database connections during the installation of our product on customers' servers. This lets us verify that a connection is not 'lost' on the way to the database. As we use JDBC as our primary connection method, DBIS provides an easy, additional, and independent way to test the connection. We use dbvis to check stored data, review table structures and metadata (e.g., when selects or inserts fail), and verify table permissions for the user who is having connection issues. We love the in-cell data editing feature, which is much easier than building SQL queries for every entry. This also allows a quick manual review of the stored data, even with large tables, and fixes the most obvious errors instantly. We test, build, and also 'deconstruct' SQL queries when there is a need to check on long-running queries. This helps us identify, for example, misused indices and other issues. We use it to easily export complete tables and data for a wide variety of DBMS for our customers and ourselves. It helps us visualize relationships and identify faults that are often not obvious within our codebase.
Pros
- Easy visualize Db-data.
- Connect to a wide range of Dbms.
- Ease of data manipulation.
- Managing a great number of different Db-connections.
- Work with big queries.
Cons
- Support for troubleshooting on a Dbms level.
- Automatically suggest syntax differences with different Dbms.
- Sharing of Db connections.
- Startup time.
Likelihood to Recommend
DbVis is our tool of choice when we need to work with a wide variety of Db vendors and versions. It allows us to replace several proprietary tools for accessing and, in part, managing database systems. It gives our customers and us a single base to work on databases. No need for us or them to install, learn, and pay for multiple solutions. If one would, for example, use ONLY one dbms, e.g., PostgreSQL, then DBVis could be a bit of an overkill.
