Comments on: Oracle Exadata 2 capacity pricing http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/ Choices in data management and analysis Sat, 31 Jul 2010 01:41:32 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: Shrikanth http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142743 Shrikanth Wed, 07 Oct 2009 18:17:09 +0000 http://www.dbms2.com/?p=1021#comment-142743 @apex. Kevin corrected this on his post. It can exist in the cache in compressed form @apex. Kevin corrected this on his post. It can exist in the cache in compressed form

]]> By: Apex http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142703 Apex Wed, 07 Oct 2009 06:16:35 +0000 http://www.dbms2.com/?p=1021#comment-142703 >Oracle’s compression could lead to better use of RAM cache. And so it goes. Actualy it is not fuly true. Data in Oracle DB Cache exists in uncompressed form only. "In the meantime I need to point out that data flows from the intelligent storage grind into the database grid in uncompressed form when Oracle Exadata Storage Server cells are scanning (Smart Scan) Hybrid Columnar Compression tables. So, the DRAM cache capacity of the database grid is an aggregate 400 GB. *Note: Please see the blog correction above regarding how this DRAM cache is populated to achieve the advertised, effective 10TB capacity." http://kevinclosson.wordpress.com/2009/09/24/sun-oracle-database-machine-cache-hierarchies-and-capacities-part-0-i/ >Oracle’s compression could lead to better use of RAM cache. And so it goes.
Actualy it is not fuly true. Data in Oracle DB Cache exists in uncompressed form only.
“In the meantime I need to point out that data flows from the intelligent storage grind into the database grid in uncompressed form when Oracle Exadata Storage Server cells are scanning (Smart Scan) Hybrid Columnar Compression tables. So, the DRAM cache capacity of the database grid is an aggregate 400 GB. *Note: Please see the blog correction above regarding how this DRAM cache is populated to achieve the advertised, effective 10TB capacity.”
http://kevinclosson.wordpress.com/2009/09/24/sun-oracle-database-machine-cache-hierarchies-and-capacities-part-0-i/

]]> By: Oracle and Vertica on compression and other physical data layout features | DBMS2 -- DataBase Management System Services http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142621 Oracle and Vertica on compression and other physical data layout features | DBMS2 -- DataBase Management System Services Tue, 06 Oct 2009 12:19:02 +0000 http://www.dbms2.com/?p=1021#comment-142621 [...] my recent post on Exadata pricing, I highlighted the importance of Oracle’s compression figures to the discussion, and the [...] [...] my recent post on Exadata pricing, I highlighted the importance of Oracle’s compression figures to the discussion, and the [...]

]]> By: rnm1978 http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142602 rnm1978 Tue, 06 Oct 2009 07:54:53 +0000 http://www.dbms2.com/?p=1021#comment-142602 @ Jerome - isn't the metric for comparison of vendor's pricing, rather than a pricing tool for a specific implementation? I don't think the suggestion is that Oracle or Netezza will come and weigh your data and then give you a price, rather that knowing you have a 50Tb DW and are looking for a shiny new toy you can get a (very) rough idea of how much it's going to cost you from the different vendors and/or how they compare to each other. @ Jerome – isn’t the metric for comparison of vendor’s pricing, rather than a pricing tool for a specific implementation? I don’t think the suggestion is that Oracle or Netezza will come and weigh your data and then give you a price, rather that knowing you have a 50Tb DW and are looking for a shiny new toy you can get a (very) rough idea of how much it’s going to cost you from the different vendors and/or how they compare to each other.

]]> By: Jerome Pineau http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142580 Jerome Pineau Tue, 06 Oct 2009 01:05:03 +0000 http://www.dbms2.com/?p=1021#comment-142580 I always found the per-TB model to be questionable. Kinda like paying more for Word depending on how many documents you'll be handling. It seems to me, unless you know fairly precisely how much data you will ingest incrementally, it's impossible to properly map your costs over time. And I don't understand either how this pricing changes (if at all) periodically say every year. Do vendors do some sort of audit every 12 months or something? I don't know how they manage to control this. Sorry for the naive questioning; no one's ever been able to explain this to me before in any way that made sense :) I always found the per-TB model to be questionable. Kinda like paying more for Word depending on how many documents you’ll be handling. It seems to me, unless you know fairly precisely how much data you will ingest incrementally, it’s impossible to properly map your costs over time. And I don’t understand either how this pricing changes (if at all) periodically say every year. Do vendors do some sort of audit every 12 months or something? I don’t know how they manage to control this. Sorry for the naive questioning; no one’s ever been able to explain this to me before in any way that made sense :)

]]> By: Curt Monash http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142576 Curt Monash Mon, 05 Oct 2009 23:05:13 +0000 http://www.dbms2.com/?p=1021#comment-142576 The only pricing metric that the industry has unanimously settled on is dollars per purchase order. Everything else is up for grabs. The only pricing metric that the industry has unanimously settled on is dollars per purchase order.

