We performed a comparison between IBM Cognos, Microsoft Power BI, and Oracle OBIEE based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Tableau, Oracle and others in BI (Business Intelligence) Tools."The most valuable features are Report Development (Functionality) and Information Distribution (Flexibility)."
"The correlation analysis is excellent. It's one of the best that I have used to date."
"In terms of stability, I think that Cognos is more stable than Tableau and Power Bi because of its framework manager concept that allows us to import metadata and store it in the framework manager."
"Dashboarding, reporting, and ad hoc reporting are the valuable features of IBM Cognos."
"It has a very powerful edit feature which allows users to back out of changes (undo) without forcing them to recreate entire reports."
"We use IBM Cognos for enterprise analytics and reporting."
"The solution's most valuable feature is its ease of use, which makes it easily compatible with other tools."
"The comprehensiveness or broadness of the software functions or business intelligence functions that it provides is valuable. It is also quite easy to use and user-friendly."
"It is really flexible. The charts and reports are really nice. You have the flexibility of self-service."
"What I like about Power BI is how fast you are able to create dashboards and how fast you are able to fetch the data. You can connect to the database or data source, and then you can design your dashboards very easily."
"The most valuable features are the easy creation of reports, dashboards, and the ability to perform analysis. It is important for us to create reports because we have some operations during certain hours and we can use this tool to track the information."
"The solution overall is very useful. The reports that are generated and the reporting functionality management are beneficial."
"Like all Microsoft products, it is very easy to set up initially."
"Good CS and administration."
"My primary use is for view of the dashboard."
"It is more user-friendly compared to SSRS."
"Oracle OBIEE is a scary and stable product since it is a strong and well-created tool... In short, the solution is stable since it works properly every day."
"The most valuable feature of Oracle OBIEE, for me, would be the Web Catalog. From a development perspective, I do not need any client or any software to be installed on my laptop or desktop. Everything is browser-based, so I just open the browser and start development."
"The visualization is very good."
"It can be used with any type of data models, such as relational lines and dimensional lines."
"It provides excellent stability."
"There are some great new features in the latest version."
"They were reasonable in terms of price."
"Scalability-wise, I rate the solution a nine out of ten...The solution's initial setup was straightforward."
"Tableau and Power BI are faster than Cognos."
"The visualization aspect needs to be improved and I believe, this is being resolved in upcoming versions."
"I would like to see is more easy building, movement in the reports, and dashboard functionality within reporting. Overall more simple elements within reports. If the elements are simple then you don't have to render a full page, but you can move separate parts in the page."
"I don't like that when we use Colab packages, we get less functionality. For example, you can make groups of data with Excel or with the data sets from the packages, but when you use the Colab packages directly, you can only group the data when you analyze it with Analysis Studio. I think Cognos needs to improve more on this functionality."
"The charts and graphics are weak."
"Chart quality: many other competitors have charts and graphics that look much better and that provide dynamic effects. Cognos doesn't."
"The technical support team’s response time is slow and needs to be improved."
"Compared to Tableau and PowerBI, the IBM interface is easier to use. However, the drag-and-drop functionality isn't as straightforward. Formatting is also more challenging in the cloud than in other applications, like Power BI. Also, if you encounter an issue, it takes more time to resolve it on the formatting side."
"The solution struggles with large amounts of data."
"The solution could improve by having more attractive graphical charts."
"We need more integration capabilities."
"A few features available in Tableau are not available in Power BI. For example. Tableau has the ability to make up the physical layer and all other stuff at runtime. In Power BI, we have to develop a proper physical layer to connect it. The limitation that we normally face is related to the direct query mode. When it comes to the direct query mode, most of the functionality is not working, which is an issue for us. We have to use the direct query mode frequently because the client needs real-time data. They should work on this limitation. There are a lot of other technical things that need to be improved. I am also following the Power BI platform and Microsoft Support Center platform on the web where users have put their requirements. Microsoft is also working on improving this solution. In every update, they add new features to this solution."
"These licenses are in US dollars. With a long-term license, the client is unaffected when the exchange rate goes up. However, if the exchange rate goes down, you don't get refunded from the excess money you've paid. I guess that is a risk you take in business."
"One area for improvement in Microsoft Power BI is serviceability. Compared to one of its competitors: Tableau, there are a lot of things which you cannot do in this tool, that can be done in Tableau."
"Some kind of expression wizard, where the user can build a complex expression without any knowledge of DAX, can be a good addition to the product."
"The solution could improve the extraction and transformation of data. For example, you transform the data and then send it to Microsoft BI without having to use your own API. We are only providing the API to Power BI, and then Power BI is doing the job."
"n the beginning it had it's stability issues, but it became stable."
"There should be more integration in the solution. For example, there should be one solution with multiple functionalities so that other solutions are not needed. Having one solution with all the needed functionality would be helpful."
"Supply chain and finance."
"Oracle OBIEEE's performance and licensing costs could be improved."
"In the on-premises version, the feature for connecting and selecting the data between the databases looks a bit cumbersome, but I am not sure. The person who is using it takes a lot of time to design a data warehouse. When I ask him why is it taking this long, I get a response that this is something that he has to design, and there are different tools that are available. He has to write the ETL and design the warehouse according to the customer's requirement, which takes a lot of time. Its visualization should be enhanced, and there should be a feature where you can easily create your custom data warehouse."
"Even though we have a feature to enable the physical query to be seen in the log, in case of any issues, it is challenging to debug and see or identify where is the issue. For example, we designed the OBIEE repository and deployed it into the server, and we are now accessing and creating a report. For some reason, if the report is not working as expected, it is very difficult to identify the issue. We have a feature to see the physical query that is being generated in the central OBIEE server. I feel that this feature should have been available at the repository level so that while designing the repository, we can select the presentation columns and the query it is going to create. This will avoid the additional task of deploying a feature into the server and then testing the report. It will also make the implementation process friendly if, while designing the repository, we can see: How is a feature working? Are any of the presentation columns selected? How is the query being generated? Which query is being generated? Are any joints used? What kind of joints are used? Having this kind of information will make Oracle OBIEE more powerful and developer-friendly."
"When a large number of queries are running at the same time, the report fails."
"Oracle OBIEE can improve the ease of use. It is a lot to learn and it could be made easier."