kovaleff - Fotolia

Get started Bring yourself up to speed with our introductory content.

Which database tools for testing should we choose?

Which database tools for testing should we choose? Learn about tools for testing and data analysis.

Testers need intuitive tools that query and display data in a way that's easy to view and analyze. Several tools are available and the choice depends on the testing team's personal preferences -- those and the budget, or what development tools are already in place. Investigating free tools may be worthwhile, but many are basic and don't allow for complex queries or data analysis.

SQL-based tools -- SQL server and SQL developer. SQL Server 2014 is a database tool built into Visual Studio. If the development team uses Visual Studio, the testing team could use SQL Server for database testing needs. Another tool wouldn't be needed and there would be no cost or integration concerns. SQL Server 2014 does a great deal more than a test team will ever need. However, it is easy to use and works on cloud and on-premises databases. The best part for testers: It has a query editor window that allows a tester to use saved SQL queries or create custom queries as needed. It's surprisingly easier to use than many of its competitors.

Another tool that works in a similar fashion is Oracle's SQL Developer, a free tool that's useful as a database testing tool for Oracle cloud or on-premises databases. Like SQL Server, the tool does more than a tester needs but depending on the complexity of the testing needs, it's easy to use and comes with a lot of online assistance and resources. SQL Developer offers a query editor and the ability to save SQL queries or create custom queries. Although SQL Developer is relatively easy to use, my personal preference is SQL Server even though I used SQL Developer for many years.

UI enhanced tools -- Toad, DB Visualizer and SQLlite. Toad, a database testing tool popular with many testers and developers,  offers several versions that work on nearly any database platform. Toad claims to have intuitive workflows and built-in features that are easy to use and return more accurate results. It still relies on SQL queries and offers the standard editor query tool. Although I've used it, I struggled to understand it. Toad has a large following and a lot of online support, if needed.

Another popular, more UI-based database testing tool is DbVisualizer, which offers many window-like features in auto completion, formatting and a GUI query builder. It also offers a command-line feature. DbVisualizer windows can be moved and displayed side by side. Spreadsheet enthusiasts tend to love DbVisualizer. Database viewing results can be bookmarked, formatted and customized. Query results are viewable in text or chart format. Many of my co-workers prefer DbVisualizer, but others find that the GUI features interfere more than they help.

Another option is SQLite, a visual GUI tool. It is an open source option that many testers prefer for creating, designing and executing SQL queries. As with most tools, it does much more than is needed for database testing. It is also spreadsheet-based and includes wizards and other GUI features.

Next Steps

Read more about best practices for DAM tools

Learn more about database security tools for preventing SQL injection attacks

Dig Deeper on Topics Archive

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Which database testing tools do you use?
I'm currently working with a company that uses PostGreSQL for its back end, so much of my testing is associated around the psql client and scripts that control and manipulate it.
I use Oracle Database and I use a variety of tools for database testing. They include Orion, Swingbench and HP LoadRunner. Orion is an IO subsystem testing tool from Oracle used for testing Oracle database IO workloads. Swingbench, also from Oracle, is used to test the performance of a Database. Lastly, I use Hp LoadRunner to test all system components at the same time. This tool interacts with application servers in order to test comprehensively.
My current project uses SQL Server. Hence testing majorly is done by writing scripts.
DBVisualizar and for MySQL, MySQL Workbench.
Workbench is very usefull for linux because it log in Linux using SSH and then log into MySql locally (you are already logged into Linux).
This is usefull when MySQL is installed the way it prohibit logged form outside.

As a person responsible for performance and capacity testing I use Apache JMeter to load test databases and Precise i3 for monitoring and analysis.
I do like Toad, and I've used a couple different versions of it. I still use it for MySQL. I've used it for DB2 as well, but unfortunately we had to stop using it for work purposes because of the licensing agreement. DB2 doesn't seem to have many good tools out there. 
Our project currently uses SQL Server 2014 and it is indeed useful in terms of using customized queries for testing.
Our current project uses PostGreSQL, and frankly, the psql client is very good for testing purposes. pgbench is also an included tool that allows you to benchmark your database tests, to se if your current release runs faster or slower than the previous one.
I use dbforge studio for oracle for the last 5 years as it's powerful and comprehensive Oracle IDE with many cool options. There are capabilities to boost coding speed, compare and synchronize data between different Oracle schemas, profile queries, consistent with Visual Studio and other options.
Which testing tool would you suggest for functional and integration testing of PostgreSQL ? (other than psql client)