DbVisualizer is a multi-database tool for developers, analysts and database administrators, providing a single interface across a wide variety of operating systems. Boasting an easy-to-use and clean interface, DbVisualizer runs on all major operating systems and supports all major RDBMS that are available. Users only need to learn and master one application. DbVisualizer integrates transparently with the operating system being used.
$0
Oracle Enterprise Manager
Score 7.4 out of 10
N/A
Oracle’s Enterprise Manager is an on-premises monitoring and management tool. The console is designed primarily to manage other Oracle products, it but can integrate to manage non-Oracle components as well.
N/A
Pricing
DbVisualizer
Oracle Enterprise Manager
Editions & Modules
DbVisualizer Free
$0
DbVisualizer Pro with Basic support - Renewal
$89
per year per user
DbVisualizer Pro with Premium support - Renewal
$119
per year per user
DbVisualizer Pro with Basic support
$199
per year per user
DbVisualizer Pro with Premium support
$229
per year per user
No answers on this topic
Offerings
Pricing Offerings
DbVisualizer
Oracle Enterprise Manager
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
New license cost includes a perpetual license, software upgrades and support for the length of the term. 1, 2 & 3 year terms are offered. Once license expires the user may access all Pro versions released before the license expiry indefinitely. To gain access to Pro versions released after the license expired, license renewal is offered. Volume discounts apply to both new and renewal licenses.
—
More Pricing Information
Community Pulse
DbVisualizer
Oracle Enterprise Manager
Features
DbVisualizer
Oracle Enterprise Manager
Database Development
Comparison of Database Development features of Product A and Product B
DbVisualizer
7.8
Ratings
9% below category average
Oracle Enterprise Manager
-
Ratings
Performance optimization tools
7.80 Ratings
00 Ratings
Schema maintenance
7.90 Ratings
00 Ratings
Database Administration
Comparison of Database Administration features of Product A and Product B
Well suited for medium size to large Oracle system that includes a large and complex database schema with many database objects including functions and triggers. Also well suited for a medium size to large Microsoft SQL Server system with many complex database objects. Its SQL editor and query builder are well suited in developing complex SQL queries.
I wish I had an option to give it a 9.5 :) OEM Cloud Control is very well suited if you have a system with multiple implementations of Oracle Database Enterprise Edition. If you are willing to pay for the huge license cost which is typical with Oracle, then you will love to use OEM Cloud Control to monitor your entire ERP solution including web servers, applications, network, storage, and physical servers. It is not worth the buck if your's is a small implementation. Your DBA's should be able to work without depending on OEM Cloud Control.
Oracle Enterprise Manager is a "one stop shop" for all of our management needs. This is helpful because it minimizes the management of the management software itself. There are less upgrades and connectivity issues to handle. And there are "plug-ins" for additional products we use like Blue Medora's one for PostgreSQL.
Managing administrative jobs can be burdensome in a shop with dozens of servers and databases. OEM Cloud Control makes it easy since you can view all the jobs for all servers in one place. It is easy to filter on jobs with problems or the like so that you can quickly look at the logs and fix the issues.
Tuning PL/SQL is much easier using OEM Cloud Control. Most DBAs are familiar with trace files and TKPROF, but not having to do those things at a command line smooths the process out. The graphical interface makes it easier to show developers exactly what the issues are. This makes for less finger-pointing and quicker resolution of performance problems.
Proactive management is easier using OEM Cloud Control. Before having the gui, I had a collection of scripts that I would have to install on each database server, then set up cron jobs to run them. When Oracle was upgraded, those scripts might have to be updated on each and every server. OEM Cloud Control has those things built in. You can choose exactly which metrics are important to you. And you can keep performance graphs up all day on a second monitor to let you instantly see when something might cause a problem.
does not handle lost connections well (specially after stopping a running query) (mysql). eg. after hitting stop, and then hitting run again, it can sometimes look like its running the query, but it isn't actually!
filtering on databases window is clunky (why the need for filtering certain object types at a time? just filter everything, google style)
altering table, adding columns (NOT to the end of the table's columns, but earlier) is not supported (mysql) even though the db supports it (alter table add column BEFORE..)
We also use OEM to monitor SQL Server. However, OEM only provided limited features for SQL Server. It would be nice if we can schedule backup jobs for SQL Server in OEM.
The ability to run SQL queries. You can't run queries in OEM. I have to go to SQL Developer or SQL PLUS to run. queries.
I use this tool for several hours each day, spanning many years in various projects. It's wide support for various database types while keeping consistency within the UI for each is important when working with various databases day in and day out.
It's great! It does everything and anything you would want it to do. It can monitor things which doesn't comes out of the box by adding plug ins to it, for example, you can even monitor Oracle GoldenGate Replication by adding a plug-in to OEM Cloud Control.
I still rate OEM as a must-have tool for central management of Oracle fleet. The pros and cons of the product is prominent. Meanwhile, I also acknowledge that OEM was design about a decade ago. At that time, it did not have the landscape we have today, such as cloud, DEVOPS, machine learning, etc. I hope in future releases, the design will incorporate those features.
[DbVisualizer] is pretty easy to use compared to IntelliJ because of it's simplicity. The performance is very good, it feels as good as a native application compared to the other two softwares I used for the same purpose. It's very cheaper compared to the other two tools and that's a big selling point.
Kibana from Elastic is another monitoring tool that claims to provide very similar information to OEM. It seems to be an information tool rather than a tool that can actually make changes within a database. I think Kibana is more robust for hardware versus database software so it is more suited to that purpose and does to compare to the Oracle Database monitoring attributes of OEM.
The only point I could potentially give is hours saved by having so many warehouses hooked up in one place vs. having to manage connection string changes/password updates across multiple applications... maybe 10% decrease in time spent managing connections? Mind you, I've had everything hooked up on DbVis for close to 6 years so it's hard to remember the "before times"
Positive: Alerting features. Without this we would have to be a 24x7 shop with someone always manning the helm. With the alerting feature we can define levels of alerts and only get the most pressing alerts sent out.
ROI: OEM is free, so the ROI is whatever you make of it.
