- Larry Ellison enjoyed observing how SAP, Salesforce and Workday pay large amounts of money for Oracle database licenses.
- We cover how PostgresSQL as an Oracle replacement.
Introduction to Oracle’s Outrageous Statements
On Jun. 17, 2015 Business Insider published the article Larry Ellison: SAP and Salesforce pay Oracle a LOT of money.
In this article, we will review the article for accuracy.
“Oracle reported its fourth quarter earnings on Wednesday and, as we’ve come to expect from the company’s flamboyant billionaire founder, Larry Ellison threw a few barbs at his major competitors.”
“He slammed SAP’s Oracle-killer database HANA on a conference call with analysts like this:
“SAP does not use HANA in the cloud very much. I know that because they keep paying us. They paid us again, this quarter, for Oracle for Concur, Oracle for Ariba, Oracle for SuccessFactors,” he said, naming three cloud companies that SAP acquired over the past few years to jump start its cloud business.
“If they’re using HANA for anything, I don’t know about it,” Ellison chuckled.”
Expanding upon what Larry said, HANA is used for only a small portion of SAP’s applications. HANA is compatible with more applications than it is generally used for, but up until now, the vast majority of HANA implementations are with only one application, which is SAP BW.
“Like other Oracle customers, SAP must have found that it isn’t easy to rip and replace a database, even though it must be excruciating to write checks to Oracle.
One of Oracle’s CEOs, Safra Catz, explained why Oracle doesn’t have that problem. Oracle makes all the hardware and software it needs to build its own cloud. This means that Oracle’s cloud can be run more profitably than competitors, she said.”
That may be true, but it is not a reflection of how most of Oracle’s database business is delivered. Most of Oracle’s database business is still delivered on premises. Furthermore, this quote does not have much to do with why HANA is not more prevalent.
“Ellison agreed and used a slam at Salesforce as an example:
“Salesforce paid us a lot of money for their platform. They buy Exadata from us to run their data center, they buy the Oracle database. They paid a LOT of money for the Oracle database,” he said, referring to a 9-year deal signed in 2013 between the two competitors.”
The parallel between SAP and Salesforce paying Oracle a lot of money simply is not there. It is not relevant (at least vis-a-vis SAP) that Salesforce pays Oracle a lot of money as unlike SAP, Salesforce has not put all of its chips on pushing HANA into their customer base. In fact, Salesforce does not even focus on the database when it discusses its solution with customers. Salesforce focuses on the business value or ease of use of its applications.
The Relevance of Salesforce on Oracle
The relevance is however between Salesforce, which does use Oracle, versus Workday, which does not use Oracle. Workday is along with Salesforce one of the largest SaaS vendors in the world.
“As the two companies became more competitive, and the two men had a falling out, Salesforce was rumored to be trying to move to an open source database known as Postgres. That would have been a bad precedent for Oracle, showing other cloud companies how they could migrate off Oracle, too.”
Postgres is picking up steam as a highly respected heavy duty database that can in many cases replace Oracle 12c. And Postgres’ rise is of concern to Oracle.
“Instead the two men buried the hatchet, momentarily, and cut a deal estimated to be valued at $300 million, where Salesforce would continue to buy Oracle’s products for another nearly decade. It was said to be a pretty good deal for Salesforce.”
“As for Oracle’s other arch rival in the cloud, Workday?
Ellison dissed Workday in the usual ways, saying that it was winning 10 times more deals than Workday for a cloud version of the financial application known as enterprise resource planning (ERP).
We know that Workday doesn’t use Oracle’s database or any of Oracle’s technology. Ellison has said so.
So, every customer that leaps to Workday is a double loss for Oracle, both in the sale of the cloud contract, and the sale of the infrastructure that runs Workday’s cloud.
“They’re basically—this small company is basically going to have to build all of their own database technology. I mean, they need recovery, they need query processing, they need ad-hoc reporting, they need all of these things. They’re gonna have to build out that tool set themselves rather than relying on us like Salesforce.com does,” said Ellison, who also mentioned in the same context Netsuite, SuccessFactors, and SAP.”
It is not just Workday, but many other SaaS companies that have the scale are bypassing Oracle to develop their databases or using open source databases. Google mostly does not use Oracle. Quite obviously, Larry is going to be negative on this strategy. Yet the trend of not building your own or using open source databases is growing not shrinking. There are many cloud vendors that are choosing not to use Oracle for their database.
How is Oracle Situated
Oracle is better situated when they market to an end customer. But large SaaS vendors have the scale to develop their own versions of databases, and to leverage open source databases like Postgres without facing the backlash that a person might receive in an IT organization for not choosing Oracle, IBM or Microsoft.
“This has caused Wall Street analyst, Jefferies analyst John DiFucci to report that Oracle has been behaving “irrationally” to win deals from Workday for over a year.
Oracle is offering such steep discounts to customers when competing for deals against Workday, that Oracle is willing to go into the red on these deals, Jefferies analyst John DiFucci tells Business Insider.”
That makes sense. If Workday shows success without Oracle as a database, it is a signal to other SaaS vendors. One of the major marketing pitches of Oracle is that for really big and important implementations you use Oracle because it is so tested, so stable, etc.. But if Workday, which uses a multi-tenant database, and has major volume, cannot choose Oracle, then it is a beacon to those who would also choose a different path.
This article by Business Insider replays the quotes from the different actors, but it does not seem to know what they mean. It hits on several important points, such as the fact that some SaaS vendors have turned away from Oracle. It also gets the fact that SAP still mostly uses Oracle.
But overall, it is not clear the author understands these topics at sufficient depth to write an article on the subjects being covered. It appears that this article could be split into two, one covering the topic of SaaS vendors that use non-Oracle databases, and the other being how even after years of promoting HANA, SAP still primarily runs on Oracle (and DB2).
Search Our Other HANA Content
Financial Bias Disclosure
This article and no other article on the Brightwork website is paid for by a software vendor, including Oracle and SAP. Brightwork does offer competitive intelligence work to vendors as part of its business, but no published research or articles are written with any financial consideration. As part of Brightwork’s commitment to publishing independent, unbiased research, the company’s business model is driven by consulting services; no paid media placements are accepted.
[Why Workday Is Different by Design, and Why It Matters](https://blogs.workday.com/why-workday-is-different-by-design-and-why-it-matters/)
[Oracle is ‘irrational’ towards Workday – Business Insider](https://www.businessinsider.com/oracle-is-irrational-towards-workday-2015-5)
The Risk Estimation Book
Better Managing Software Risk
The software implementation is risky business and success is not a certainty. But you can reduce risk with the strategies in this book. Undertaking software selection and implementation without approximating the project’s risk is a poor way to make decisions about either projects or software. But that’s the way many companies do business, even though 50 percent of IT implementations are deemed failures.
Finding What Works and What Doesn’t
In this book, you will review the strategies commonly used by most companies for mitigating software project risk–and learn why these plans don’t work–and then acquire practical and realistic strategies that will help you to maximize success on your software implementation.
Chapter 1: Introduction
Chapter 2: Enterprise Software Risk Management
Chapter 3: The Basics of Enterprise Software Risk Management
Chapter 4: Understanding the Enterprise Software Market
Chapter 5: Software Sell-ability versus Implementability
Chapter 6: Selecting the Right IT Consultant
Chapter 7: How to Use the Reports of Analysts Like Gartner
Chapter 8: How to Interpret Vendor-Provided Information to Reduce Project Risk
Chapter 9: Evaluating Implementation Preparedness
Chapter 10: Using TCO for Decision Making
Chapter 11: The Software Decisions’ Risk Component Model