IBM admits Oracle's Big Data Appliance, Exadata, Database and Exalytics are central to your big data strategy

By -

Not often I agree with IBM but thanks for the name-check and confirmation that our big data strategy is the best way forward for customers: http://www.enterpriseappstoday.com/business-intelligence/7-enterprise-friendly-ways-of-dealing-with-big-data.html

In an interview in Enterprise Apps Today online magazine, former Forrester Research analyst and current IBM Big Data evangelist James Kobielus said:

"This is where Hadoop MapReduce — which Kobielus calls the real “core” of Hadoop — comes into play. “What MapReduce represents is the industry’s first-ever vendor-agnostic framework for building a broad range of advanced analytics. What we think of as advanced analytics is supported within this sort of abstraction framework for development called MapReduce.”

After the data is transformed, it’s fed downstream into another database, such as an Oracle Exadata data warehouse or OLAP cubes, or even to an in-memory platform such as Oracle Exalytics"

Nice to know that IBM is advising its customers to put Oracle technology at the center of their big data strategy rather than their own DB2 based Smart Analytics platform. Of course this is not surprising given that Gartner reported in its last EDW MQ report that approx. 60% of IBM's own customers would not consider deploying DB2 for their data warehouse.

It was nice to see IBM call out two key features that business users are always looking to help them with their analysis: 1) multi-dimensional models that make data navigation and complex analytics very easy and 2) in-memory analytics so you can have speed-of-thought data exploration. Of course IBM does not offer these features which I suspect is why they are recommending customers use Oracle.

If you are an IBM customer and want to get started with big data then welcome to Oracle and the start of your big data journey. You can find more information about our big data platform (Big Data Appliance, Exadata and Exalytics) here: http://www.oracle.com/bigdata.

Comments

Post a Comment

Popular posts from this blog

My query just got faster - brief introduction to 12.2 in-memory cursor duration temp tables

By -
Image
Image courtesy of wikipedia This post covers one of the new SQL performance enhancements that we incorporated into Database 12c Release 2 . All of these enhancements are completely automatic, i.e. transparent to the calling app/developer code/query. These features are enabled by default because who doesn’t want their queries running faster with zero code changes? So in this post I am going to focus on the new In-Memory “cursor duration” temporary table  feature. Let’s start by looking at cursor duration temp tables… Above image courtesy of wikimedia.org What is a cursor duration temp table? This is a feature that has been around for quite a long time. Cursor duration temporary tables (CDTs) are used to materialize intermediate results of a query to improve performance or to support complex multi step query execution. The following types of queries commonly use cursor duration temp tables: WITH Clause and parallel recursive WITH Grouping Sets S...
Keep reading

SQL Pattern Matching Deep Dive - Part 1

By -
Image
There has been quite a lot of interest in the new 12c MATCH_RECOGNIZE feature for SQL pattern matching. Therefore, I thought now would be the perfect time to start a series of quick deep dive posts that explain how SQL pattern matching works. Over the coming weeks I will cover the following topics in a series of posts. This is the start of a series of posts based on a presentation that I put together for the recent annual  BIWA conferenc e at Oracle HQ. The Oracle BI, DW and Analytics user community always puts on a great conference and this year was the best yet. You can download any or all of the presentations from this year’s conference by following this link . My pattern matching deep dive presentation started life about a year ago as a post covering some of the new keywords in the explain plan that are linked to pattern matching, see here . It has now expanded to cover a much wider range of topics. Firstly, a huge vote of thanks to my development team (Lei Sheng and Chun-Chie...
Keep reading

SQL Pattern Matching Deep Dive - Part 6, state machines

By -
Image
The obvious way to start this particular post is to pose a couple of simple questions: what is a state machine and why should you care? In general I would say that you don't need to know about or care about state machines. That's the beauty of using SQL for pattern matching. The MATCH_RECOGNIZE clause encapsulates all the deep technical modelling and processing that has to be performed to run pattern matching on a data set. However, there are times when it is useful, probably vital, that you understand what is going on behind the scenes and one of the most obvious situations is when backtracking happens. Therefore, the content covered in this post is a going to be a gently lead-in into my next post where I am going to discuss the concept of “backtracking”  and the dreaded  ORA-30009 error. Let’s start our voyage of discovery…when you attempt to run a SQL statement containing a MATCH_RECOGNIZE clause during the compilation phase we generate a finite state machine ba...
Keep reading