ER/Studio is a database development and management tool from Embarcadero Technologies (acquired by Idera) in California.
$1,470.40
one-time fee per user
Informatica PowerCenter (legacy)
Score 8.5 out of 10
N/A
Informatica PowerCenter was data integration technology designed to form the foundation for data integration initiatives, application migration, or analytics. It is a legacy product.
N/A
Pricing
ER/Studio Data Architect
Informatica PowerCenter (legacy)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
ER/Studio Data Architect
Informatica PowerCenter (legacy)
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
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.
—
More Pricing Information
Community Pulse
ER/Studio Data Architect
Informatica PowerCenter (legacy)
Features
ER/Studio Data Architect
Informatica PowerCenter (legacy)
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
ER/Studio Data Architect
-
Ratings
Informatica PowerCenter (legacy)
8.5
18 Ratings
2% above category average
Connect to traditional data sources
00 Ratings
9.018 Ratings
Connecto to Big Data and NoSQL
00 Ratings
8.014 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
ER/Studio Data Architect
-
Ratings
Informatica PowerCenter (legacy)
7.5
18 Ratings
9% below category average
Simple transformations
00 Ratings
8.018 Ratings
Complex transformations
00 Ratings
7.018 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
ER/Studio Data Architect
-
Ratings
Informatica PowerCenter (legacy)
8.2
18 Ratings
3% above category average
Data model creation
00 Ratings
9.015 Ratings
Metadata management
00 Ratings
8.016 Ratings
Business rules and workflow
00 Ratings
9.018 Ratings
Collaboration
00 Ratings
6.116 Ratings
Testing and debugging
00 Ratings
9.017 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
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
1.- Scenaries with poor sources of data is not recomended (Very bad ROI). The solution is for medium-big enterprises with a lot of sources of data and users. 2.- Bank and finance enviroment to integrate differente data form trading, Regulatory reports, decisions makers, fraud and financial crimes because in this kind of scenary the quality of data is the base of the business. 3.- Departments of development and test of applications in enterprises because you can design enviroments, out of the production systems, to development and test the new API's or updateds made.
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.
Informatica Powercenter is an innovative software that works with ETL-type data integration. Connectivity to almost all the database systems.
Great documentation and customer support.
It has a various solution to address data quality issues. data masking, data virtualization. It has various supporting tools or MDM, IDQ, Analyst, BigData which can be used to analyze data and correct it.
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.
There are too many ways to perform the same or similar functions which in turn makes it challenging to trace what a workflow is doing and at which point (ex. sessions can be designed as static or re-usable and the override can occur at the session or workflow, or both which can be counter productive and confusing when troubleshooting).
The power in structured design is a double edged sword. Simple tasks for a POC can become cumbersome. Ex. if you want to move some data to test a process, you first have to create your sources by importing them which means an ODBC connection or similar will need to be configured, you in turn have to develop your targets and all of the essential building blocks before being able to begin actual development. While I am on sources and targets, I think of a table definition as just that and find it counter intuitive to have to design a table as both a source and target and manage them as different objects. It would be more intuitive to have a table definition and its source/target properties defined by where you drag and drop it in the mapping.
There are no checkpoints or data viewer type functions without designing an entire mapping and workflow. If you would like to simply run a job up to a point and check the throughput, an entire mapping needs to be completed and you would workaround this by creating a flat file target.
Positives; - Multi User Development Environment - Speed of transformation - Seamless integration between other Informatica products. Negatives; - There should be less windows to maintain developers' focus while using. You probably need 2 big monitors when you start development with Informatica Power Center. - Oracle Analytical functions should be natively used. - E-LT support as well as ETL support.
PowerCenter is robust and fast, and it does a great job meeting all the needs, not just the most commercially vocal needs. In the hands of an expert power user, you can accomplish almost anything with your data. It is not for new users or intermittent users-- for that the Cloud version is a better fit. Be prepared for costly connectors (priced differently for each source or destination you are working with), and just be planful of your projects so you are not paying for connectors you no longer need or want
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.
Informatica power center is a leader of the pack of ETL tools and has some great abilities that make it stand out from other ETL tools. It has been a great partner to its clients over a long time so it's definitely dependable. With all the great things about Informatica, it has a bit of tech burden that should be addressed to make it more nimble, reduce the learning curve for new developers, provide better connectivity with visualization tools.
While Talend offers a much more comfortable interface to work with, Informatica's forte is performance. And on that front, Informatica Enterprise Data Integration certainly leaves Talend in the dust. For a more back-end-centric use case, Informatica is certainly the ETL tool of choice. On the other hand, if business users would be using the tool, then Talend would be the preferred tool.
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.
The data pipeline automation capability of Informatica means that few resources are needed to pre-process the data that ultimately resides in a Data Warehouse. Once a workflow is implemented, manual intervention is not needed.
PowerCenter did require more resources and time for installation and configuration than was expected/planned for.
The lack of or minimal support of unstructured data means that newer sources of dynamic/changing data cannot be easily processed/transformed through PowerCenter workflows.