Try our new research platform with insights from 80,000+ expert users

Looker vs Oracle OBIEE comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Looker
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
19
Ranking in other categories
Embedded BI (9th)
Oracle OBIEE
Average Rating
7.8
Reviews Sentiment
6.4
Number of Reviews
158
Ranking in other categories
BI (Business Intelligence) Tools (13th), Reporting (8th)
 

Mindshare comparison

While both are Business Intelligence solutions, they serve different purposes. Looker is designed for Embedded BI and holds a mindshare of 6.4%, down 9.1% compared to last year.
Oracle OBIEE, on the other hand, focuses on BI (Business Intelligence) Tools, holds 1.4% mindshare, down 3.9% since last year.
Embedded BI Market Share Distribution
ProductMarket Share (%)
Looker6.4%
Tableau Enterprise17.9%
Qlik Sense9.2%
Other66.5%
Embedded BI
BI (Business Intelligence) Tools Market Share Distribution
ProductMarket Share (%)
Oracle OBIEE1.4%
Microsoft Power BI8.9%
Tableau Enterprise6.2%
Other83.5%
BI (Business Intelligence) Tools
 

Featured Reviews

Kishore Jhunjhunwala - PeerSpot reviewer
Sr Analytics Consultant at a outsourcing company with 1,001-5,000 employees
A cloud solution for operational reporting but is expensive
Some basic feature that is available in other reporting tools is missing. Looker has the ability to show more than 5,000 rows for operational reporting. Some reporting tools allow users to scroll down to see more than 5,000 rows, but in Looker, you have to download the entire dataset. Looker should consider adding a scroll-down option to allow users to view large datasets on screen without downloading them. Looker has some options for granting users access as viewers. However, viewers cannot download the entire dataset. Only superusers can download the whole dataset on the Explore screen. This is a big limitation, as you cannot give any user viewer access. You can give access to superuser access, which is a cost to the company.
reviewer2701689 - PeerSpot reviewer
Innovation & Data Management Enterprise Architect at a government with 1,001-5,000 employees
Facing a complex learning curve challenges, automation capabilities provide some clerical work savings
Oracle OBIEE has a steep learning curve compared to tools like SQL Server or Power BI. In situations where complex problem-solving is required, Oracle's support tends to direct users to sales representatives with limited technical knowledge, which is less than ideal. Additionally, the solution is more expensive than using Microsoft's reporting tools.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I would rate the stability a ten out of ten. I didn't face any issues with stability."
"Looker allows you to generate the most optimal SQL queries in a DC through UI actions. We had signed a contract with Google Cloud to use BigQuery. That was the primary reason we adopted Looker. It works better with BigQuery than any other BI platform. We also like how this tool was developed. It was designed with an eye toward microservices architecture."
"We can centralize all our data models."
"The product is easy to use."
"With Looker, I have experienced benefits in terms of usability and shareability."
"From a developer's perspective, the way the functionality's being handled is great."
"It's quite effortless to navigate through various applications and review their updated data in real-time."
"It is a pretty stable solution because it is a cloud-based product."
"There are a lot of functions in the product, including a drill-down functionality and level-based hierarchies that are very attractive."
"It is a very stable solution."
"Some of the dashboard capabilities are good. The dashboard capabilities that tell you what kind of reports are available and provide you a summary of the reports are valuable. It is easy to navigate and easy to download reports into Excel to utilize them."
"Its robustness is most valuable. It can handle massive amounts of data quickly. If it's properly configured and tuned, it can handle massive amounts of data very quickly to produce results. That to me is the number one feature."
"The centralized metadata model component is most valuable."
"It's easy to use for business analysts."
"I think having the conformed structures makes it a lot easier for end users and pulling reports together."
"The most valuable feature of Oracle OBIEE is its ability to handle large volumes of data and provide traditional BI functionalities that developers can easily understand."
 

Cons

