Comments on: Competitive issues in data warehouse ease of administration http://www.dbms2.com/2006/09/22/competitive-issues-in-data-warehouse-ease-of-administration/ Choices in data management and analysis Fri, 29 Aug 2008 04:11:32 +0000 http://wordpress.org/?v=2.5.1 By: Roger Gaskell, Kognitio http://www.dbms2.com/2006/09/22/competitive-issues-in-data-warehouse-ease-of-administration/#comment-7893 Roger Gaskell, Kognitio Wed, 27 Sep 2006 14:52:46 +0000 http://www.dbms2.com/2006/09/22/competitive-issues-in-data-warehouse-ease-of-administration/#comment-7893 WX2 from Kognitio takes ease of use even further. Like Netezza and DATAllegro WX2 does not use any indices. but it also does not require any pre-partitioning of the data. Data is randomly distributed across all nodes in the system. At data load, this process is completely automatic, no input is required from the DBA. When a query is executed that requires data to co-exist on a node other than the one it was loaded on, WX2 will automatically re-distribute only the parts of the data required to satisfy the query, into memory, in such a way that the data is now correctly co-located. Because the re-distribution is to memory not disk this process is very fast and all subsequent database operations are performed "in-memory". WX2 uses very sophisticated data streaming techniques to ensure that queries do not run out of memory no matter how much data is involved. Roger Gaskell Kognitio WX2 from Kognitio takes ease of use even further.

Like Netezza and DATAllegro WX2 does not use any indices. but it also does not require any pre-partitioning of
the data. Data is randomly distributed across all nodes in the system. At data load, this process is
completely automatic, no input is required from the DBA.

When a query is executed that requires data to co-exist on a node other than the one it was loaded on, WX2
will automatically re-distribute only the parts of the data required to satisfy the query, into memory,
in such a way that the data is now correctly co-located.

Because the re-distribution is to memory not disk this process is very fast and all subsequent database
operations are performed “in-memory”.

WX2 uses very sophisticated data streaming techniques to ensure that queries do not run out of memory no
matter how much data is involved.

Roger Gaskell
Kognitio

]]> By: Stuart Frost http://www.dbms2.com/2006/09/22/competitive-issues-in-data-warehouse-ease-of-administration/#comment-7722 Stuart Frost Tue, 26 Sep 2006 16:50:20 +0000 http://www.dbms2.com/2006/09/22/competitive-issues-in-data-warehouse-ease-of-administration/#comment-7722 This seems to be Netezza's latest competitive response to DATAllegro - that we're not a 'real' appliance. Here's how we respond: - Our appliance can be used in much the same way as Netezza - i.e. no indices and just date range partitioning within the nodes. Netezza doesn't have true range partitioning, but zone maps perform the same function as single-level range partitions for data that is in date order. DBA effort will be very similar, but performance at a given price point or data capacity will generally be better on our appliance. - If a customer wants even better performance, they can easily add multi-level partitioning with a day or two of physical design work. Some queries will run 10-50 times faster. - VERY occasionally, it's useful to add one or two indices for queries that just look up one or two rows. This is very easy for any experienced DBA. This is just not an option in Netezza. - Our caching does not add ANY administration effort. Which product is more of an appliance is pretty irrelevant IMHO. Data warehouse platforms will never be as simple as household appliances such as microwave ovens. The question is whether they are good enough to do the job. A microwave without a timer would still work, but it wouldn't be very convenient. We feel that Netezza's architecture is just too simplistic for most real-world projects. Stuart DATAllegro This seems to be Netezza’s latest competitive response to DATAllegro - that we’re not a ‘real’ appliance. Here’s how we respond:

- Our appliance can be used in much the same way as Netezza - i.e. no indices and just date range partitioning within the nodes. Netezza doesn’t have true range partitioning, but zone maps perform the same function as single-level range partitions for data that is in date order. DBA effort will be very similar, but performance at a given price point or data capacity will generally be better on our appliance.

- If a customer wants even better performance, they can easily add multi-level partitioning with a day or two of physical design work. Some queries will run 10-50 times faster.

- VERY occasionally, it’s useful to add one or two indices for queries that just look up one or two rows. This is very easy for any experienced DBA. This is just not an option in Netezza.

- Our caching does not add ANY administration effort.

Which product is more of an appliance is pretty irrelevant IMHO. Data warehouse platforms will never be as simple as household appliances such as microwave ovens. The question is whether they are good enough to do the job. A microwave without a timer would still work, but it wouldn’t be very convenient. We feel that Netezza’s architecture is just too simplistic for most real-world projects.

Stuart
DATAllegro

]]>