Why Oracle must kiss goodbye to its database past

Moneybags Larry hopes cloud will shower him in cash

Providing a secure and efficient Helpdesk

Open ... and Shut A few years back Apple opted to drop the "Computer" from its corporate name, and instead became "Apple Inc." Last week, Oracle made a similar move, quietly stopping its decades old practice of reporting database revenues. Oracle chief executive Larry Ellison was quick to point out on Oracle's earnings call that for its database sales force "it's business as usual." But is it? By opting to stop breaking out its database numbers, Oracle is telling the market that it's no longer a database company.

That's the spin Cloudera CEO Mike Olson puts on the change, arguing in a Facebook post (which he allowed me to share):

Oracle wants investors to pay attention to something else now, and is changing what it talks about to make that happen….[I]f you don't report database revenue, you're no longer a database company. And I bet Oracle leadership would agree with that statement.

Not that Olson thinks the move is insignificant. In announcing the shift, he wrote: "Oracle Corporation no longer breaks out database revenues in its earnings reports. Next up: Frogs. Locusts." Steven J. Vaughan-Nichols, a long-time Oracle observer, for his part, "find[s] it troubling," arguing that "at the end of the day, [databases are] what defines them" and that analogous changes would be "IBM not reporting on mainframes, MSFT on Windows, etc."

But maybe, just maybe, that's what Oracle wants, to underline Olson's point.

Despite initially pooh-poohing the cloud, Oracle has doubled-down on cloud computing. It has also acquired a mass of companies selling everything from applications to hardware. In the midst of that "cloud" of software services and on-premises software that Oracle now peddles, the database has become just component among many in Oracle's arsenal, as Sean Kerner points out:

And yet, Oracle president Mark Hurd insists that it continues to have a dedicated database team that does nothing but sell its database offering. Surely that team is being compensated for those sales, so figuring out total database sales must remain reasonably straightforward.

If Oracle wanted to do so. But, apparently, it doesn't.

The charitable, and perhaps correct, view is Olson's. But others are less sanguine about Oracle's rational and, indeed, about its business, generally. Cowens & Co analyst Peter Goldmacher had this to say:

Management claims of investing in Sales and Marketing ring hollow considering Sales and Marketing spend is down year-over-year in absolute terms. Revenues are in structural decline as every segment of Oracle's business is under attack from a new generation of technology providers that offer equivalent or better technology at a lower cost. But as long as management can continue to cut costs faster than revenues slow, earnings will grow, until they won't. No part of the bull case for Oracle... addresses growth, competitiveness or market share gains.

Painful, but possibly true. Oracle, after all, is seeing its applications business under siege from more nimble competitors like Workday, while its core database business is under threat from a long-term shift to non-relational database and Big Data competitors like Cloudera (currently an Oracle partner) and 10gen (MongoDB).

Given the headwinds facing Oracle, coupled with the difficulty of changing direction for a company that employs 120,000 people, it's perhaps not surprising that Oracle is trying to shield scrutiny from the inevitable pain it's going to feel in individual product lines while it moves to becoming a true cloud computing company. El Reg's own Timothy Prickett Morgan emphasizes that Oracle's change in product revenue reporting means "we have no idea how these business units are doing individually anymore."

Which is almost certainly the point. As Ellison noted on the Oracle earnings call:

A lot of companies have a difficult time adapting to the next generation of technology. And those with the most are also the ones with the most to lose. You have to be willing to change the way you were doing business in the past and adapt to the new opportunities and exploit the new opportunities.

Reading between the lines, Ellison seems to be acknowledging just how difficult this transition to the cloud has been (Oracle has been working on its Fusion technology for seven years), and will continue to be. Buying some breathing room by focusing on the big picture (cloud) while minimizing short-term pain in individual products (such as databases or applications) is a smart move.

And a painful one. As ZDNet's Larry Dignan highlights, Oracle has spent years dabbling in hardware, only to have the hardware business consistently underperform and distract the company from getting fully into the cloud. Apparently Oracle has learned its lesson. What remains unclear, however, is whether shifting to the cloud will prove as successful as decades of database dominance have been. In the cloud Oracle is a neophyte, albeit one with gargantuan resources behind it.

No matter how Oracle financially engineers the painful shift to the cloud, at some point it's going to have to show financial results. So far, they don't look pretty. With all the competition it's facing, they may never look pretty. But full credit to Oracle for engineering a transition to the cloud, even if it had to abandon its past glory as a database giant to do so. ®

Matt Asay is senior vice president of business development at Nodeable, offering systems management for managing and analysing cloud-based data. He was formerly SVP of biz dev at HTML5 start-up Strobe and chief operating officer of Ubuntu commercial operation Canonical. With more than a decade spent in open source, Asay served as Alfresco's general manager for the Americas and vice president of business development, and he helped put Novell on its open source track. Asay is an emeritus board member of the Open Source Initiative (OSI). His column, Open...and Shut, appears three times a week on The Register.

Secure remote control for conventional and virtual desktops

More from The Register

next story
Scrapping the Human Rights Act: What about privacy and freedom of expression?
Justice minister's attack to destroy ability to challenge state
WHY did Sunday Mirror stoop to slurping selfies for smut sting?
Tabloid splashes, MP resigns - but there's a BIG copyright issue here
DVLA website GOES TITSUP on day paper car tax discs retire
Welcome to GOV.UK - digital by de ... FAULT
Hey Brit taxpayers. You just spent £4m on Central London ‘innovation playground’
Catapult me a Mojito, I feel an Digital Innovation coming on
Google hits back at 'Dear Rupert' over search dominance claims
Choc Factory sniffs: 'We're not pirate-lovers - also, you publish The Sun'
EU to accuse Ireland of giving Apple an overly peachy tax deal – report
Probe expected to say single-digit rate was unlawful
Inequality increasing? BOLLOCKS! You heard me: 'Screw the 1%'
There's morality and then there's economics ...
While you queued for an iPhone 6, Apple's Cook sold shares worth $35m
Right before the stock took a 3.8% dive amid bent and broken mobe drama
EU probes Google’s Android omerta again: Talk now, or else
Spill those Android secrets, or we’ll fine you
prev story


Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Storage capacity and performance optimization at Mizuno USA
Mizuno USA turn to Tegile storage technology to solve both their SAN and backup issues.
The next step in data security
With recent increased privacy concerns and computers becoming more powerful, the chance of hackers being able to crack smaller-sized RSA keys increases.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.