Marketing versus reality on the one-petabyte barrier
Usually, I don’t engage in the kind of high-speed quick-response blogging I have over the past couple of days from the Teradata Partners conference (and more generally have for the past week or so). And I’m not sure it’s working out so well.
For example, the claim that Teradata has surpassd the one-petabyte mark comes as quite a surprise to variety of Teradata folks, not to mention at least one reliable outside anonymous correspondent. That claim may indeed be true about raw disk space on systems sold. But the real current upper limit, according to CTO Todd Walter,* is 5-700 terabytes of user data. He thinks half a dozen or so customers are in that range. I’d guess quite strongly that three of those are Wal-Mart, eBay, and an unspecified US intelligence agency.
*Teradata seems to have quite a few CTOs. But I’ve seen things much sillier than that in the titles department, and accordingly shan’t scoff further — at least on that particular subject. 😉
On the other hand, if anybody did want to buy a 10 petabyte system, Teradata could ship them one. And by the way, the Teradata people insist Sybase’s claims in the petabyte area are quite bogus. Teradata claims to have had bigger internal systems tested earlier than the one Sybase writes about.
| Categories: Data warehouse appliances, Data warehousing, eBay, Petabyte-scale data management, Specific users, Sybase, Teradata | 3 Comments |
Yet more on petabyte-scale Teradata databases
I managed to buttonhole Teradata’s Darryl MacDonald again, to follow up on yesterday’s brief chat. He confirmed that there are more than one petabyte+ Teradata databases out there, of which at least one is commercial rather than government/classified. Without saying who any of them were, he dropped a hint suggestive of Wal-Mart. That makes sense, given that a 423 terabyte figure for Wal-Mart is now three years old, and Wal-Mart is in the news for its 4 petabyte futures. Yes, that news has tended to mention HP NeoView recently more than Teradata. But it seems very implausible that a NeoView replacement of Teradata has already happened, if if such a thing is a possibility for the future. So right now however much data Wal-Mart has on its path from 423 terabytes to 4 petabytes and beyond is probably collected mainly on Teradata machines.
| Categories: Analytic technologies, Data warehouse appliances, Data warehousing, HP and Neoview, Petabyte-scale data management, Teradata | 1 Comment |
Another firm that never sees DB2 in data warehousing
At the Teradata show today, I talked with Mike Weber of Scorecard Systems Inc. Scorecard’s business is vertical BI for telecommunications companies to analyze call data. They support Teradata (obviously), Oracle, and Microsoft SQL*Server, with Netezza coming soon. But not DB2.
Mike says that, in ten years in this business, he’s never seen DB2. Read more
| Categories: Analytic technologies, Business intelligence, Data warehousing, IBM and DB2, Microsoft and SQL*Server, Oracle, Teradata | 2 Comments |
One reason Teradata spun out publicly rather than being bought
There were well-publicized tax reasons for Teradata to be spun out publicly from NCR rather than just sold off. Back in April, I questioned these, suggesting there was a pretty good workaround.
Today, however, after hearing Teradata management repeatedly finesse the question of why they didn’t pursue the buyout option, a very good reason hit me like a ton of bricks. Teradata employees — especially senior managers — got hefty stock options in connection with the spinout. The same would probably have happened if Teradata were LBOed. But it would surely have not have happened if Teradata had merely been sold off to a third company.
| Categories: Teradata | Leave a Comment |
Hot buzzword — multidimensional partitioning
Teradata finally announced multidimensional range partitioning in Version 12, not that they kept their plans in that regard a big secret. DATAllegro has also shipped multidimensional partitioning to at least one customer. Other vendors — well, I’ll stop there, given my ongoing atttitude problems about vendors’ self-defeating NDAs.
Whether or not multidimensional partitioning is a big improvement over single-dimensional will of course depend a great deal on the details of a particular database. Teradata used a figure of 30% performance improvement, but that’s surely just an example. Certainly in some extreme cases one could have a rather large reduction in the amount of data retrieved, and correspondingly a many-times-X improvement in the performance of certain important queries. Read more
| Categories: Analytic technologies, Data warehouse appliances, Data warehousing, DATAllegro, Teradata | Leave a Comment |
Teradata apparently has crossed the petabyte barrier
According to a hurried conversation I had with Chief Marketing Office Darryl MacDonald, Teradata has customers with over 1 petabyte of user data in a single instance. He wouldn’t disclose any names, but I’d guess one is eBay, who he did confim is a customer. The intelligence area is another one where I’d speculate there are Very Large Databases.
However, since Darryl mentioned testing systems internally up to 4 petabytes, I’d guess the upper limit of Teradata deployments is in the 1-2 petabyte range.
EDIT: I’m now guessing that Teradata’s largest classified database — which previously was the largest overall — isn’t much over a petabyte in size. And there’s a strong chance this is larger than any unclassified one.
Update: That wasn’t really 1+ petabyte of user data.
| Categories: Analytic technologies, Data warehouse appliances, Data warehousing, eBay, Specific users, Teradata | Leave a Comment |
SAS gets close to the database
One of the big announcements at the Teradata user conference this week (confusingly named “Partners”) is SAS integration. Now, SAS is integrating with other MPP data warehouse appliance vendors as well, but it’s likely that the Teradata integration is indeed the most advanced. For example, one customer proofpoint offered was an insurer who used this capability to reevaluate its risk profile at high speed after Hurricane Katrina. I doubt any of the other SAS/DBMS integrations I know of were in customer hands a year ago.
Three still-open questions I hope to address over the next couple of days are: Read more
| Categories: Analytic technologies, Data warehouse appliances, Data warehousing, Predictive modeling and advanced analytics, SAS Institute, Teradata | Leave a Comment |
The era of memory-centric BI may have finally started
SAP is acquiring Business Objects. There’s nothing inherent in BI Accelerator’s design that ties it to NetWeaver, SAP star schema InfoCubes, or any other particular current implementation detail. So BI Accelerator could become a lot more than an afterthought.
Combine that with Cognos’s acquisition of Applix and the continued success of upstart QlikView, and we could finally see a general memory-centric BI boom.
Maybe. There have been a lot of false alarms before.
| Categories: Analytic technologies, Business intelligence, Business Objects, Cognos, Memory-centric data management, QlikTech and QlikView, SAP AG | 3 Comments |
The four horsemen of data warehousing
I’ve been talking a lot to text mining vendors this week, as per a series of posts over on Text Technologies. Specifically, I’ve focused on the two with exhaustive extraction strategies, namely Attensity and Clarabridge. (Exhaustive extraction is Attensity’s term for separating the linguistic-analysis part of text mining from the DBMS-based BI/analytics part.)
So I asked each of Attensity and Clarabridge the side question as to which data warehouse software or appliances they were seeing. The answers were almost identical — Oracle, Microsoft SQL*Server, Teradata, and Netezza. One also mentioned MySQL and 2 HP prospects — but the HP sites were running NonStop SQL, not NeoView. Amazingly, there were no mentions of DB2. There also weren’t any mentions of the smaller specialist startups, such as DATAllegro, Greenplum, or Vertica.
SAP takes back MaxDB from MySQL
Way back in January, 2006, I wrote that MaxDB was not getting merged into MySQL. Given that, it makes sense for SAP to take back control of the product. As The Reg reports, that’s exactly what’s happening.
The bigger question is — how’s MySQL’s SAP certification coming along? Whether or not MySQL gets SAP-certified and included in the SAP product catalog will be a huge indicator of whether it’s ready for OLTP prime time.
Anybody want to place bets on which midrange OLTP DBMS gets certified for SAP first, MySQL or EnterpriseDB? MySQL has a large head start, but if my clients at EnterpriseDB have their priorities straight, they might wind up lapping MySQL even so.
| Categories: EnterpriseDB and Postgres Plus, Mid-range, MySQL, OLTP, SAP AG | 4 Comments |