<?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"
	>
<channel>
	<title>Comments on: Vertica update</title>
	<atom:link href="http://www.dbms2.com/2008/02/07/vertica-update-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbms2.com/2008/02/07/vertica-update-2/</link>
	<description>Choices in data management and analysis</description>
	<pubDate>Fri, 16 May 2008 19:00:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: DBMS2 &#8212; DataBase Management System Services &#187; Blog Archive &#187; Vertica update</title>
		<link>http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-84927</link>
		<dc:creator>DBMS2 &#8212; DataBase Management System Services &#187; Blog Archive &#187; Vertica update</dc:creator>
		<pubDate>Tue, 13 May 2008 11:48:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-84927</guid>
		<description>[...] outsourced data marts. But I also had the opportunity to follow up on a couple of points from February&#8217;s briefing, [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] outsourced data marts. But I also had the opportunity to follow up on a couple of points from February&#8217;s briefing, [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amrith</title>
		<link>http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-80940</link>
		<dc:creator>Amrith</dc:creator>
		<pubDate>Mon, 07 Apr 2008 01:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-80940</guid>
		<description>You make a mention of the Sybase vs. Vertica lawsuit in your post. The lawsuit currently is against Vertica but may affect column store databases in general.

http://amrithkumar.wordpress.com/2008/04/06/sybaseiq-suit/</description>
		<content:encoded><![CDATA[<p>You make a mention of the Sybase vs. Vertica lawsuit in your post. The lawsuit currently is against Vertica but may affect column store databases in general.</p>
<p><a href="http://amrithkumar.wordpress.com/2008/04/06/sybaseiq-suit/" rel="nofollow">http://amrithkumar.wordpress.com/2008/04/06/sybaseiq-suit/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Column Oriented Storage lawsuits? &#171; Technophilia</title>
		<link>http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-80933</link>
		<dc:creator>Column Oriented Storage lawsuits? &#171; Technophilia</dc:creator>
		<pubDate>Sun, 06 Apr 2008 21:40:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-80933</guid>
		<description>[...] vertica update 2 the author [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] vertica update 2 the author [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curt Monash</title>
		<link>http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-71605</link>
		<dc:creator>Curt Monash</dc:creator>
		<pubDate>Sat, 09 Feb 2008 02:38:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-71605</guid>
		<description>As I understand it, this isn't primarily for the hedge funds' own transactions (although I'm sure those are stored too).  Rather, it's for historical market data, trade-by-trade.  I.e., it's for the algorithm-development part of algorithmic trading.

CAM</description>
		<content:encoded><![CDATA[<p>As I understand it, this isn&#8217;t primarily for the hedge funds&#8217; own transactions (although I&#8217;m sure those are stored too).  Rather, it&#8217;s for historical market data, trade-by-trade.  I.e., it&#8217;s for the algorithm-development part of algorithmic trading.</p>
<p>CAM</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Dooley</title>
		<link>http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-71551</link>
		<dc:creator>Larry Dooley</dc:creator>
		<pubDate>Fri, 08 Feb 2008 20:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbms2.com/2008/02/07/vertica-update-2/#comment-71551</guid>
		<description>I'm very familiar with hedge funds have worked at one for almost 7 years (a top 25 fund).  
10 tb is a lot of data for a hedge fund even if you've got both position by strategy/hedge by security 
by tax lot by day and also keep it by prime brokerage account strategy security tax lot by day that's
a lot of data but for the big guys for 5 years data I don't see it close to 10 TD (and I've had my
nose buried in this for a good bit of the past seven years)  The first by strategy by security is going
to be both wide and deep.  The second at prime brokerage location is going to narrow and deep. It's 
extremely difficult if not impossible to do P&#38;L at prime brokerage locations Margin is a different matter
and very important because managing that means managing your leverage.  

If you've got anyone else doing DW/BI at hedge funds I'd be interestend in corresponding</description>
		<content:encoded><![CDATA[<p>I&#8217;m very familiar with hedge funds have worked at one for almost 7 years (a top 25 fund).<br />
10 tb is a lot of data for a hedge fund even if you&#8217;ve got both position by strategy/hedge by security<br />
by tax lot by day and also keep it by prime brokerage account strategy security tax lot by day that&#8217;s<br />
a lot of data but for the big guys for 5 years data I don&#8217;t see it close to 10 TD (and I&#8217;ve had my<br />
nose buried in this for a good bit of the past seven years)  The first by strategy by security is going<br />
to be both wide and deep.  The second at prime brokerage location is going to narrow and deep. It&#8217;s<br />
extremely difficult if not impossible to do P&amp;L at prime brokerage locations Margin is a different matter<br />
and very important because managing that means managing your leverage.  </p>
<p>If you&#8217;ve got anyone else doing DW/BI at hedge funds I&#8217;d be interestend in corresponding</p>
]]></content:encoded>
	</item>
</channel>
</rss>
