<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Infobright update</title>
	<atom:link href="http://www.dbms2.com/2009/04/20/infobright-update-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2009/04/20/infobright-update-3/</link>
	<description>Choices in data management and analysis</description>
	<lastBuildDate>Mon, 01 Mar 2010 19:09:32 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Calpont&#8217;s InfiniDB &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.dbms2.com/2009/04/20/infobright-update-3/comment-page-1/#comment-148372</link>
		<dc:creator>Calpont&#8217;s InfiniDB &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Sun, 08 Nov 2009 01:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=753#comment-148372</guid>
		<description>[...] One thing free InfiniDB has that Infobright only offers in its Enterprise Edition is ACID-compliant Insert/Update/Delete. (Note: I wish people would stop saying that Infobright Enterprise Edition isn&#8217;t ACID-compliant, since that point was cleared up a while ago.) [...]</description>
		<content:encoded><![CDATA[<p>[...] One thing free InfiniDB has that Infobright only offers in its Enterprise Edition is ACID-compliant Insert/Update/Delete. (Note: I wish people would stop saying that Infobright Enterprise Edition isn&#8217;t ACID-compliant, since that point was cleared up a while ago.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Infobright metrics &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.dbms2.com/2009/04/20/infobright-update-3/comment-page-1/#comment-129608</link>
		<dc:creator>Infobright metrics &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Wed, 08 Jul 2009 17:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=753#comment-129608</guid>
		<description>[...] posted about Infobright, and included some company-supplied metrics. Most looked familiar from a post I did in April, but Infobright&#8217;s latest figure for # of paying customers seems to be &#8220;&gt;60&#8243;, [...]</description>
		<content:encoded><![CDATA[<p>[...] posted about Infobright, and included some company-supplied metrics. Most looked familiar from a post I did in April, but Infobright&#8217;s latest figure for # of paying customers seems to be &#8220;&gt;60&#8243;, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Swanhart</title>
		<link>http://www.dbms2.com/2009/04/20/infobright-update-3/comment-page-1/#comment-121957</link>
		<dc:creator>Justin Swanhart</dc:creator>
		<pubDate>Mon, 18 May 2009 18:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=753#comment-121957</guid>
		<description>ACID stands for:

Atomicity
Consistency
Integrity
Durability

Please explain how Infobright accomplishes all of these tasks w/out any transactional logging that I&#039;m aware of?

For instance, how can they claim to support the &#039;I&#039; in acid w/out supporting FOREIGN KEY CONSTRAINTS and UNIQUE KEY CONSTRAINTS, which form the basis of integrity checking?

Since they don&#039;t support the concept of transactions, how can I load into two tables atomically and ensure rows do not end up in either of the tables (ie, both loads are rolled back) if an error happens on either load?  This is the &#039;A&#039; in ACID.

I imagine that the &#039;C&#039; and &#039;D&#039; portions are handled well, at least in the case of the database crashing while loading a single table,  since a column store has an easily identified HWM (high water mark) for the columns.  I&#039;m not sure how they can guarantee this across multiple tables w/out transactional logging which I&#039;m not aware of.</description>
		<content:encoded><![CDATA[<p>ACID stands for:</p>
<p>Atomicity<br />
Consistency<br />
Integrity<br />
Durability</p>
<p>Please explain how Infobright accomplishes all of these tasks w/out any transactional logging that I&#8217;m aware of?</p>
<p>For instance, how can they claim to support the &#8216;I&#8217; in acid w/out supporting FOREIGN KEY CONSTRAINTS and UNIQUE KEY CONSTRAINTS, which form the basis of integrity checking?</p>
<p>Since they don&#8217;t support the concept of transactions, how can I load into two tables atomically and ensure rows do not end up in either of the tables (ie, both loads are rolled back) if an error happens on either load?  This is the &#8216;A&#8217; in ACID.</p>
<p>I imagine that the &#8216;C&#8217; and &#8216;D&#8217; portions are handled well, at least in the case of the database crashing while loading a single table,  since a column store has an easily identified HWM (high water mark) for the columns.  I&#8217;m not sure how they can guarantee this across multiple tables w/out transactional logging which I&#8217;m not aware of.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victoria Eastwood</title>
		<link>http://www.dbms2.com/2009/04/20/infobright-update-3/comment-page-1/#comment-117454</link>
		<dc:creator>Victoria Eastwood</dc:creator>
		<pubDate>Mon, 20 Apr 2009 19:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=753#comment-117454</guid>
		<description>Hi Curt,

It was nice to talk with you last week.  Our apologies for not updating you on ACID compliance.  We have made a number of changes in this area and now pass ACID compliance, using the TPC-H tests as a guideline.  As you suggest, we should have included that in the release and briefing.

Regarding SQL 2003 standard support, MySQL supports very few of these newer additions including even some from SQL-99.  We would need to extend MySQL ourselves to add support and we haven&#039;t seen a market demand yet to schedule the extra work.

Cheers</description>
		<content:encoded><![CDATA[<p>Hi Curt,</p>
<p>It was nice to talk with you last week.  Our apologies for not updating you on ACID compliance.  We have made a number of changes in this area and now pass ACID compliance, using the TPC-H tests as a guideline.  As you suggest, we should have included that in the release and briefing.</p>
<p>Regarding SQL 2003 standard support, MySQL supports very few of these newer additions including even some from SQL-99.  We would need to extend MySQL ourselves to add support and we haven&#8217;t seen a market demand yet to schedule the extra work.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL storage engine round-up, with Oracle-related thoughts &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.dbms2.com/2009/04/20/infobright-update-3/comment-page-1/#comment-117417</link>
		<dc:creator>MySQL storage engine round-up, with Oracle-related thoughts &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Mon, 20 Apr 2009 13:39:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=753#comment-117417</guid>
		<description>[...] Infobright is the most established of the rest. At the moment I&#8217;m not recommending it for most industrial-strength uses unless the user is particularly cash-constrained. But I wouldn&#8217;t be surprised if that changed soon.  A cheap, fast, simple columnar analytic DBMS has a place in the world. [...]</description>
		<content:encoded><![CDATA[<p>[...] Infobright is the most established of the rest. At the moment I&#8217;m not recommending it for most industrial-strength uses unless the user is particularly cash-constrained. But I wouldn&#8217;t be surprised if that changed soon.  A cheap, fast, simple columnar analytic DBMS has a place in the world. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Calpont update &#8212; you read it here first! &#124; DBMS2 -- DataBase Management System Services</title>
		<link>http://www.dbms2.com/2009/04/20/infobright-update-3/comment-page-1/#comment-117394</link>
		<dc:creator>Calpont update &#8212; you read it here first! &#124; DBMS2 -- DataBase Management System Services</dc:creator>
		<pubDate>Mon, 20 Apr 2009 07:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/?p=753#comment-117394</guid>
		<description>[...] to offer a MySQL storage engine for analytic database processing. Thus, Calpont will compete with Infobright, Kickfire, and perhaps [...]</description>
		<content:encoded><![CDATA[<p>[...] to offer a MySQL storage engine for analytic database processing. Thus, Calpont will compete with Infobright, Kickfire, and perhaps [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.214 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2010-03-02 19:22:07 -->
