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."The security is good. For example, we can implement column-level security."
"The most valuable feature is the ability to run it in Exalytics within memory coupled to a Repository on Exadata is where it flies. So it's not meant for mom and pop shops, but if you are a global 500 fortune 1000 company, this is a tool that can get you what you need on time and even in real time."
"The most valuable feature is the visualization."
"It can be used with any type of data models, such as relational lines and dimensional lines."
"The performance can issue queries to work in the Oracle database in Oracle's native language. There are a lot of visualizations which suit our business."
"They are introducing AI. There are good forecasting features and machine learning."
"We have scheduled reports delivered automatically to our business users using enterprise features."
"The solution has great reporting and forecasting capabilities."
"The most valuable aspect is its extensive library on Microsoft, providing a robust framework for implementation."
"One of the good thing is that you can integrate different data source technologies. So you can model your environment without having any of our views running."
"The initial setup is not very complex."
"If you correctly use the product for your use cases, it provides value for money."
"Associative model - no more cubes."
"The search feature: ability to see the related data."
"The language support is very good."
"This is a very cool application with endless options of creativity and visuals."
"Its overall organization as an analytical tool, the layout of OBIEE, is not very good."
"I find I prefer Oracle OAC over OBIEE. It's more advanced, has artificial intelligence, and there's more that we can do with it in general. OBIEE is lacking features."
"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."
"They should develop greater visualization because their visualization isn't industry leading at the moment. The way you pull the data and see the data compared to other platforms, they're lagging a little bit behind. Also, their cost. I've got Oracle account managers trying to persuade me every day to purchase these licenses. Once you purchase OBIEE, then you have to purchase the virtualization and then you have to purchase the mobile license to operate on the mobile. It's really expensive."
"It would be better if it had a wide range of visualization options. For example, Microsoft Power BI has an extensive range of visualization options, but it's not available in OBIEE. There are also some conflicts because it's complicated, but the cloud application is easier. They added some features for ETL with the on-premises application, but we need a different or a separate application for ETL in the cloud. In the next release, I would like to have more AI features."
"Essbase integration needs to be worked on."
"Its functionality is lacking."
"While it is a user-friendly, data-driven tool, the data modeling should be easier to use."
"Error handling."
"Sometimes the filters are disappearing, and I'm not sure why this is happening."
"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."
"The solution is quite costly."
"I would like to see more advanced features from Qlik Sense integrated into QlikView to keep it competitive and up-to-date."
"Improvement in collaboration, between that and publishing of reports and publishing of models."
"This solution would be improved with the inclusion of a feature that would allow us to add a common library of (our) commands used in load scripts and expressions, so with a keyword, we would get a drop down to select the command we are looking for, as opposed to the generic help."
"There is a challenge on the frontend when it comes to browsing data through QlikView, as it isn't entirely compatible with other platforms we use."
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.