Comments on: So what does Oracle Exadata mean for HP Neoview? http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/ Choices in data management and analysis Thu, 09 Feb 2012 13:48:12 +0000 hourly 1 http://wordpress.org/?v=3.0.3 By: Curt Monash http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-111757 Curt Monash Sat, 28 Feb 2009 20:40:53 +0000 http://www.dbms2.com/?p=575#comment-111757 a hayes, What is your experience with Neoview? a hayes,

What is your experience with Neoview?

]]> By: a hayes http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-111751 a hayes Sat, 28 Feb 2009 19:33:12 +0000 http://www.dbms2.com/?p=575#comment-111751 Neoview will be a failure. It fails to perform, runs queries slower than Teradata, and will in due course be scrapped by HP. Neoview will be a failure. It fails to perform, runs queries slower than Teradata, and will in due course be scrapped by HP.

]]> By: Infology.Ru » Blog Archive » Итак, что означает Oracle Exadata для платформы HP Neoview? http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98921 Infology.Ru » Blog Archive » Итак, что означает Oracle Exadata для платформы HP Neoview? Thu, 09 Oct 2008 18:59:37 +0000 http://www.dbms2.com/?p=575#comment-98921 [...] Автор: Curt Monash Дата публикации оригинала: 2008-09-26 Источник: Блог Курта Монаша [...] [...] Автор: Curt Monash Дата публикации оригинала: 2008-09-26 Источник: Блог Курта Монаша [...]

]]> By: HP Neoview in the market to date | DBMS2 -- DataBase Management System Services http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98308 HP Neoview in the market to date | DBMS2 -- DataBase Management System Services Thu, 02 Oct 2008 09:22:22 +0000 http://www.dbms2.com/?p=575#comment-98308 [...] evidently got HP’s attention by a recent post in which I questioned its stance on the relative positioning of the Exadata-based HP Oracle data warehouse appliance and [...] [...] evidently got HP’s attention by a recent post in which I questioned its stance on the relative positioning of the Exadata-based HP Oracle data warehouse appliance and [...]

]]> By: Vincent McBurney http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98182 Vincent McBurney Tue, 30 Sep 2008 01:41:53 +0000 http://www.dbms2.com/?p=575#comment-98182 The question for the Neoview team is whether HP EDS and Knightsbridge architects and proposal teams are going to recommend Oracle or Neoview. In a competitive evaluation and bidding situation they are unlikely to propose both. My guess is that Oracle will be recommended for Oracle shops and Neoview recommended elsewhere and that Neoview has lost about 40% of it's potential market. The question for the Neoview team is whether HP EDS and Knightsbridge architects and proposal teams are going to recommend Oracle or Neoview. In a competitive evaluation and bidding situation they are unlikely to propose both. My guess is that Oracle will be recommended for Oracle shops and Neoview recommended elsewhere and that Neoview has lost about 40% of it’s potential market.

]]> By: Curt Monash http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98146 Curt Monash Mon, 29 Sep 2008 11:54:13 +0000 http://www.dbms2.com/?p=575#comment-98146 Jef, My rule of thumb is that Teradata's actual users usually love Teradata, but their bosses who sign the checks sometimes hate Teradata. You seem to be an exception to that rule -- not that it ever was 100% true anyway :)-- which is a valuable contribution. So thanks for speaking up! CAM Jef,

My rule of thumb is that Teradata’s actual users usually love Teradata, but their bosses who sign the checks sometimes hate Teradata. You seem to be an exception to that rule — not that it ever was 100% true anyway :) – which is a valuable contribution. So thanks for speaking up!

