My main use case for DbVisualizer is data analysis, but also increasingly performance monitoring and tuning of databases due to the broad support for multi vendors in the tool. A specific example of how I use DbVisualizer for performance monitoring or tuning includes monitoring the condition of indexes on tables, rebuilding them, and profiling data for looking for additional opportunities to index my data. Additionally, the built-in performance measures for query performance, while not necessarily to the degree of a dedicated solution, are often enough to provide troubleshooting of a specific performance issue with a different app interaction with a dataset.
I use this mostly for browsing databases and for certain specific monitoring processes. Like monitoring a database restore/recovery where the time SQL executions and real-time graphs are a great help estimating the time left.
I use DbVisualizer to run complex queries in many databases, including about every vendor with a relational database. Timed SQL execution and real-time graphs are the killer features. It is a multiple-platform tool, based on Java but with a native look and feel. Most colleagues initially don't believe it is entirely written in Java. For Oracle, I use it to analyze AWR data. During database restores, I use this to monitor the progression and to estimate the remaining time. The limits to its use are by imagination only.
One tool for all databases and OSes
DbVisualizer is the ultimate database tool for developers, analysts and DBAs. It runs on all major OSes and connects to all major databases.
My main use case for DbVisualizer is data analysis, but also increasingly performance monitoring and tuning of databases due to the broad support for multi vendors in the tool. A specific example of how I use DbVisualizer for performance monitoring or tuning includes monitoring the condition of indexes on tables, rebuilding them, and profiling data for looking for additional opportunities to index my data. Additionally, the built-in performance measures for query performance, while not necessarily to the degree of a dedicated solution, are often enough to provide troubleshooting of a specific performance issue with a different app interaction with a dataset.
I use this mostly for browsing databases and for certain specific monitoring processes. Like monitoring a database restore/recovery where the time SQL executions and real-time graphs are a great help estimating the time left.
I use DbVisualizer to run complex queries in many databases, including about every vendor with a relational database. Timed SQL execution and real-time graphs are the killer features. It is a multiple-platform tool, based on Java but with a native look and feel. Most colleagues initially don't believe it is entirely written in Java. For Oracle, I use it to analyze AWR data. During database restores, I use this to monitor the progression and to estimate the remaining time. The limits to its use are by imagination only.