Informatica PowerCenter (legacy) vs. Logi Symphony

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.

Incentivized

For all the scenarios I have so far worked on or I am currently working on, Dundas BI has proved to be more than adequate and apt to handle all of those. It is a very easy-to-use tool with quick shortcuts enabling you to prepare ad-hoc reports or dashboards in a matter of minutes.

Incentivized

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

Incentivized

• Project organization from Development to Production, you get a production and development license but I think the best way to do it is with DEV and Prod project in the Production box. Use the development box for testing updates and really crazy things. With the Dev and Prod projects on the same box, you just publish from Dev to Prod and you are done. Users only have access to the Prod projects so no one can mess up what you are working on.
• Security - If you have a hierarchy (subsidiaries, divisions, department, teams) and you want each group to see only their data, then Security hierarchies are for you!
• Dependent filters! What's this you ask? Here is an example of how it can be used, in your company you have departments and who works for what department is in your database. You make a dashboard that has a department filter (only show these departments), a managers filter, and employee filter. Not every manager or employee is in multiple departments usually only one. With dependent filters you can say that the manager and employee filter are dependent on what is selected in the departments filter so when you go to filter them they only show the managers or employees that are part of that department, and you can even it do so employees are not only dependent on department but on manager as well. Then it gets even better as it can be done in reverse as well so when you select a manager then go to the department it only shows the departments he works for (there are better situations where this is more useful).
• It is scriptable! From calculate columns, null replacements, button actions, load actions, hover over events there a way to do what you want.
• They are constantly improving and listens to your suggestions.

Incentivized

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

Incentivized

• Not too many cons for how we use the application. It really is easy and powerful. Very powerful.
• Licensing is one thing that could be looked into. It is simple, but a little confusing. For example, if I get a license today, but a new release comes out tomorrow, it seems that the license doesn't work with the new release. Maybe that is by design, but it would be nice to clearly understand.

Our team enjoys using Informatica and feels that it is one of the best ETL tools on the market.

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.

Incentivized

We are still in the implementation phase, but so far we are finding it to be easy to use and learn. The eLearning courses that they have made available for free, as well as User Forums and other training videos have made even difficult concepts easier to understand.

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

Incentivized

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.

Incentivized

We have bi-weekly calls with our Success Manager, as well as access to support as needed. Any question that I have had, multiple people have been willing and able to jump on a call to talk me through it, or send an email with the solution

Providing that you have the client's needs well known, creating BI content using Dundas BI is a walk in the park!

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.

Incentivized

Per dollar spent, it offers the widest range of features of the tools that we evaluated. It offers lots of options for how to configure your environment, though they are not always intuitive to figure out. Having an ETL layer was a must have for us, as well as the ability to host to secure HIPAA compliance. It is not a replacement for ad hoc reporting, but does a great job of creating parameterized reports and dashboards that look great.

Incentivized

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

Incentivized

• Coming from an SQL based standard delivery model, Dundas BI has provided a fantastic rate of ROI.
• The preparation and delivery time has reduced from weeks to just a few hours.

Incentivized