Enterprise Data Architect & Senior Manager at Health First Inc.
Real User
Top 10
2024-06-17T09:21:52Z
Jun 17, 2024
Since the solution was originally developed in the eighties and nineties and hasn't changed much since then, it could use an overhaul. The solution is not so strong at creating modeling views and database views.
Data Architect at a performing arts with 201-500 employees
Real User
Top 5
2024-05-15T12:10:46Z
May 15, 2024
The solution's reporting could be improved because the report writer is terrible. Writing definitions and not being able to generate a nice report to view is useless. To me, that's a huge problem.
It isn't easy to compare the thousands of tables in the model against the database. The tool should improve the synchronization within the large organization
With ER/Studio, the roadmap to send us new versions with the new database is slow. I think it could allow us to test and use new database versions faster. Sometimes we get new functionalities like, for example, the Collibra integration. We receive these new functionalities, and sometimes we start to test them and we find errors that we need to correct by talking with tech support. I think they allow functionalities to be released before the full tests for catching and correcting errors are completed. My other point is about the team server. We're using the web portal, and the interface is not so good. The client was modified, and we have the new version. It's good. The client is good to us, but the web portal is using the old UI. It's not as modern, and it's limited. We found that the new version is slow when compared to the older version. We are trying to investigate what component is causing the slowness, because you have the client access, the repository, the API, the team server, and the web portal. Getting a single sign-on feature is very important to us.
Sr Data Integration Modeler at a insurance company with 1,001-5,000 employees
Real User
2020-10-07T07:04:40Z
Oct 7, 2020
The model diagram because very clumsy when you save it on the team server and the models are very big. It becomes difficult to enlarge and difficult to print. Although they say that it supports concurrent users, we have issues while branching, merging, and performing check-in or check-out. It's not as seamless as it should be. Now that we are all working from home and our repository is on the cloud servers, we are experiencing issues with performance. In general, support for big data should be improved.
Data Architect at a pharma/biotech company with 1,001-5,000 employees
Real User
2020-07-13T06:56:52Z
Jul 13, 2020
The visual presentation is a little too colorful and seems that it is dumbed down. I would like to see support for creating macros in the way that erwin can. It did not reverse engineer all of the data types correctly, although it was pretty close. The only mistake was with some Oracle table objects, where it incorrectly determined them to be character references.
IDERA ER/Studio is a powerful suite for business-driven data modeling that enables companies to create an enterprise architecture foundation for data governance. With round-trip support for multiple database platforms, data architects have the power to reverse-engineer, analyze, and optimize existing databases easily from diverse platforms. Data professionals can easily capture and share models, metadata, data sources, and glossaries across the organization for improved alignment between the...
Since the solution was originally developed in the eighties and nineties and hasn't changed much since then, it could use an overhaul. The solution is not so strong at creating modeling views and database views.
The solution's reporting could be improved because the report writer is terrible. Writing definitions and not being able to generate a nice report to view is useless. To me, that's a huge problem.
It isn't easy to compare the thousands of tables in the model against the database. The tool should improve the synchronization within the large organization
With ER/Studio, the roadmap to send us new versions with the new database is slow. I think it could allow us to test and use new database versions faster. Sometimes we get new functionalities like, for example, the Collibra integration. We receive these new functionalities, and sometimes we start to test them and we find errors that we need to correct by talking with tech support. I think they allow functionalities to be released before the full tests for catching and correcting errors are completed. My other point is about the team server. We're using the web portal, and the interface is not so good. The client was modified, and we have the new version. It's good. The client is good to us, but the web portal is using the old UI. It's not as modern, and it's limited. We found that the new version is slow when compared to the older version. We are trying to investigate what component is causing the slowness, because you have the client access, the repository, the API, the team server, and the web portal. Getting a single sign-on feature is very important to us.
What needs the most improvement are semantic lineage and usability.
The model diagram because very clumsy when you save it on the team server and the models are very big. It becomes difficult to enlarge and difficult to print. Although they say that it supports concurrent users, we have issues while branching, merging, and performing check-in or check-out. It's not as seamless as it should be. Now that we are all working from home and our repository is on the cloud servers, we are experiencing issues with performance. In general, support for big data should be improved.
The visual presentation is a little too colorful and seems that it is dumbed down. I would like to see support for creating macros in the way that erwin can. It did not reverse engineer all of the data types correctly, although it was pretty close. The only mistake was with some Oracle table objects, where it incorrectly determined them to be character references.