We performed a comparison between Oracle OBIEE and QlikView based on real PeerSpot user reviews.
Find out in this report how the two Reporting Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
"Provides good data visualization features, and provides a lot of visualization reports from various data sources."
"The most valuable feature of Oracle OBIEE is the security of the solution."
"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."
"Oracle OBIEE is good for data visualization and analytical reporting."
"The dashboard and analysis are the most valuable features of this solution."
"The solution offers a wide range of software tools to meet various needs, such as those concerning reports, developer solutions like APEX and the integration of data."
"The visualization is very good."
"The solution has great reporting and forecasting capabilities."
"We can scale it if we need to."
"Easy to analyze data by click-through."
"The scalability is there."
"You can switch views easily."
"Once you open it up, you see everything that you can do."
"On the positive side, QlikView's scripting is a great asset as it functions as an ETL."
"It is useful to use a tool like this to have a view of data at a point in time. You can extract and create little data sets that you can store, and then over time, you can have a view for tracking changes. Especially when you work with a relational database or a database that's a production database, the data is dynamic, but if you use QlikView, you can take a snapshot of different datasets. In your own time, you can then get insights and report, build, analyze, and draw whatever you need from the data, which is quite useful."
"There's a lot of redundancy, especially in relation to creating the code."
"Expanding beyond pure data reporting and into analytics, or expanding data science, would be areas for improvement."
"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."
"One significant improvement is the need for simplification. The set up could be more intuitive. An enterprise setup with HA and DR are pretty complex and to get a robust solution one has to play around with Real Application Cluster data sources and FAN notifications as well as WebLogic clustering and external load balancers. SSO also is not that simple to set up especially if you want all your Oracle systems to use the same SSO solution, i.e., no cheating with direct LDAP connectivity."
"There are a lot of aspects of Oracle OBIEE that are exceptionally complicated, make things unnecessarily difficult for everyone who uses it. In terms of the integrations, Oracle needs to improve a little more, but I believe that they have tried to capture all those issues. The issues we are facing in the Oracle OBIEE 12C versions, in the Oracle Analytical Server Center or Analytical Cloud versions, Oracle has managed to overcome the challenges."
"The graphical capabilities could be better. They are also cumbersome, and they are limited compared to Tableau, Power BI, or even Business Objects to a certain extent and Cognos. The error logging isn't great either. The errors that come out when you schedule aren't easy to understand. I find how they filter within a query quite cumbersome and difficult to debug if somebody else has done it. You can see as you build, and I think that's where the problem is. It doesn't lend itself to debug something. For example, if you create a formula that's quite complicated, it's not easy to understand what goes with what. It becomes spaghetti, and it's very difficult to unpick. That's really my gripe about it, and in some ways, it's too flexible. It tries to be a Jack of all trades when it's not. I think a lot of these products, if they concentrate on trying to produce your reports, then that's fine. But when they're trying to do all sorts of other things as well, then it isn't very easy. We get lots of support from Oracle, but I think the problem is that we get many invalid file operations. Nobody understands why. It can be a multitude of reasons, but no one reason could cause it. That's just one of the issues we've had in the last year. But the scope of reporting has gone through the roof over the previous 12 to 18 months. We want an end-of-life OBIEE in our environment because some of the infrastructure runs unclustered. We weren't allowed to go clustered for some reason, and we never knew why. Unfortunately, going down that route means that the platform we run it on, WebLogic, has now become non-standard within our organization. Everything's been moved off it and onto other platforms. Unfortunately, our OBIEE runs on that platform, and we're being pushed down different routes, and we don't know where we're going at the moment. Within the next two years, I don't think we'll have OBIEE in our part of the business. In the next release, I think having the capability of being able to develop and then promote to a production environment rather than having to have separate environments will help. I know that Tableau and Power BI can be created on a desktop application, and then when it's ready to go live, you can promote it."
"The performance and the complex setup are the main reason for switching to Qlik Sense."
"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."
"They could improve the speed."
"The user interface is old."
"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."
"The only thing I would improve about it is the fact that it refreshes all the time, and when it does that, it just deletes all the options you had, all the filters that you had selected, so you need to select them from the beginning."
"It is really old. We are moving towards converting everything into a Power BI environment. We want to have a self-service type of BI environment where different levels of users in organizations can log onto a portal and retrieve the data they need or get the necessary insights for decision-making that's important for them or their business unit. They have built a new version of QlikView called QlikSense, which probably competes with newer BI tools, such as Power BI, but they are far behind. That's why we are moving towards a newer tool that's easier to use and has more visualizations to represent the data."
"They could improve the update time."
"Sometimes the filters are disappearing, and I'm not sure why this is happening."
Oracle OBIEE is ranked 4th in Reporting Tools with 33 reviews while QlikView is ranked 5th in Reporting Tools with 7 reviews. Oracle OBIEE is rated 7.8, while QlikView is rated 7.8. The top reviewer of Oracle OBIEE writes "Extremely flexible, easy to set up and great for reporting". On the other hand, the top reviewer of QlikView writes "Snapshots are helpful for having a view of the data at a point in time and comparing changes, but it is expensive and far behind other modern tools". Oracle OBIEE is most compared with Microsoft BI, Oracle Analytics Cloud, SAP BusinessObjects Business Intelligence Platform, Tableau and MicroStrategy, whereas QlikView is most compared with Tableau, Qlik Sense, Microsoft BI, SQL Server and Alteryx. See our Oracle OBIEE vs. QlikView report.
See our list of best Reporting Tools vendors.
We monitor all Reporting Tools 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.
