DBMS product categories
Analysis of database management technology in specific product categories. Related subjects include:
Notes, links, and comments January 20, 2011
I haven’t done a pure notes/links/comments post for a while. Let’s fix that now. (A bunch of saved-up links, however, did find their way into my recent privacy threats overview.)
First and foremost, the fourth annual New England Database Summit (nee “Day”) is next week, specifically Friday, January 28. As per my posts in previous years, I think well of the event, which has a friendly, gathering-of-the-clan flavor. Registration is free, but the organizers would prefer that you register online by the end of this week, if you would be so kind.
The two things potentially wrong with the New England Database Summit are parking and the rush hour drive home afterwards. I would listen with interest to any suggestions about dinner plans.
One thing I hope to figure out at the Summit or before is what the hell is going on on Vertica’s blog or, for that matter, at Vertica. The recent Mike Stonebraker post that spawned a lot of discussion and commentary has disappeared. Meanwhile, Vertica has had three consecutive heads of marketing leave the company since June, and I don’t know who to talk to there any more. Read more
| Categories: About this blog, Analytic technologies, Data warehousing, GIS and geospatial, Investment research and trading, MongoDB, OLTP, Open source, PostgreSQL, Vertica Systems | 4 Comments |
Sound bites on HP/Microsoft and Neoview
HP and Microsoft put out a press release. Three new appliances are being announced, and we’re being reminded of at least one past announcement. I wasn’t briefed, and wouldn’t want to comment on, say, price/performance or feature particulars. That said:
- HP Neoview seems pretty dead.
- I haven’t heard a single favorable reference to HP Neoview since I remarked in March, 2010 that “HP Neoview is reeling.”
- A reporter asked me “What went wrong?” Well, almost any new analytic DBMS/appliance product will compete mainly on two things in its early days — price/performance (or absolute performance), and just how (im)mature it initially is. (Aster Data may be the only prominent exception to that rule.) Presumably, HP Neoview did badly by those metrics.
- HP Neoview was widely conjectured to be a pet project of ousted former HP CEO Mark Hurd.
- Nobody tells me of competing with Microsoft SQL Server 2008 Parallel Data Warehouse either (i.e. Madison/DATallegro). Thus, in particular, I haven’t heard any reason to believe there’s anything good about the technology, especially now that the ever-upbeat Stuart Frost has left Microsoft. I’m conjecturing that Parallel Data Warehouse is focused heavily on the existing Microsoft installed base.
- Speaking of Aster — even under NDA, they won’t tell me or give me any useful hints as to who their undisclosed strategic investor is. Well, HP has a long history of investing in sometimes-competing DBMS vendors (back to Oracle and Informix), and a good reason to keep quiet (reluctance to admit the end of Neoview). Hmm …
- The consolidation appliance in the HP/Microsoft announcement is a clear response to Oracle’s Exadata strategy, or (which is probably more accurate) to the same market opportunity Oracle identified.
- I couldn’t quite figure out whether the cheap data warehouse appliance included Microsoft PowerPivot support, but that would make sense if it did.
| Categories: Aster Data, Data warehouse appliances, Data warehousing, HP and Neoview, Microsoft and SQL*Server | 3 Comments |
Evolving definitions and technology categories for 2011
It seems my prediction of a limited blogging schedule in December came emphatically true. I shall re-start with a collection of quick thoughts, clearing the decks for more detailed posts to follow. Read more
| Categories: Analytic technologies, Data types, Data warehousing, DBMS product categories, MOLAP, Theory and architecture | 6 Comments |
Notes and links October 22, 2010
A number of recent posts have had good comments. This time, I won’t call them out individually.
Evidently Mike Olson of Cloudera is still telling the machine-generated data story, exactly as he should be. The Information Arbitrage/IA Ventures folks said something similar, focusing specifically on “sensor data” …
… and, even better, went on to say: Read more
Notes on data warehouse appliance prices
I’m not terribly motivated to do a detailed analysis of data warehouse appliance list prices, in part because:
- Everybody knows that in practice data warehouse appliances tend to be deeply discounted from list price.
- The only realistic metric to use for pricing data warehouse appliances is price-per-terabyte, and people have gotten pretty sick of that one.
That said, here are some notes on data warehouse appliance prices. Read more
| Categories: Data warehouse appliances, Data warehousing, Database compression, EMC, Exadata, Greenplum, Netezza, Oracle, Pricing | 8 Comments |
Quick introduction to Schooner Information Technology appliances
Back in August I talked with John Busch of Schooner Information Technology, which has a non-obvious URL. Schooner Information Technology sells Flash-based appliances that are mainly intended to run MySQL with blazing write performance.
This is one of those cases in which I warned that due to my September wave of family health issues I would cut a few blogging corners, so:
- I’m only going to write about the MySQL aspect, even though Schooner has a memcached product and claims to be able to run other NoSQL stuff as well.
- I’m not going to dig for company information beyond recalling:
- Schooner said that it has invested $20 million in R&D.
- Schooner’s appliances are resold by IBM.
- Schooner also has a direct sales force.
- One flagship customer had 30 TB of data on 17 Schooner nodes.
If Schooner wants to add some of what I’ve left out into the comments to this post, that would be great.
Schooner appliances are meant to be clustered, Read more
| Categories: memcached, MySQL, OLTP, Parallelization, Schooner Information Technology, Solid-state memory | 4 Comments |
A few notes from XLDB 4
As much as I believe in the XLDB conferences, I only found time to go to (a big) part of one day of XLDB 4 myself. In general: Read more
| Categories: Analytic technologies, Health care, Michael Stonebraker, MySQL, Open source, Parallelization, Petabyte-scale data management, Scientific research, Surveillance and privacy | 2 Comments |
Details of the JPMorgan Chase Oracle database outage
After posting my speculation about the JPMorgan Chase database outage, I was contacted by – well, by somebody who wants to be referred to as “a credible source close to the situation.” We chatted for a long time; I think it is very likely that this person is indeed what s/he claims to be; and I am honoring his/her requests to obfuscate many identifying details. However, I need a shorter phrase than “a credible source close to the situation,” so I’ll refer to him/her as “Deep Packet.”
According to Deep Packet,
- The JPMorgan Chase database outage was caused by corruption in an Oracle database.
- This Oracle database stored user profiles, which are more than just authentication data.
- Applications that went down include but may not be limited to:
- The main JPMorgan Chase portal.
- JPMorgan Chase’s ability to use the ACH (Automated Clearing House).
- Loan applications.
- Private client trading portfolio access.
- The Oracle database was back up by 1:12 Wednesday morning. But on Wednesday a second problem occurred, namely an overwhelming number of web requests. This turned out to be a cascade of retries in the face of – and of course exacerbating – poor response time. While there was no direct connection to the database outage, Deep Packet is sympathetic to my suggestions that:
- Network/app server traffic was bound to be particularly high as people tried to get caught up after the Tuesday outage, or just see what was going on in their accounts.
- Given that Deep Packet said there was a definite operator-error contributing cause, perhaps the error would not have happened if people weren’t so exhausted from dealing with the database outage.
Deep Packet stressed the opinion that the Oracle outage was not the fault of JPMorgan Chase (the Wednesday slowdown is a different matter), and rather can be blamed on an Oracle bug. Read more
| Categories: JPMorgan Chase, OLTP, Oracle | 41 Comments |
Soundbites about Mark Hurd joining Oracle
I’m on “vacation”, so I don’t know how timely I’ll be in getting back to reporters with quotes on Mark Hurd’s new job at Oracle. I put “vacation” in quotes because my father has been in a coma for over a week back in Ohio; I’m getting stonewalled for information about his and especially about my senile mother’s condition (while there’s a support structure making sure nothing too ridiculous happens, the whole thing has been even harder to block out for a while than if a full set of medical ethics were being used); Linda arrived here with an injury that has largely wrecked the vacation for her (if we had confidence in the local doctors we’d be seeing them for sure, and may yet see them anyway); and the mix of lesser factors is otherwise normal — great place, I took way too much work with me and had clients demanding more, connectivity was deplorable and is still unreliable (this post has been spread out over several hours by yet another connectivity outage), and weather has been a pleasant surprise to date (but clearly I’m benefiting from it a lot less than usual).
My thoughts on Mark Hurd (who I’ve never met) joining Oracle include:
- Mark Hurd is one of the least successful leaders in the modern history of the DBMS industry.
- Mark Hurd presided over Teradata while Teradata allowed a bunch of smaller competitors to grow up.
- Mark Hurd was said to be the prime mover behind HP Neoview, which has been an epic failure.
- Mark Hurd was in charge of HP when HP lost the Exadata business to Sun, and it’s not clear that the loss was just because Oracle bought Sun.
- Mark Hurd seems to have done poorly running services businesses at HP as well, at least in terms of their reputations.
- None of this means that Mark Hurd can’t do a good job on the volume-hardware side of Oracle. Nor does it seem likely that Hurd would get the power to gut Oracle’s R&D the way he is reputed to have gutted HP’s. And by the way, the investment in the HP Neoview fiasco shows that Hurd didn’t COMPLETELY gut R&D at HP either.
- The Mark Hurd hire is a signal that Oracle is very serious about hardware/software integration. Notwithstanding any of the foregoing, Hurd can surely talk the hardware/software integration game. And one can reasonably spin Hurd’s HP Neoview failure as a high-desire, low-odds attempt to get into the database software/hardware stack business.
- The time to assess whether Oracle will continue with the hardware/software integration emphasis will be when Mark Hurd leaves. Just as Ray Lane’s departure coincided with a reversal of the software/services integration strategy he so successfully championed, Hurd’s eventual departure could signal a backing off from emphasizing a software/hardware stack.
- Mark Hurd’s sexual harassment problems sound similar to Al Gore’s:
- He got services of the sort that are often a euphemism (massage in Gore’s case, escort in Hurd’s).
- The provider(s) just wanted to provide the real thing, not the euphemistic part as well.
- Unpleasantness ensued.
| Categories: Data warehouse appliances, Exadata, HP and Neoview, Oracle, Teradata | 12 Comments |
More on NoSQL and HVSP (or OLRP)
Since posting last Wednesday morning that I’m looking into NoSQL and HVSP, I’ve had a lot of conversations, including with (among others):