Everything else is up for grabs.

]]> By: Jerome Pineau http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142575 Jerome Pineau Mon, 05 Oct 2009 22:54:02 +0000 http://www.dbms2.com/?p=1021#comment-142575 Oracle pricing is still indeed "rocket science"! Has the industry pretty much settled on this $/TB metric or do I get a feeling it's not a satisfactory or sufficient measure still? What is you had a database that priced dynamically based on query complexity and/or depth? Has anyone every tried something like that? Just curious as this pricing business is all very flaky to me (that's just me of course ). Oracle pricing is still indeed “rocket science”! Has the industry pretty much settled on this $/TB metric or do I get a feeling it’s not a satisfactory or sufficient measure still? What is you had a database that priced dynamically based on query complexity and/or depth? Has anyone every tried something like that? Just curious as this pricing business is all very flaky to me (that’s just me of course ).

]]> By: Curt Monash http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142572 Curt Monash Mon, 05 Oct 2009 20:09:11 +0000 http://www.dbms2.com/?p=1021#comment-142572 I read the incorrect Oracle document more recently than Kevin's blog, and forgot the conflict between them. My bad. Corrected above. I read the incorrect Oracle document more recently than Kevin’s blog, and forgot the conflict between them. My bad. Corrected above.

]]> By: Bence Arató http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142571 Bence Arató Mon, 05 Oct 2009 20:07:52 +0000 http://www.dbms2.com/?p=1021#comment-142571 Oracle's Kevin Closson explicitly states in his blog that the hybric compression method only available with Exadata storage: "Oracle Database 11g Release 2 does not offer column-store technology as thought of in the Vertica (for example) sense. The technology, available only with Exadata storage, is called Hybrid Columnar Compression. The word hybrid is important." http://kevinclosson.wordpress.com/2009/09/01/oracle-switches-to-columnar-store-technology-with-oracle-database-11g-release-2/ Oracle’s Kevin Closson explicitly states in his blog that the hybric compression method only available with Exadata storage:

“Oracle Database 11g Release 2 does not offer column-store technology as thought of in the Vertica (for example) sense. The technology, available only with Exadata storage, is called Hybrid Columnar Compression. The word hybrid is important.”

http://kevinclosson.wordpress.com/2009/09/01/oracle-switches-to-columnar-store-technology-with-oracle-database-11g-release-2/

]]> By: RC http://www.dbms2.com/2009/10/05/oracle-exadata-2-capacity-pricing/#comment-142567 RC Mon, 05 Oct 2009 18:52:06 +0000 http://www.dbms2.com/?p=1021#comment-142567 It seems that columnar hybrid compression was present in the non-exadata 11gr2 beta release but is omitted in the non-exadata production release: http://guyharrison.squarespace.com/blog/2009/9/2/columnar-compression-in-11gr2.html It seems that columnar hybrid compression was present in the non-exadata 11gr2 beta release but is omitted in the non-exadata production release: http://guyharrison.squarespace.com/blog/2009/9/2/columnar-compression-in-11gr2.html

]]>