"The integration with different databases must be improved."
"The visualization capability of the product is limited."
"Integrations with other BI tools could be better."
"Looker doesn't connect to Excel, which is a huge disappointment because a lot of data is presented in Excel. Also, it can't consume data directly from REST APIs, which is necessary. Looker needs to expand its horizons when it comes to data sources. The inability to connect to different data sources is hampering our use cases. Currently, it only has an ODBC connection that connects to a database. It needs to connect to other data sources, such as Excel, APIs, and different platforms."
"The product does not have documented material."
"It needs to be more user-friendly."
"The main area of concern in Looker is probably related to blending the data from the different sources, including the data present internally in the company and on the cloud."
"Stability needs improvement."
"Oracle OBIEE can improve the ease of use. It is a lot to learn and it could be made easier."
"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."
"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."
"The performance and the complex setup are the main reason for switching to Qlik Sense."
"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."
"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."
"Supply chain and finance."
"It crashes when many people login simultaneously."
 

Pricing and Cost Advice

"I do not have to make any payments to use the solution."
"Looker is expensive and could be made better by reducing it."
"The price of Looker usually depends on the solution's provider, but it is usually cheaper than the other products in the market. Looker is offered at different prices for different companies."
"It's not cheap, but it's not expensive for big companies."
"It is cheap."
"This was not an expensive product for us, although the price varies depending on conditions for each company."
"The licensing cost for Oracle OBIEE is expensive."
"It's comparable to the current technology we're using, Qlik Sense."
"The cost of this solution is a little bit high compared with other products like Zoho, so reducing it would make OBIEE more competitive."
"The price of Oracle OBIEE is expensive, it is difficult for a small business to afford."
"It is reasonable, but it depends on how you're going to use it. There are no costs in addition to the standard licensing fees."
"It's expensive."
"In our organization, we use a user-based license for Oracle OBIEE, and I've heard that the license cost is based on the number of users."
report
Use our free recommendation engine to learn which Embedded BI solutions are best for your needs.
882,886 professionals have used our research since 2012.
 

Comparison Review

it_user79932 - PeerSpot reviewer
Senior Manager - BI Head with 5,001-10,000 employees
Feb 4, 2015
Comparison of SAP BO, Tableau, QlikView, Cognos, Microsoft, OBIEE and Pentaho
1. SAP BO/BI Enterprise scalability Security Ease of use Semantic layer 2. Tableau Visualization Data discovery Turnaround time 3. IBM Cognos Enterprise scalability Security In-memory feature 4. MS BI - Flexibility 5. Pentaho - Open source but still enterprise grade 6. QlikView Data…
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Retailer
9%
Computer Software Company
9%
Media Company
8%
Financial Services Firm
16%
Government
10%
Manufacturing Company
7%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise8
Large Enterprise6
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise34
Large Enterprise102
 

Questions from the Community

Ask a question
Earn 20 points
How does Oracle OBIEE compare with Microsoft BI?
Oracle OBIEE is great in allowing design and creativity per the individual needs of the organization. Dashboards are fully customizable and very user-friendly. This solution is very stable. Oracle ...
Which Oracle product is better - OBIEE or Analytics Cloud?
Oracle OBIEE is designed to be relatively easy to set up and has a helpful customer support staff at the ready to assist customers. These are two attributes that make this system quite valuable. OB...
What do you like most about Oracle OBIEE?
The most valuable feature of Oracle OBIEE is its ability to handle large volumes of data and provide traditional BI functionalities that developers can easily understand.
 

Comparisons

 

Also Known As

No data available
OBIEE, Oracle Business Intelligence Enterprise Edition, Oracle BI, Oracle BI EE 11g
 

Overview

 

Sample Customers

Yahoo!, Etsy, Kohler, Hipcamp, Hubspot, Kickstarter, Venmo, Dollar Shave Club, 600+ customer
Banca Transilvania, BeckmanCoulter, Hong Kong Housing Society, HealthShare, Ivanhoe Cambridge Unifies, and Home Credit, and Finance Bank.
Find out what your peers are saying about Salesforce, Qlik, MicroStrategy and others in Embedded BI. Updated: February 2026.
882,886 professionals have used our research since 2012.