DBeaver vs. Oracle Enterprise Manager

Great tool for developers to use to dive into their databases. Not so great if you are a die-hard Windows user with expectations of a SQL Management studio replacement. This is the less suited tool for people looking to just view and edit data. If you need to generate any scripts or import and export data, this is the tool to use.

Incentivized

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.

Incentivized

• Identify types of DB connections by color code: development, testing and production.
• Predictive typing, it is incredibly accurate and saves me a lot of time.
• Jump between different simultaneous DB connections.
• Navigate through the schema object tree.
• Provide all the tools I need in one window.

• 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.

Incentivized

• No support for NoSQL databases.
• The interface could be confusing for first-time users.
• No support for multiple queries in one editor.

Incentivized

• 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.

Incentivized

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.

Incentivized

Not a lot of users have DBeaver so fewer resources are available online to help you if you have any issues. When I was trying to figure out how to create my own ER diagrams, it was a little tough to find resources

Incentivized

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.

Incentivized

We found that sharing scripts and generating DDLs from Snowflake's IDE was a bit too much of a chore. Because of this, we began looking for alternate products. We found DBeaver, a free community tool, and tried it out. We've found that it is very intuitive and easy to use, I would recommend it.

Incentivized

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.

Incentivized

• Positive Ability to manage DBeaver and query ad-hoc quickly
• By having the queries saved it has saved developer time and thereby increased the ROI on the investment on the tool
• This has made firefighting quicker and freed up resources for more development work.

Incentivized

• 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.

Incentivized