Comments on: Teradata’s Active Enterprise Data Warehouse story

By: Teradata has over 100 appliances in production | DBMS2 -- DataBase Management System Services

Wed, 02 Sep 2009 04:59:10 +0000

[...] recently wrote that Teradata had gotten serious about appliance product lines, and had non-trivial sales figures for them. In a press release today, Teradata is now explicitly saying (emphasis [...]

By: Curt Monash

Curt Monash — Mon, 31 Aug 2009 23:02:25 +0000

Richard,

Then “Active” just becomes a performance review for the analytics team. If they are Smart and build Quick systems, then their warehouse is active. If they are Slow and build Dumb systems, however, then it isn’t.

By: Richard Hackathorn

Richard Hackathorn — Mon, 31 Aug 2009 21:12:26 +0000

Curt- Good initial struggle with defining ‘active’ data warehousing. Instead of getting involved with confusing factors, like latency, think of the concept of ‘active’ as an effective Stimulus->Response->Stimulus cycle within a business. First, you need to know what is happening. Second, you need need to respond (capture, store, analyze, decide, act) to the situation. Third, you need to make an impact. Do that quickly and smartly, and you are ‘active’. -Richard

By: Curt Monash

Curt Monash — Mon, 24 Aug 2009 21:38:00 +0000

Dan,

Thanks for the additional info!

By: Dan Graham

Dan Graham — Mon, 24 Aug 2009 16:06:58 +0000

A small clarification — there are two latencies being discussed in this blog.

First is the response time for web site (eCommerce) fast queries which typically run 1-5 seconds. Residency time for a unique key read is less than 40 milleseconds on the Teradata 5500 series. However total round trip from client, TCP/IP internet, to web app server, to the RDBMS and back has many possible speed bumps. So while 1 second queries are common, some may creep up to 2-4 seconds.

The second latency discussed in the blog described as minutes and hours are for mini-batch loading data concurrent with complex queries and operational queries. So loading a few hundred megabytes every 15 minutes 24X7 is becoming common with Teradata servers. Latencies < 2 minutes are in production but only a few applications can justify the labor and complexity involved so 15 minute mini-batch is more common.

Thanks Curt — a good unbiased write up.

By: Teradata highlights some analytic use cases | DBMS2 -- DataBase Management System Services

Mon, 24 Aug 2009 08:54:23 +0000

[...] couple of slides in my recent briefing onTeradata’s Active Enterprise Data Warehouse Story contained long lists of analytic use cases, at a finer level of granualarity than I’m focusing [...]