ORACLE 12.c – A Good First Step, But A Database Could And Should Be So Much More


My introduction to SQL was learning Oracle 8.x around 1996 or 97. And since that time, I have heard about Larry Ellison. Interestingly – that is around the first time I heard of Hasso Plattner too . Till then I only knew of 5 IBM engineers being the founders of SAP. I have deep respect for both the gents – they have a lot in common, despite having such different personalities. Of course I have only seen Hasso at close quarters, not Larry. Having worked at IBM for many years, I also have the greatest respect for the DB engineers and researchers there.

When SAP entered DB market seriously with Hana – my first thought was that it was a terrible idea. DB is the stickiest part of the stack at customers. I also remembered being tutored in IBM by the sales leaders that if you own the lowest levels of the stack – like HW, OS , DB and middleware, you own the account for ever. What I did not know at that time was that SAP’s plan was not to be yet another DB vendor – they wanted to change how DB works fundamentally. SAP wanted to play offense in a game that had moved on to heavy defense as the winning strategy. That is not just a sales and marketing thing – it needed a level of engineering that is extremely sophisticated. I was sufficiently convinced that SAP had a real chance of changing the market – and I bet my livelihood on it.

IBM is a great place to get trained in enterprise software. I learned from my first year there that all competitors have to be respected, but none should ever be feared. Competition is the best thing about this industry – keeps everyone on their productive best. Few months ago, IBM came up with DB2 BLU and now ORACLE has come out with 12c. I think both are good moves and both companies will use it to try and negate the impact of SAP Hana. And this is great validation of SAP’s strategy to change how DB should work. What is also not too surprising is that Oracle and IBM chose incremental steps to find some common ground with Hana – rather than go all out. For one – this fits well with their strong defensive strategy of protecting existing instal base, and two it needs a level of engineering that takes more time than what they had since they realized SAP made the right bets. But all things said and done – still a good move that is positive for the enterprise software market.

I give Oracle full marks on messaging – I thought it was absolutely brilliant to say “don’t need to change anything, just flip a switch and reap the benefits of in-memory DB”. That is a simple and elegant message. And it is not trivial to come up with such good messages. It is very easy to understand and appreciate at a high level. Nicely done.

Ellison did say many things in his keynote that Hasso and Vishal from SAP have been saying for years – why RAM is faster, why columnar DBs work better and all of that. All of which are good statements, and he has the credibility to say these things about databases. He definitely was in his elements talking about databases – and I enjoyed watching it. It was also a nice change of pace from the opening act from Fujitsu.

SAP Hana is fast and it is in memory, and it is column based – and looks like 12c does all of this too in some way. But that is just a fraction of what makes Hana special. SAP views Databases very differently from Oracle. HANA is a full fledged platform – which supports all types of processing with one copy of data . Not only does it store data in memory and in columns, it pushes down processing closer to data – and reduces the number of physical layers needed traditionally in an application. It has built in libraries for predictive and statistical functions. It has built in app server and web server. HANA can seamlessly integrate with other big data systems like Hadoop. That is a long winded way of saying – a database can and should be so much more. SAP showed it can be done in one system without needing to club together many different applications – at multiple productive customer projects, not in some proof of concept labs environment.

Oracle could have done a lot more – but chose to just do only very little. I am sure they have the engineering brilliance to do more, and a sales force who could have made use of such innovation. That is disappointing for the techie in me – and I hope they do way more in future and push the envelope on what a DB can do.

I was also kind of confused on why Oracle chose to do Column and row stores with multiple copies of data (unless I misunderstood what Larry said in the keynote). Enterprises already can’t deal with the many redundant copies of data – why would you add to that problem with a “modern” solution?

I have more questions – why is OLTP faster now ? What is the behavior of the system when it starts up ? What happens when there is not enough memory – will it use disk ? What happens when an app needs data in rows and columns ? How much of DBA effort is needed – how smart is the system in deciding what goes into memory and what does not? how much does this “switch” cost a customer? and many more. I am hoping that more details will be available through the conference, or in the weeks that follow. I am hoping there are good logical answers to all of these details.

There were two general types of questions on twitter after the keynote – will be now see a Hana vs Oracle bake off on speed ? and will 12c slow down hana deals and put pricing pressure on hana ? I think both are genuine questions worth asking .

If 100X performance is all 12c is capable of, then we probably won’t need to do any bake offs. There are enough customers who have way more performance gains with Hana than 100X. In any case – raw speed is only one part. What you do with that speed is what happens – and Hana has applications purpose built to exploit the speed – using the other capabilities in Hana like predictive and geospatial cpabilities for example. And given the head start Hana has over 12c, it is hard to imagine Oracle catching up in incremental steps like it seems to be doing.

On slowing down deals and pricing pressure – I have no idea given I don’t work in sales. Nor do I make sales or pricing decisions for SAP. However, from past sales experience – I think this is a factor of how well Oracle and SAP can educate their customers on the technology options. I will definitely be curious to see how it plays out in market. Customers do not buy on technology merit alone – I know that well. Given Hana grew pretty fast and has thousands of customers in last 2 years, I doubt customers will have any issues in seeing its value proposition.

Oracle is a great competitor and will not just sit back and watch hana eat its lunch – as an engineer, I just hope that they bring in some serious innovation to database technology, to back up its messaging. I will be the first to stand up and applaud if they do that. And for SAP, I am sure the intention is to continue to try as hard as we can to maintain and increase the lead on innovation front.

When Applications Scream “I don’t Trust You”


Between telecons today, I was glancing through twitter and had a brief chat there with Ben Haines, the CIO of Box.
See below.

20130920-084051.jpg

