G2

Verified User in Information Technology and Services

QA Analyst

Enterprise (> 1000 emp.)

10/1/2026

"Easy to Navigate, Efficient Query Tabs, and Handy Grid Editing"

5/5

What do you like best about DbVisualizer?

I'm a QA tester for school district software and I'm in DbVisualizer Pro pretty much every day, mostly against our PostgreSQL & MSSQL databases for our internal services and our customers. A lot of my testing depends on having the right data before I start. For example, if I'm testing a report download screen I need a print file my test login can actually see. I just poke around the tables, write a quick query (autocomplete fills in most of the table and column names) and I've got what I need in a couple of minutes. After the test I run the same query again to make sure what the app saved matches what the screen showed me.

I use the software mostly for fixing payrolls for our customers. I can easily back up and back out data, which allows me to rerun programs to repost payrolls. I have used other types of DB softwares but prefer DBVisualizer. It's easy to use and user friendly in my opinion. I haven't used it for integrations yet as I haven't needed it for that reason.

Getting started was easy. I had it connected to our servers and was running queries the first day. Between the docs and the built-in help I haven't needed to contact support.

Performance has been fine for me. I leave it open all day with a few tabs and connections and it keeps up, even with bigger result sets. I love that I can adjust the number of rows of data display to help with performance as well.

I have not used the AI features in DBVisualizer yet, not sure if I will anytime soon. I mainly use external AI features to help in my daily duties.

We pay for Pro and I think it's worth it. Stuff I used to have to ask a developer to check, I just do myself now, several times a day. Grid editing and the export options alone make it worth it over the free version for me. Review collected by and hosted on G2.com.

What do you dislike about DbVisualizer?

Slow on huge schemas. Loading the table list or the relationships view can lag on very large databases.

Dated look. It works well but looks older than some newer tools.

License cost. The Pro license can be a hard sell to a manager when there's a free edition and free alternatives. Review collected by and hosted on G2.com.

What problems is DbVisualizer solving and how is that benefiting you?

As a QA tester, I need to confirm that what the application shows matches what's actually in the database. Before DbVisualizer, that meant asking a developer to run a query for me, or testing blind and hoping the data was right. Now I can do it myself.

Finding the right test data. I can quickly find records that fit a test case, such as a user with the right permissions or a file a test login can see, instead of guessing or setting up data by trial and error.

Checking results after a test. After I run a test, I query the database to confirm the change really happened and the screen isn't just showing what I expect.

The benefit is speed and independence. I spend less time waiting on developers, my bug reports are clearer and more convincing, and I catch data problems that a UI-only test would miss. One tool connects to all our QA databases, so I'm not switching between apps. Review collected by and hosted on G2.com.