We performed a comparison between Oracle OBIEE and QlikView based on real PeerSpot user reviews.
Find out in this report how the two Reporting solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I have found the most valuable features are business intelligence and reporting."
"The “Business Model & Mapping” layer in the Administration Tool, because the maintenance and evolution processes are greatly facilitated."
"Easy to create ad hoc reporting for different solutions."
"The most valuable features of the solution are the various scenarios the product offers and its stability."
"Provides good data visualization features, and provides a lot of visualization reports from various data sources."
"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."
"They were reasonable in terms of price."
"The most valuable feature is the reporting."
"Its ability to build, very quickly, very complicated models."
"Our Qlikview applications help us to get a good idea of our Client Base Performance and assist us in the decision making for Seasonal Specials. On the other hand QlikView helps us to get a grasp on our Suppliers and helps us to negotiate pricing with them."
"The integration with Salesforce has helped us gain access to crucial sales data in real-time."
"The scalability is there."
"We can scale it if we need to."
"If you correctly use the product for your use cases, it provides value for money."
"Scripting as per a customer's need, which is a pretty cool feature and not available in other tools."
"It's incredibly fast and can handle large volumes of data without slowing down our operations."
"An area for improvement is that Oracle pushes more users to Oracle BI Publisher rather than emphasizing Oracle OBIEE for reporting. The pricing for Oracle OBIEE could be improved."
"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."
"OBIEE doesn't have audit logs."
"In terms of tech support, we have our own technicians. But, we did register for their help. When we register a call, it takes time for them to respond to us."
"They should make the dashboard more intuitive."
"For a beginner, this is a product that is difficult to learn. You cannot learn it quickly."
"One feature I would definitely like to see is the ability to provide the in-memory data. Oracle might have some plugins but, as of now, that feature isn't available out-of-the-box. You might have to purchase that feature."
"Particularly on the Cloud, a lot of functionality has yet to be ported."
"Scalability really depends on the size of your data and QlikView server architecture. For the biggest data sets, it could become an issue at some point."
"If a user wanted to see something not included in the application the new object had to be created by a power user or developer because Qlik view's scripting has somewhat of a learning curve."
"Though the initial setup phase is simple, when it comes to the integration with the custom systems, the configuration and the compatibility sometimes take some more time."
"They could improve the speed."
"For me, it is important to have a mix, what is the "view" and what is the "sense", Qlik Sense. They have two tools, but for me it is important to have only one tool, which combines the functions that we have from one side and the other side."
"The tool is expensive in Turkey."
"Sometimes, dealing with complex reports requires more effort, which could be really improved."
"The pricing is high."
Oracle OBIEE is ranked 3rd in Reporting with 154 reviews while QlikView is ranked 5th in Reporting with 158 reviews. Oracle OBIEE is rated 7.8, while QlikView is rated 8.2. The top reviewer of Oracle OBIEE writes "A solution that is easily accessible, scalable and requires a straightforward initial setup process to get started". On the other hand, the top reviewer of QlikView writes "Useful for data visualization and business intelligence". Oracle OBIEE is most compared with Microsoft Power BI, SAP BusinessObjects Business Intelligence Platform, IBM Cognos, Tableau and SAP Crystal Reports, whereas QlikView is most compared with Tableau, Microsoft Power BI, Amazon QuickSight, SQL Server and Microsoft SQL Server Reporting Services. See our Oracle OBIEE vs. QlikView report.
See our list of best Reporting vendors.
We monitor all Reporting reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.