Just reminded me of a few phone calls I have had from the expense police in past life

Expense Police :Can you explain why you tipped $10 more than 15% at dinner ?
Moi : err- because the client loved the service at the dinner I took him to and let me get away with a missed milestone which would have cost the company a few thousand dollars

Expense Police : I need a daily exchange rate breakup for your claims for Germany trip last month. If you can’t respond in 2 hrs , I will deny the claim and you have to raise a new claim later
Moi : sure – let me step out of this stupid negotiation with CIO for a $30M deal right away and go find the exchange rates for you for my $5000 claim

3. Expense Police : I am denying the $2K air ticket because you didn’t attach a manager approval note

Moi : sorry – I made the assumption that the General Manager 3 levels above my boss had the authority to approve the travel and only attached his approval . Let me call and yell at him for aiding and abetting a willful negligence of company policy by me

4. Expense Police : I will let the first 3 things slide this time based on your explanation. But this is the last time and I will have to notify your manager

Moi : Much appreciated. I will let my manager know so that he can prepare his manager for his call with you for his own expenses

5. Expense Police : Remember I told you I will pass your claims this time? Well, we cannot do that. The system does not allow us to do that. So I am denying the claim.

Moi : OK – I am sure the system has good reasons to do it, given it is more intelligent than both of us. Does the system accept thank you notes or flowers that I can send to mark my appreciation?

I will stop here – there are a dozen more along these lines .

I would be hard pressed to find an application that is more universally loathed than expense apps .
Why is it so ?

Mostly because the fundamental thinking behind corporate expenses is. “Trust no one”. Everyone from CEO to Janitor are out there to cheat the company on expense reports apparently . Put as many obstacles in the way – and we can find that one bad guy amongst the thousands of employees and contractors.

Second , legal frame work is stuck in the 1950s . There are places where you can claim electronically with a nice iPhone app but you need to mail in receipts . A paradigm of productivity and efficiency , eh ?

Last, apps get built by people who don’t travel and hence have limited knowledge of how traveling employees live and pay .

I know many including me wanted job promotions in past strictly because then you can offload expense reports to an assistant . But every time I give a bunch of receipts to my EA , I feel rather sorry for her . I hope she doesn’t get as many calls from the expense police .

Zero Inbox Strategy – To Be Or Not To Be ?


I have a zero inbox policy . I read every email I get within a short time of it showing up , respond to the ones that need attention then move them to an archive . I don’t go to bed till I am done . And I have been this way for about 8 years .I don’t let my assistant reply to my emails , although she has access to it .I have the same zero inbox policy on personal email and twitter too . In that aspect , I was “real time” friendly before real time became the new black 🙂

It has its advantages that I can reasonably stay on top of my work , given the high volume of emails I get. In general it has definitely helped me with career success and progression too .

However , there is a big price to pay to keep this habit. And I will be lying if I say I enjoy this habit a lot . A more accurate statement will be that I have high tolerance now 🙂

For starters – it means I stay up late every night , including most weekends . Even on vacations I try to stay up late to finish email some times – which irritates my family to no end . If I don’t – I will never catch up with the back log . I kid you not – I had to once lock my smartphone in a bag and leave the key out of sight to stop looking at email during vacation.

It also means I very rarely write long , well crafted emails . I usually respond in one sentence or two – and it occasionally comes across as harsh or non caring to people who don’t know me . I am however a tad more careful when I email customers – but even there , I stay brief . In general – people need a bit of time to get used to my ultra brief emails with rarely any salutation or signature 🙂 . Thankfully – my boss is also a fan of brief emails .

One lesson I learned early in my career was to not rely on email for all communication . I use chat functionality and phone heavily , and that minimizes the email traffic . I also like to do face to face communication with others whenever possible . On the bad side – you might not have anything documented if memory fails you about a phone call . So for important stuff – I try to send a short summary via email .

I also use a separate email id for Internet stuff that has even a remote chance of spamming me in future . And of course I rarely open that account . If anyone spams me intentionally more than once – I block them . This is especially a problem with personal friends and relatives who will get offended quickly.

With my team, I encourage them to use the phone as much as possible and then just send one email in summary . It doesn’t always work – given I never had the same team working for me for several years at a stretch . So we relearn together periodically 🙂

I also don’t create a complex folder structure for my archive . I trust search more than my organizational skills . However , search is as much an art as a science – so occasionally I get some serious grief . For that matter , I don’t use flags or color coding or anything of that sort . This is probably why I think BI should also largely move to search as primary interface 🙂

Some emails always will fall through the cracks – given my frequent archival . I try to be careful , but I make mistakes . But the good thing is that if it was important – I would get a reminder most of the time . Again, if the email is from a customer – I try to be twice as careful , but of course I occasionally miss those too.

I do let my EA handle my calendar almost exclusively . I am terrible at that – and she is very good with that . So I just follow her lead and will only mess with it if something comes up when she is not working . I refer to her as my life saver .

So for all the good things I get out of having a zero inbox – and all the discipline I follow to keep it that way, there is one thing that I have no control over . Since I respond near real time – it gives the wrong idea to some people that I am “always on”. And some of them will get offended if I read but do not respond quickly at 2 AM . I have tried many different things – but no good scalable solution has been found yet .

So that brings me back to why I wrote this now – is it worth keeping up with zero inbox policy and the stress that comes with it? Or should I relax and let it slide ? That will be something I will think about in 2 weeks time when we leave for an island vacation . Last year when we went to Hawaii is when I decided to quit my job at IBM . I wonder whether I will decide to stop the zero inbox policy this trip . The decision kind of has similar magnitude in my mind 🙂

If any one has any tips, suggestions , wise cracks et al – let me know .