ER/Studio is a database development and management tool from Embarcadero Technologies (acquired by Idera) in California.
$2,687
per year per user
Oracle Enterprise Manager
Score 7.0 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
ER/Studio
Oracle Enterprise Manager
Editions & Modules
Standard
$2,687
per year per user
Professional
$3,693
per year per user
Enterprise
Custom
per year per user
No answers on this topic
Offerings
Pricing Offerings
ER/Studio
Oracle Enterprise Manager
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Pricing for new customers only, first year maintenance included. Maintenance includes access to technical support and product updates for the defined period of the agreement.
Data Architect is well suited at organizations of all sizes. It is never too early or unnecessary to enforce proper modelling and design standards on data solutions, and this tool will help that greatly by providing an industry leading data modelling tool, ability to import ETL mappings for data lineage, enforcing and managing naming conventions through the naming convention tool, and publishing of data dictionaries through the report publisher. I was successfully able to build models, provide traceability, and document source to target with lineage throughout for both the business (by providing business definitions in the descriptions), and technical teams (by documenting ETL instructions in text fields) along with field level mapping (by creating "Attachments" representing data sources, tables, and fields) providing easy search capabilities using business friendly terms
OEM is very well suited for all Oracle products, especially Oracle databases and Exadata machines; even not Oracle hardware, it is very good and displaying high level details. OEM is not well suited for older hardware vendors like AIX, HP-UX, DEC/Digital, Microsoft (sql server). This is a big negative as most large companies have a heterogeneous environment with many different vendor hardware and (database) software products.
ER/Studio has the ability to provide consistent field names and data types through domains, which are templates. This provides a way to have consistent naming of common fields, like CreatedBy and the data types for the fields. They also have the ability to change all the fields that use that domain to a different data type.
ER/Studio provides the ability to create custom macros. These macros can be used to apply everything from standard fields based on domains to naming all constraints and indexes. I've also used a macro that comes with ER/Studio to spell check field and table names.
My favorite feature is the ability to compare your data model to databases for deployments of changes, and to other data models.
Monitoring Templates: There are out of box monitoring templates for each target types, you can customize them or use them as it is.
Administrative Groups: This is a relatively new feature in OEM Cloud Control. This lets you create and manage your targets and monitoring templates smarter and with less re-work.
DB Monitoring: There are so many cool DB monitoring features and visual graphics, that it can be used by both DBA and functional people to see what's going on in the database.
ER\Studio licensing can be cumbersome and upgrading from one version to another usually takes several phone calls and emails to the licensing group to get the update installed and running.
The repository can be slow when the model count gets larger. By large I mean 20 to 30 models.
A nice feature that I would like to see is table comments be displayed on the model along with the attributes. Currently you have to choose between the two.
Bugs. Every version we upgrade to has a number of bugs. Some stop us from rolling to production OEM (we have a sandbox OEM), some are simply annoying. If I could improve on one thing, it would be for better QA from oracle before releasing each version.
Flash. I'm told that they are moving from Flash to Jet in version 13.3 and beyond (we are on 13.2 currently). That change cannot come soon enough. The OEM pages load SO slowly due to Flash.
Hierarchy Groups. OEM allows five Hierarchy groups. A Hierarchy group allows a top down metric/rule roll out. However, they limit you to five. I'd like to see them open that up, so that we can have any number of custom groups.
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 can call or email support and both get quick turn around. The only issue is they are on the west coast (US) and have a west coast work schedule and I'm on the East coast.
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.
Being an Oracle shop using Oracle Database and MySQL, management console from Oracle was a better choice than IBM or Microsoft even though we do use Microsoft Azure and storage/servers from IBM (on-prem).
ER/Studio has had a positive impact on my project as we can develop the data model and have a clear understanding of business needs before we continue with the development phase.
We are a 7x24 shop. Oracle Enterprise Manager Cloud Control helps us meet that objective by proactively warning us before issues cause down time. Things like disk space, archive log issues or temporary table space issues.
Spreading the use of this tool outside of the DBA group has allowed us to not hire additional personnel for those teams. Over time, as folks have retired from our operations team, we are not replacing them. Instead we have used OEM Cloud Control to automate tasks.
We also now have the tools to measure up-time by using specific measurements inside of OEM. This allows us to report real numbers to management.
