We performed a comparison between Oracle OBIEE and Tableau 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."In terms of features, everything is good. It is also stable and scalable."
"It is easy to use...I rate the scalability of the solution a nine out of ten."
"The setup isn't too difficult."
"The centralized metadata model component is most valuable."
"It can be used with any type of data models, such as relational lines and dimensional lines."
"We have scheduled reports delivered automatically to our business users using enterprise features."
"It doesn't have many frills and is definitely older technology, but it is undeniably a workhorse."
"It is easy to create a report quickly. It does not take much time to create an ad hoc report."
"When compared to Power BI, Tableau has more readily available resources."
"The most valuable feature is the geographic data analysis."
"It is an excellent tool for data capture, processing, and visualization."
"The maps and colors and interface are all fantastic."
"Technical support has been responsive."
"Tableau is easy to use compared to some other solutions, such as Excel."
"The solution deployment was straightforward."
"Partner support is very good."
"Oracle OBIEE is a product that is not easy to implement. The product is also not easy to use."
"When a large number of queries are running at the same time, the report fails."
"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."
"It was a little bit tedious to install a new release."
"The performance could improve and in a future release, they could provide more virtualization options."
"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."
"It's not so flexible to do BI reporting directly from the data source without models. It is not that agile."
"The data processing in Tableau is pathetic compared to Qlik."
"There should be more GIS features, such as location analysis, which is quite limited. There are very few location-based functionalities."
"With performance tuning, it generates a pretty complex query when it is not required."
"The customization requires a lot of effort and should be simplified. The performance could be better."
"When there are millions of records, scaling up is quite difficult."
"I would like to have the product be more flexible in terms of creating online shared dashboards."
"I also work as an SME on the platform side. Tableau is very nice and jazzy for the end-users, but there are pain points for the admins. Performance is something about which we hear a lot of complaints, such as the dashboard doesn't open in time. It performs well on the desktop but not on the server. I know that there is always a limitation when it comes to a huge amount of data or the complexity of the calculations, but we often hear from end-users about the performance on the server side. It is easy to drag and drop all the columns and do what we want, but if it is not going to load better on the server, users are not going to like it."
"The performance could be better."
Oracle OBIEE is ranked 3rd in Reporting with 154 reviews while Tableau is ranked 2nd in Reporting with 290 reviews. Oracle OBIEE is rated 7.8, while Tableau is rated 8.4. 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 Tableau writes "Provides fast data access with in-memory extracts, makes it easy to create visualizations, and saves time". Oracle OBIEE is most compared with Microsoft Power BI, SAP BusinessObjects Business Intelligence Platform, IBM Cognos, Oracle Analytics Cloud and Microsoft SQL Server Reporting Services, whereas Tableau is most compared with Microsoft Power BI, Amazon QuickSight, Domo, SAS Visual Analytics and Google Data Studio. See our Oracle OBIEE vs. Tableau report.
See our list of best Reporting vendors and best BI (Business Intelligence) Tools 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.