CAM

]]> By: jef http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98140 jef Mon, 29 Sep 2008 08:09:08 +0000 http://www.dbms2.com/?p=575#comment-98140 as a user of teradata system for more than 15 years, I just want to tell you guys to stop promoting things that you don't know!!! if you don't have teradata balanced configuation then teradata is not better than oracle (et all)! shared nothing obviously not good in heavy joining (PIs are not located in the same node!need to redistribute rows)...full table scan could be the only a differentiator for teradata in a big config...what is the cost of that? as a user of teradata system for more than 15 years, I just want to tell you guys to stop promoting things that you don’t know!!! if you don’t have teradata balanced configuation then teradata is not better than oracle (et all)! shared nothing obviously not good in heavy joining (PIs are not located in the same node!need to redistribute rows)…full table scan could be the only a differentiator for teradata in a big config…what is the cost of that?

]]> By: Curt Monash http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98101 Curt Monash Sun, 28 Sep 2008 19:24:30 +0000 http://www.dbms2.com/?p=575#comment-98101 Carl, With the possible exception of DB2, none of those has supported the I/O to query large amounts of data quickly. Exadata proposes to change that in Oracle's case. DB2 hasn't covered itself in glory at the super high end of database sizes either, but I'm not totally clear on why. CAM CAM Carl,

With the possible exception of DB2, none of those has supported the I/O to query large amounts of data quickly. Exadata proposes to change that in Oracle’s case.

DB2 hasn’t covered itself in glory at the super high end of database sizes either, but I’m not totally clear on why.

CAM

CAM

]]> By: Carl http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98095 Carl Sun, 28 Sep 2008 15:39:01 +0000 http://www.dbms2.com/?p=575#comment-98095 CAM, I’ll buy into your concurrency and mixed workload definitions (although there are some slight ambiguities). Now I’ll get back to the “big query” question and why you think that Oracle cannot run big queries fast. Is the issue one of architecture (e.g., row versus column storage) or of a poor query optimizer? I infer from this and your other posts that you consider it to be more the latter. I ask whether you consider any of the following row-based RDBMSs to be bad/so-so/good with respect to big queries: MS SQL Server, IBM DB2, Sybase ASE, and Sybase ASA? (I'll leave it you as to which releases/platforms you are familiar with. I know that ASE 15.0.2 is generally faster than 12.5.x but sometimes is slower.) Thank you, Carl. CAM,

I’ll buy into your concurrency and mixed workload definitions (although there are some slight ambiguities). Now I’ll get back to the “big query” question and why you think that Oracle cannot run big queries fast. Is the issue one of architecture (e.g., row versus column storage) or of a poor query optimizer? I infer from this and your other posts that you consider it to be more the latter. I ask whether you consider any of the following row-based RDBMSs to be bad/so-so/good with respect to big queries: MS SQL Server, IBM DB2, Sybase ASE, and Sybase ASA? (I’ll leave it you as to which releases/platforms you are familiar with. I know that ASE 15.0.2 is generally faster than 12.5.x but sometimes is slower.)

Thank you, Carl.

]]> By: Curt Monash http://www.dbms2.com/2008/09/26/so-what-does-oracle-exadata-mean-for-hp-neoview/#comment-98029 Curt Monash Fri, 26 Sep 2008 23:25:16 +0000 http://www.dbms2.com/?p=575#comment-98029 Carl, Concurrency problems arise when the resources required to run a bunch of simultaneous queries are significantly more than the sum of the resources that would be required to run them one after the other. Mixed workloads are ones in which the concurrent queries have very different characteristics. Big queries are ones that, for example, scan huge tables or join medium-to-huge tables with each other, or do large numbers of joins. Smaller ones might do a SELECT on a single table, or just join a couple of non-huge ones, generating a report. Query volumes of small queries are commonly higher than volumes of big ones. One may populate 100s of dashboards at once. One probably is not going to run 100s of data mining extracts at the same moment. CAM Carl,

Concurrency problems arise when the resources required to run a bunch of simultaneous queries are significantly more than the sum of the resources that would be required to run them one after the other.

Mixed workloads are ones in which the concurrent queries have very different characteristics.

Big queries are ones that, for example, scan huge tables or join medium-to-huge tables with each other, or do large numbers of joins. Smaller ones might do a SELECT on a single table, or just join a couple of non-huge ones, generating a report.

Query volumes of small queries are commonly higher than volumes of big ones. One may populate 100s of dashboards at once. One probably is not going to run 100s of data mining extracts at the same moment.

CAM

]]>