Subscribe to Terdata Developer Exchange - RSS feed for all blogs Latest blog posts
1 week ago

During my first coding class, after the obligatory “Hello, World,” my assignment was to find the least cost path in a matrix of values (linear programming).  The computer took some time to crunch the data to come to a solution.  Now, this is an app on your phone.  

2 weeks ago

Statistical information is vital for the optimizer when it builds query plans. But collecting statistics can involve time and resources. By understanding and combining several different statistics gathering techniques, users of Teradata can find the correct balance between good query plans and the time required to ensure adequate statistical information is always available.

This recently-updated compilation of statistics collection recommendations are intended for sites that are on any of the Teradata Database 14.10 software release levels. Some of these recommendations apply to releases earlier than Teradata Database 14.10 and some rely on new features available only in Teradata Database 14.10.

For greater detail on collecting statistics for Teradata Database 14.10, see the orange book titled:  Teradata Database 14.10 Statistics Enhancements by Rama Krishna Korlapati.

Contributors: Carrie Ballinger, Rama Krishna Korlapati, Paul Sinclair, September 11, 2014

31 Jul 2014

Teradata has great perfomance in batch processing. As a typical OLAP system, Tereadata can't peform as well as OLTP in high concurrency real-time application. I wrote an open source framework - cheetah, which tries to work with Teradata together to provide better application experience cross batch and real-time requiements.

31 Jul 2014

How does TASM enforce rules such as classification and workload exceptions against User Defined Functions?  What about table functions and table operators, some of which do their work outside of Teradata?  How far can you rely on TASM classifications using estimated processing time in these cases?  Will there be accurate resource usage numbers reported to support workload exceptions on CPU or I/O?

These are some of the questions that need answering if you are extending the use of simple or more complex user-defined functions on your platform.

14 Jul 2014

This will be part 1 of a multi-part blog about how the .NET Data Provider for Teradata 15.0 can now In-Line Large Objects (LOB)  that are sent to a Teradata Database when executing an INSERT or UPDATE statement.  This first blog will introduce In-Lining of LOB.   Blogs will also be written that discuss how to take advantage of this feature, and performance characteristics.  All these blogs will be more technically oriented than my other blogs.

Overview

07 Jul 2014

This blog concentrates on the expected unexpected external factors that can have a (negative) impact on your organizations’ Integrated Data Warehouse (IDW).  The current discussions around what NSA can and cannot capture and store for data analysis got me thinking about the biggest elephant in the room:  the government.

30 Jun 2014

Because they look like just another group of workloads, you might think that SLES11 virtual partitions are the same as SLES10 resource partitions.  I’m here to tell you that is not the case.  They have quite different capabilities and purposes.  So don’t fall victim to retro-conventions and old-school habits that might hold you back from the full value of new technology.  Start using SLES11 with fresh eyes and brand new attitudes.  Begin at the virtual partition level.

This content is relevant to EDW platforms only.

03 Jun 2014

If I told you there was a way you might be able to speed up parsing time for your queries, would you be interested?  

In Teradata Database 14.10.02 there is a new capability that allows you to expedite express requests, and I’d like to explain how that works, describe when it can help you, and make some suggestions about how you can use it to get the best performance you can from parsing when the system is under stress.  But first a little background.

10 Mar 2014

A couple of recent articles in Wired got me thinking about just how social media services, and thus the value of the big data that they create, could be under threat from their own customers.

07 Mar 2014

The SLES 11 priority scheduler implements priorities and assigns resources to workloads based on a tree structure.   The priority administrator defines workloads in Viewpoint Workload Designer and places the workloads on one of several different available levels in this hierarchy. On some levels the admin assigns an allocation percent to the workloads, on other levels not.

How does the administrator influence who gets what?  How does tier level and the presence of other workloads are on the same tier impact what resources are actually allocated?  What happens when some workloads are idle and others are not?

This posting gives you a simple explanation of how resources are shared in SLES 11 priority scheduler and what happens when one or more workloads are unable to consume what they have been allocated.

Pages