Analytics’ role in a frightening economy
I chatted yesterday with the general business side (as opposed to the trading operation) of a household-name brokerage firm, one that’s in no immediate financial peril. It seems their #1 analytic-technology priority right now is changing planning from an annual to a monthly cycle.* That’s a smart idea. While it’s especially important in their business, larger enterprises of all kinds should consider following suit. Read more
| Categories: Analytic technologies, Application areas, Business intelligence, Cognos, Data warehousing, IBM and DB2, MOLAP | Leave a Comment |
Final (for now) slides on how to select a data warehouse DBMS
I’ve now posted a final version of the slide deck* I first posted Wednesday. And I do mean final; TDWI likes its slide decks locked down weeks in advance, because they go to the printer to be memorialized on dead trees. I added or fleshed out notes on quite a few slides vs. the prior draft. Actual changes to the slides themselves, however, were pretty sparse, and mainly were based on comments to the prior post. Thanks for all the help!
*That’s a new URL. The old deck is still up too, for those morbidly curious as to what I did or didn’t change.
| Categories: Buying processes, Data warehousing, Presentations | 14 Comments |
Draft slides on how to select an analytic DBMS
I need to finalize an already-too-long slide deck on how to select an analytic DBMS by late Thursday night. Anybody see something I’m overlooking, or just plain got wrong?
Edit: The slides have now been finalized.
Winter Corporation on Exadata
The most ridiculous analyst study I can recall — at least since Aberdeen pulled back from the “You pay; we say” business — is Winter Corporation’s list of large data warehouses. (Failings include that it only lists warehouses run by software from certain vendors; it doesn’t even list most of the largest warehouses from those vendors; and its size metrics are in my opinion fried.) So it was with some trepidation that I approached what appears to be an Oracle-sponsored Winter Corporation white paper about Exadata.* Read more
| Categories: Data warehouse appliances, Data warehousing, Exadata, Oracle | 5 Comments |
EMC’s take on data warehousing and BI
I just ran across a December 10 blog post by Chuck Hollis outlining some of EMC’s — or at least Chuck’s — views on data warehousing and business intelligence. It’s worth scanning, a certain “Where you stand depends upon where you sit” flavor to it notwithstanding. In a contrast to my usual blogging style, Chuck’s post is excerpted at length below, with comments from me interspersed. Read more
| Categories: Analytic technologies, Data warehousing, EMC, MOLAP, Solid-state memory, Storage | 2 Comments |
Oracle Exadata article — up at last
I’d been promising Intelligent Enterprise editor Doug Henschen an article on Oracle Exadata for months. It’s finally up. For a variety of reasons, it was a lot more work than one might at first guess. One such reason is that it spawned four related blog posts over the past few days.
As I post this, there are two glitches in the article. One is that em dashes are appearing as quote marks — and as you know, I use a lot of em dashes. The other is that one sentence on in-database data mining seems unclear to me, and I’ve asked for a small edit to make it clearer what I’m talking about. No doubt both will be cleared up soon. Edit: Doug indeed fixed all that within minutes.
This is an edited article. Other than columns, it may be my first such since the Upside Magazine cover story on AOL over a decade ago. But it was edited with a light and skillful touch. Please don’t hold me responsible for every minor subtlety of emphasis or grammatical nuance. But otherwise I stand behind the opinions, for they are indeed mine.
| Categories: About this blog, Data warehouse appliances, Exadata, Oracle | 1 Comment |
I’ll be answering e-mail again soon
I’ll be answering e-mail again soon, from clients, PR folks, and my mother alike. Ditto blog comments and Twitter direct messages. And I’ll close out on the inessential deadlines I missed for TDWI. I’ve been a little busy, as you may be gathering.
Now just put those pitchforks down gently, and back away slowly …
| Categories: About this blog | 1 Comment |
One vendor’s trash is another’s treasure
A few months ago, CEO Mayank Bawa of Aster Data commented to me on his surprise at how “profound” the relationship was between design choices in one aspect of a data warehouse DBMS and choices in other parts. The word choice in that was all Mayank, but the underlying thought is one I’ve long shared, and that I’m certain architects of many analytic DBMS share as well.
For that matter, the observation is no doubt true in many other product categories as well. But in the analytic database management arena, where there are literally 10-20+ competitors with different, non-stupid approaches, it seems most particularly valid. Here are some examples of what I mean. Read more
| Categories: Aster Data, Data warehousing, Exadata, Kognitio, Oracle, Theory and architecture, Vertica Systems | 22 Comments |
Oracle says they do onsite Exadata POCs after all
When I first asked Oracle about Netezza’s claim that Oracle doesn’t do onsite Exadata POCs, they blew off the question. Then I showed Oracle an article draft saying they don’t do onsite Exadata proofs-of-concept. At that point, Oracle denied Netezza’s claim, and told me there indeed have been onsite Exadata POCs. Oracle has not yet been able to provide me with any actual examples of same, but perhaps that will change soon. In the mean time, I continue with the assumption that Oracle is, at best, reluctant to do Exadata POCs at customer sites.
I do understand multiple reasons for vendors to prefer POCs be done on their own sites, both innocent (cost) and nefarious (excessive degrees of control). Read more
| Categories: Benchmarks and POCs, Buying processes, Data warehouse appliances, Data warehousing, Exadata, Oracle | 10 Comments |
Simplicity in analytic database management systems
Ideally, administering a relational database management system should be simple — describe the tables, load the data, and rely on the system to take care of everything else. Complexity comes primarily in two (somewhat overlapping) forms:
- Manual steps required for the system’s regular operation, that in principle could be automated away, but actually haven’t been.
- Manual steps need to tune the system for performance.
Vendors whose products shine in one of those areas but not in both tend to claim greater advantages in “simplicity” than they actually possess. And the list of such vendors is long, because there’s something of a negative correlation between excellence in the two metrics, often because:
- Older products tend to require more tuning, but tend to have more mature automation tools.
- Newer products often need less tuning, but might not yet have all their tools up to snuff.
| Categories: Analytic technologies, Data warehousing | 2 Comments |