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

Earlier this year I posited that, due to the exponential rate of growth, the amount of data collected for analysis is becoming beyond the scope of the current analytical staffs to examine it all.  And that the answer to growing the cumulative brain power necessary for this exponential growth in analysis is going to have to be machine learning and artificial intelligence. This is now in the works.

2 weeks ago

You’ll probably want to skip over this posting. 

Unless you’re curious about some of the more obscure workload classification conventions used by TASM and TIWM.

3 weeks ago

In July 2015 Eric shared on insights on the Teradata Python Module which is supporting the devops approach. The article above is describing the main functions and is showing basic examples how to use them. In the meantime, the discussions clarified some questions and also revealed some minor bugs which had been fixed instantly.

4 weeks ago

If you are user DBC or user TDWM and you log onto a Teradata Database, you might get treated somewhat differently than other users.  This posting describes what user DBC and user TDWM do, some of the special things about them, and when you can expect them to get treated differently.   We’ll also look at any implications in setting up workload management for these two special users.

10 Aug 2015

This “Teradata Basics” posting describes the current dimensions of parallelism in the Teradata Database, and how they work together.

30 Jun 2015

MLOADX is a new load utility enhancement introduced in Teradata Database 14.10 which is intended to overcome some of the limitations that are associated with standard MultiLoad.  This posting focuses on how workload management options will open up MLOADX for more expanded usage in Teradata Database 15.10.

03 Apr 2015

Think about the priority part of workload management for a minute.

The settings that the administrator makes when defining priorities for different workloads are on the surface--things like workload allocation percentages and access level assignments.  They are easy to see.  Below the surface are “global weights”, which starting in Teradata Database 14.10 indicate to you the actual percentage of platform resources your workload will receive, based on its allocation.

But they do more than translate your settings to an expected resource share.  Global weights are used by the database to order the queues for several internal entities.  For example, the AMP worker task (AWT) message queue is now ordered by global weight in SLES 11. 

So it’s time you spent a few minutes taking a closer look at what global weights are, how the SLES 11 priority scheduler calculates them, and how you can influence them.

30 Mar 2015

The amount of data that is now available for analysis is growing at an exponential rate.  As the hardware to capture the data becomes cheaper, faster and omnipresent, the amount of data collected for analysis is becoming beyond the scope of the current analytical staffs to examine it all. 

22 Jan 2015

The Teradata JDBC Driver Engineering team receives a lot of questions about what happens when a JDBC connection is created. Let's clarify the concepts Laddered Concurrent Connect (LCC) versus COP Discovery versus logon, and review what the Teradata JDBC Driver does to create a JDBC connection.


First, some definitions...

"COP" stands for Communications Processor, and is a term originating from Teradata's earliest database appliances in the 1980s. In modern usage, a "COP" is a Teradata Database node that is running a Teradata Database Gateway process.