Please note, we are no longer supporting teradataR since the decision was made for Teradata to focus on our partnership with Revolution for R integration with Teradata.

R  is an open source language for statistical computing and graphics. R provides a wide variety of statistical (linear and nonlinear modeling, classical statistical tests, time-series analysis, classification, clustering) and graphical techniques, and is highly extensible. This free package is designed to allow users of R to interact with a Teradata database.  Users can use many statistical functions directly against the Teradata system without having to extract the data into memory.

In this post, we will cover some more advanced logging topics in TRM, including PE logging, SQL output, user clicks, authentication attempts, and startup logging.

This article describes the basics of TRM's V6 logging in the application server. This includes log file configuration, versioning, location and content.

Here are a couple of helpful links in Teradata Relationship Manager (TRM).  These allow you to see all of the security privileges and user groups assigned to the logged in user, as well as a report of the TRM version and detailed environmental information.

Right out-of-the box, custom processing engine tasks may be created without having to write new Java components. These tasks are application components that implement common functionalities. There are several base processing engine tasks that are also based on these common tasks. Built-in processing engine tasks are limited in scope and functionality to what they’re capable of and cannot be extended or changed.

In parts 1 and 2, we looked at how to load and retrieve large objects using Teradata BLOBs and CLOBs. In part 1, I put forward my unbreakable golden rule that you shouldn’t simply store Object Models as Large Objects. Rather, always map your objects’ attributes to columns in a table; don’t just serialize a bunch of classes and store them in a BLOB.

In part 3, I present another of my unbreakable golden rules; which is “Rules were made to be broken”. The focus of this article is how to serialize and persist (store) an Object Model into a BLOB on Teradata and reinstate it.

Expect 
"It will not do to leave a live dragon out of your plans if you live near one." ~ The Hobbit

No matter what you do, no matter how long you prepare, your plan will begin to slowly, or not so slowly, unravel before your eyes.  Plans fail, that is the one constant you can actually plan for.  

What in the world do you mean?  Agile is a spotlight?  That's ridiculous.  It's all about daily stand up meetings, burndown charts, cards on walls, and other fun stuff like that, right?  If I do those things, I am Agile, right?  

WRONG!

Come on, doing all of that stuff has to count for something!!!

OK, fair enough, it actually counts for a lot.  It shows commitment to the process and a desire to make the life of your project less painful over the long haul.

In Part 1, we looked at what Large Objects are and some tactics that we could employee to load them into Teradata. As I stated back in part 1, loading large objects is great, but by itself is pretty useless. In this article, we will look at extracting Binary Large Objects from Teradata for inclusion in a web application.

But before we get to that, we need to know something about the large objects we will be dealing with.

Last week we concluded by challenging you to consider how a Connection Pool contributes to the performance of Web and Web service applications. Further we suggested that this week we would expand on this thought by exploring what you can do, during the development of an Active Integration application, to achieve improved performance through collaborating with the Database on Workload Management.

Until now nothing that we have discussed has been dramatically different from any other Spring Framework / DAO / Web services / JEE / POJO tutorial, however, there is method to this madness in that it was necessary to introduce the Teradata Masters out there to some new Java concepts while leading the Java Masters into the Teradata fold. While this has taken a reasonable number of weeks to accomplish it should now be safe for the entire readership to enter the world of Teradata Workload Management and Query Banding together.