And during the conference, SAP senior executive Steve Lucas announced that he intends SAP to be the #2 database vendor by 2015. It wasn't a throwaway comment and hyperbole is not Steve's way. He was clear on who this meant overtaking and clear on this difficulty of this journey. But is this realistic, or just pie in the sky?
For those who don't completely understand: SAP HANA is a next-generation database. At a 30,000ft level it can do anything that Oracle, IBM or Microsoft can do, but hundreds or thousands of times faster, because it runs in the main memory of a computer system rather than on slow spinning disks. I've used it and it does exactly what it says on the tin.
Why doesn't SAP HANA have deeper market penetration?
Put simply it is because SAP wanted it this way. Whilst HANA truly is a general-purpose database, SAP first announced it as an analystics appliance for the 1.0 release. They also priced it really high and didn’t' offer a discount – list pricing can be as high as €180,000 for a 64GB HANA "unit", depending on which version you require.
And what's more, SAP sells solutions and HANA is a platform, so the global salesforce doesn't quite know how to sell it in volume - yet. They didn't want to sell it in volume in any case because they wanted to introduce it slowly to market – building stability, references along the way and avoiding expensive and embarrassing global escalations.
So by the end of 2011 we should expect $100-150m of HANA sales, which is 3-5% of SAP's total revenue. Not particularly significant, right? Well in September they released HANA as being supported for SAP's Business Warehouse software, which allows large-scale data warehouses. And this is where it gets interesting: there are 17,000 existing BW customers, and HANA would provide business benefit to all of them.
What is the wider market opportunity for SAP HANA?
It starts with the SAP BW product, which has 17,000 customers. HANA can replace the database that BW runs on – which is typically from Oracle, IBM or Microsoft. The benefits of this are huge – much faster reporting, data loads, far better agility and a better business experience overall. HANA literally transforms SAP BW.
But that is just the start because the fact that BW runs on HANA means that SAP can allow any of its software to run with HANA – replacing the existing database. And how quickly it chooses to allow this is a factor of how quickly it decides that HANA is mature enough to do this. Larry Ellison from Oracle claimed that there is no in-memory database anywhere near to being able to run as the database for a transactional system at the beginning of 2011. HANA has not yet proven that it is ready yet, but this is exactly what SAP intends.
And even that is just the tip of the iceberg. Because let's be clear: HANA can be used for anything. It supports industry standard connections like ODBC and JDBC and anything that runs a database can be run on HANA – just much faster than ever before. Other vendors have in-memory technologies but the way HANA is designed means it is much more general-purpose than what Oracle and IBM have to offer.
So what is possible by 2015?
Well this is the billion dollar question. From a personal perspective I am deeply impressed with what SAP have done with HANA in 2011. It has gone from being vapourware (January) to being a real product on the price list (July) - albeit immature. And by September a second – much more mature – release was released to market that supports BW. That's an enormous amount of progress in 12 short months.
And I already have projects underway that use HANA as a general purpose database for things like the Sybase Unwired Platform – enabling real-time enterprises with iPads, providing decision making on the move based on events that happened seconds before. There's no doubt that the technology has huge potential. The question is – what happens next, and how fast?
It also depends what you mean by #2 database vendor. For example Oracle say they are the #1 SAP database vendor. Yes – they have the most large systems. Microsoft claim the same, because they have the most customers (a lot of smaller customers run Microsoft). And guess what, IBM claim the same – because IBM have the biggest SAP databases. SAP are going to have to be clear when they explain what they mean by #2.
But based on what I've seen – expect early ERPs to be supported by SAP in 2012 – including the BusinessOne ERP suite – ERP lite, if you like, designed for organisations with 1-100 employees. Expect SAP's SME (10-1000 employee) ByDesign cloud suite to run on HANA and also expect HANA to support standards: because today whilst HANA supports ODBC and JDBC, it does not support 3rd party systems to connect directly into this.
In 2012 we should also expect to see proper support for larger (>1TB databases). HANA compresses around 10:1 to 5:1 compared to other databases so 1TB is 5-10TB of standard database, but it hasn't really been proven to scale properly yet. Expect to see this happen in 2012, as well as scenarios that require disaster recovery and other technical stuff like integration with enterprise monitoring suites like Tivoli.
Why is SAP taking its sweet time?
It seems to be that the answer is pretty simple. The last major database to go to market was Microsoft in the mid-90s with SQL Server. They made an acquisition and it was still awful until the release in 2000. SAP doesn't want this stigma and is therefore phasing the rollout, making the software expensive and thereby limiting the number of customers.
For example there was no shortage of customers out of the 17,000 to join the NetWeaver BW early adoption program that SAP calls Ramp-Up. But there were 50 slots and those were easily filled with customers who had realistic projects that would go live. Little by little they build references, quality software and trust within the customer base – but not growing so fast that there are major project failures. There have been a few instances where HANA was oversold in the early days and those projects were managed carefully – directly by the SAP leadership team.
Projects that use HANA as an ERP database have been deliberately avoided, as SAP Chief Technology Officer Vishal Sikka told me. He described how if Porsche's BW data warehouse were to stop working, they would raise a priority support call and SAP would sort it out. However if their ERP system stopped working and production of cars ceased, he would get a personal phone call from a board member.
So in 2013 expect support for the ERP suite to start to come. And by then, HANA will be sold for every conceivable scenario through 2014 and 2015. And the interesting thing is I don't believe that a killer scenario exists for HANA yet, because all the scenarios right now are really about doing what you do today, but faster. Let's start thinking about what you can't do today – and might give you a huge competitive advantage.
And can SAP be the #2 database vendor by 2015? Really?
Honestly I'm not sure, but it is definitely the right goal. HANA isn't about high-performance analytics – it's about changing the way that customers do business, with a technology enabler. For this reason, SAP have to be looking at going after the database market – and helping customers get a huge competitive advantage along the way.
I honestly suspect that the biggest challenge that SAP have along this way is enabling the salesforce to educate customers on how beneficial it would be – because the SAP salesforce is aligned around industry verticals and Lines of Business. A global reorganisation is underway to change this, and the way that HANA is explained and sold is at the core of this, but HANA is a platform and will need to be sold as such. That is a serious piece of organisational change for SAP and shouldn't be underestimated.
Regardless of whether Steve's goal is met or not, SAP HANA is perhaps one of the most interesting technologies I have seen in my 14 years of working in Enterprise IT, and well worth serious consideration, whatever business you run. If you are a SAP customer I would go a step further and say that you should look at building your HANA roadmap, based on your business imperatives compared to the product maturity and availability roadmap.
Disclosure: SAP paid for John's travel and expenses to the Influencer Summit in Boston. Mine, too, btw, and SAP is a client of mine (Dennis).