Teradata Active System Management (TASM) is a powerful tool available to you that gives you unprecedented control over your Teradata system. Teradata 14.0 SLES 11 introduces Teradata Integrated Workload Management (TIWM), which, for the first time, provides workload management capabilities to customers without full TASM licensing.

No two customers are the same, and it follows that there cannot be a one size fits all approach to workload management. In this session, we will cover some common, and some not-so-common resource allocation problems and solutions.

We will demonstrate how to use the intuitive and easy to use Viewpoint TASM portlets for all your workload management needs. Use Workload Designer to create Filters, Throttles and Workloads, and manage allocating resources between them. Learn to use Workload Health and Workload Monitor for live, in-depth analysis of workload performance.

Come and see how to make Workload Management work for you!

Note: This was a 2012 Teradata Partners Conference session.

Teradata Release information:14.0

Presenters:
Betsy Cherian, Software Engineer – Teradata Corporation
Darrick Sogabe, Product Manger – Teradata Corporation

This session will provide information on the basic concepts of Partitioned Primary Indexes.

What is a partitioned primary index? How do you define a partitioned primary index (PPI)? What are the RANGE_N and CASE_N functions all about? Get the answers and more about this performance enhancing capability during this presentation on the basics of partitioned primary indexes. This topic is of particular interest to physical database designers and database performance analysts. This session will describe the newer partitioning capabilities such as multi-level partitioning, character PPI enhancements (13.10), ALTER TABLE TO CURRENT (13.10), and the increased number of partitions in Teradata 14.0. This session will provide numerous DDL examples of creating partitioned tables using the newest features.

Key Points:

• Understand the structure of a partitioned primary index and how it is implemented

• Learn how to create and alter a PPI using various functions such as RANGE_N

• Understand the advantages and disadvantages of using a partitioned primary index

Presenter: Larry Carter, Senior Learning Consultant – Teradata

Defining workloads in TDWM may qualify as a TASM implementation but is just a small piece of the puzzle.  This presentation will look at this and all the other pieces needed to complete the picture.

This presentation will provide you with best practices based on more than 100 TASM implementations.  Learn how to understand  workloads and determine the impact of changes.  Examine how to improve tactical query performance and keep your system from AWT saturation and flow control.  If you’re setting up TASM for the first time, or just want to improve the scheme you have now, then this presentation is for you.

Note: This was a 2012 Teradata Partners Conference session.

Presenters:
Greg Hamilton - Teradata Corporation
Srini Gorella - Teradata Corporation
 

In earlier postings I’ve described how TASM system events can detect such things as AMP worker task shortages, and automatically react to change workload managements settings.   These system events tell TASM to look out for and gracefully react to resource shortages without your direct intervention, by doing things like adjusting throttle limits temporarily downwards for the less critical work.

This switchover happens as a result of TASM moving you from one Health Condition to another, and as a result, from one state to another state.  But how does this shift to a new actually state happen?  And under what conditions you will you be moved back to the previous state?

Timers that control the movement between states

Before you use system events to move you between states, you will need to familiarize yourself with a few timing parameters within TASM, including the following:

• System-wide Event Interval - The time between asynchronous checks for event occurrences.  It can be set to 5, 10, 30 or 60 seconds, with 60 seconds being the default
• Event-specific Qualification Time – To ensure the condition is persistent, this is the amount of time the event conditions must be sustained in order to trigger the event
• Heath Condition Minimum Duration – Prevents a constant flip-flop between states,  the minimum amount of time that a health condition (which points to the new state) must be maintained even when the conditions that triggered the change are no longer present.

Entering a State

Let’s assume you have defined an AWT Available event that triggers when you have only two AMP worker tasks available on any five of your 400 AMPs, with a Qualification Time of 180 seconds.   Assume that you have defined the Health Condition associated with the state to have a Minimum Duration of 10 minutes, representing the time that must pass before the system can move back to the original state. 

TASM takes samples of database metrics in real-time, looking to see if any event thresholds have been met.  It performs this sampling at the frequency of the event interval. 

Once a sampling interval discovers the system is at the minimum AMP worker task level defined in the event, a timer is started.   No state change takes place yet.  The timer continues on as long as each subsequent sample meets the event’s thresholds.  If a new event sample shows that the event thresholds are no longer being met, then the timer will start all over again with the next sample that meets the event’s threshold criteria.

Only when the timer reaches the Qualification Time (180 seconds) will the event be triggered, assuming that all samples along the way have met the event’s threshold.  At that point TASM moves to the new state. 

Exiting a State

Returning to the original state follows a somewhat similar pattern.

The Minimum Duration DOES NOT determine how long you will remain in the new state, but rather it establishes the minimum time that TASM is required to keep you in the new state before reverting back to the original state.  

So when will you exit a state?

Event interval sampling continues at the event interval number of seconds all the while you are in the new state.  Even if the event threshold criteria is no longer being met and available AWTs are detected to be above the available threshold, once the move to the new state has taken place, the new state remains in control for the Minimum Duration.

After the Minimum Duration number of seconds has been passed, if event sampling continues to show that the AWT thresholds are being met (you still have at least five AMPs with only two AWTs available), TASM will continue to stay in that new state.  Only after the first sample that fails to meet the event thresholds is experienced (once the Minimum Duration number of seconds has passed) will control be moved back to the original state.

The bottom line is that you will not return to the original state until the Minimum Duration time of the state's Health Condition has been passed, but you may not be returned then if the condition that triggered the event persists.

Have you ever struggled over whether, or how, to use a new database feature?  In this presentation, we’ll demonstrate how database query log (DBQL) data can help when it comes to determining candidates for MLPPI (Multi-Level Partitioned Primary Index) as well as the new Columnar Partitioning feature of Teradata 14.

This presentation will discuss using DBQL object data for gathering such key information as frequency of use, large scan, and total query counts, as well as CPU and I/O usage.  In addition, the presentation will review techniques for testing and validating conclusions, instilling confidence in your decisions.  Finally, learn how the wealth of information available from DBQL can make it easier for you to benefit from the performance advantages that come with features like MLPPI and Columnar.

Note: This was a 2012 Teradata Partners Conference session.

Teradata Release information: TD 13 & 14

Presenters:
Barbara Christjohn, Performance COE – Teradata Corporation
David Hensel, Performance COE – Teradata Corporation

It's well-known that the application of database optimization techniques can improve query performance.

However these techniques are often overlooked when it comes to analytical queries (especially those in-database) as those queries are already significantly faster than analysts are used to. However the application of techniques, such as AJIs, MVC, MLPPI, soft RI and columnar partitioning, can all lead to further improvements in processing time. This talk will explain those techniques and show how they can be applied to analytical data sets to increase the productivity of the analysts. Examples from the field will be presented detailing how they benefited the analytic process.

Note: This was a 2012 Teradata Partners Conference session.

Presenter: Paul Segal, PS Consultant – Teradata Corporation

The Teradata Database system is different from other databases in a number of fundamental ways.

If you want to know what these differences are and how they make it possible for Teradata to deliver unlimited scalability in every dimension, high performance, simple management and all the other requirements of an Active Data Warehouse, then this is the presentation for you. We will discuss how the architecture of Teradata enables you to quickly, efficiently and flexibly deliver value to your business.

Key Points:

• Teradata's key differentiators
• What the differences mean to the IT staff
• How the differences result in value to the business

Note: This was a 2012 Teradata Partners Conference session.

Presenter: Todd Walter, Distinguished Fellow – Teradata Corporation

Statistics about tables, columns and indexes are a critical component in producing good query plans.

This session will examine the different options that are available when collecting statistics, with an emphasis on the new USING clauses and other enhancements in Teradata 14.0.  Statistics histograms will be detailed, and the important role that SUMMARY statistics play will be emphasized.   The improved statistics extrapolation process and the ability to combine statistics collections into a single table scan will be covered.  The session will wrap up with some general recommendations for statistics collection in Teradata 14.0.

Key Points:

• Learn the differences between statistics collection approaches
• Find out how the new Teradata 14.0 enhancement can benefit you
• Understand the new statistics collection recommendations for 14.0

Teradata Release information: Teradata 14.0

Presenter: Carrie Ballinger, Software Engineer – Teradata Corporation

Collecting statistics on data dictionary tables is an excellent way to tune long-running queries that access multi-table dictionary views.  Third party tools often access the data dictionary several times, primarily using the X views.  SAS, for example, accesses DBC views including IndicesX and TablesX for metadata discovery.  Without statistics, the optimizer may do a poor job in building plans for these complex views, some of which are composed of over 200 lines of code.

In an earlier blog posting I discussed the value of collecting statistics against data dictionary tables, and provided some suggestions about how you can use DBQL to determine which tables and which columns to include.  Go back and review that posting.  This posting is a more comprehensive list of DBC statistics that is updated to include those recommended with JDBC.

Note that the syntax I am using is the new create-index-like syntax available in Teradata 14.0.  If you are on a release prior to 14.0 you will need to rewrite the following statements so they are in the traditional collect statistics SQL.

Here are the recommendations for DBC statistics collection.  Please add a comment if I have overlooked any other useful ones.

COLLECT STATISTICS
 COLUMN TvmId
 , COLUMN UserId
 , COLUMN DatabaseId
 , COLUMN FieldId
 , COLUMN AccessRight
 , COLUMN GrantorID
 , COLUMN CreateUID
 , COLUMN (UserId ,DatabaseId)
 , COLUMN (TVMId ,DatabaseId)
 , COLUMN (TVMId ,UserId)
 , COLUMN (DatabaseId,AccessRight)
 , COLUMN (TVMId,AccessRight)
 , COLUMN (FieldId,AccessRight)
 , COLUMN (AccessRight,CreateUID)
 , COLUMN (AccessRight,GrantorID)
 , COLUMN (TVMId ,DatabaseId,UserId)
ON DBC.AccessRights;


COLLECT STATISTICS
 COLUMN DatabaseId
 , COLUMN DatabaseName
 , COLUMN DatabaseNameI
 , COLUMN OwnerName
 ,  COLUMN LastAlterUID
 , COLUMN JournalId
 , COLUMN (DatabaseName,LastAlterUID)
ON DBC.Dbase;


COLLECT STATISTICS
 COLUMN LogicalHostId
 , INDEX ( HostName )
ON DBC.Hosts;

COLLECT STATISTICS
 COLUMN OWNERID
 , COLUMN OWNEEID
 , COLUMN (OWNEEID ,OWNERID)
ON DBC.Owners;

COLLECT STATISTICS
 COLUMN ROLEID
 , COLUMN ROLENAMEI
ON DBC.Roles;


COLLECT STATISTICS
INDEX (GranteeId)
ON DBC.RoleGrants;


COLLECT STATISTICS 
COLUMN (TableId)
, COLUMN (FieldId)
, COLUMN (FieldName)
, COLUMN (FieldType)
, COLUMN (DatabaseId)
, COLUMN (CreateUID)
, COLUMN (LastAlterUID)
, COLUMN (UDTName)
, COLUMN (TableId, FieldName)
ON DBC.TVFields;


COLLECT STATISTICS
 COLUMN TVMID
 , COLUMN TVMNAME
 , COLUMN TVMNameI
 , COLUMN DATABASEID
 , COLUMN TABLEKIND
 , COLUMN CREATEUID
 , COLUMN CreatorName
 , COLUMN LASTALTERUID
 , COLUMN CommitOpt
 , COLUMN (DatabaseId, TVMName)
 , COLUMN (DATABASEID ,TVMNAMEI)
ON DBC.TVM;

 
COLLECT STATISTICS
 INDEX (TableId) 
 , COLUMN (FieldId)
 , COLUMN (IndexNumber)
 , COLUMN (IndexType)
 , COLUMN (UniqueFlag)
 , COLUMN (CreateUID)
 , COLUMN (LastAlterUID)
 , COLUMN (TableId, DatabaseId)
 , COLUMN (TableId, FieldId)
 , COLUMN (UniqueFlag, FieldId)
 , COLUMN (UniqueFlag, CreateUID)
 , COLUMN (UniqueFlag, LastAlterUID)
 , COLUMN (TableId, IndexNumber, DatabaseId)
ON DBC.Indexes;


COLLECT STATISTICS
 COLUMN (IndexNumber)
 , COLUMN (StatsType)
ON DBC.StatsTbl;


COLLECT STATISTICS
 COLUMN (ObjectId)    
 , COLUMN (FieldId)
 , COLUMN (IndexNumber)
 , COLUMN (DatabaseId, ObjectId, IndexNumber)
ON DBC.ObjectUsage;


COLLECT STATISTICS
 INDEX (FunctionID )
 , COLUMN DatabaseId
 , COLUMN ( DatabaseId ,FunctionName )
ON DBC.UDFInfo;


COLLECT STATISTICS
 COLUMN (TypeName)
 , COLUMN (TypeKind)
ON DBC.UDTInfo;

Download Teradata Express for VMware, a free, fully-functional Teradata database, that can be up and running on your system in minutes. For TDE 14.0, please read the launch announcement, and the user guide. For previous versions, read the general introduction to the new Teradata Express family, or learn how to install and configure Teradata Express for VMware.

There are multiple versions of Teradata Express for VMware available: for Teradata 13.0 and 13.10 and 14.0. More information on each package is available on our main Teradata Express page.

Note that in order to run this VM, you'll need to install VMware Player or VMware Server on your system. Also, please note that your system must have 64-bit support. For more details, see how to install and configure Teradata Express for VMware.

For feedback, discussion, and community support, please visit the Cloud Computing forum.

Download sizes, space requirements and MD5 checksums

Teradata is announcing new Teradata Express 14.0 images that update those announced last year. These new images are at patch level 14.00.03.02 which represents the current shipping version of Teradata 14.0. This gives you access to the latest patch updates for Teradata 14.0 for your test and development needs.

Depending upon your needs and the resources available on your PC, three versions of Teradata Express14.0 are available. Please note that the resources needed for Teradata Express are in addition to those needed by the operating system on your PC:

• TD Express 14.0 with 4GB of storage. Requires 13 GB of disk space and 2.0 GB of RAM for the Virtual Machine.
• TD Express 14.0 with 40GB of storage. Requires 18 GB of disk space and 2.5 GB of RAM for the Virtual Machine.
• TD Express 14.0 with 1TB of storage. Requires 35 GB of disk space and 4.0 GB of RAM for the Virtual Machine.

A 64-bit virtualization-capable PC is required.  VMware provides a utility to check your system for 64 bit support at this link.

Details on the images remain the same as the original TD 14.0 and can be found here:

http://developer.teradata.com/database/articles/teradata-express-14-0-for-vmware-now-available

Instructions for running the images remain the same and can be found here:

http://developer.teradata.com/database/articles/teradata-express-14-0-for-vmware-user-guide

The new images are available at the down load page

Please note that while the Teradata Express family of products is not officially supported, you can talk to other users and get help in the Cloud Computing forum. Note also that Japanese-language instructions for configuring TDE-V are available for download in PDF format.

Behind the Big Data hype and buzzword storm are some fundamental additions to the analytic landscape.

What new tools do you need to deal with the new storm of data ripping up your IT infrastructure? What do these new tools do and what are they not good at? How do you choose among these tools to solve the business challenges your company is facing? And how do you tie all the tools together to make them work as an overall analytic ecosystem?

Presenter: Todd Walter, Chief Technologist – Teradata Corporation

You know about how the athlete coming off the bench is inserted into a game and radically alters the team play such that the team coasts to victory.  A Game Changer!  So too, is Columnar Partitioning, radically altering the process of physical data model development to ease application migration to Teradata Database. 

We all have large, legacy applications in our environments.  You know the characteristics:  huge tables with a large amount of columns, lots of data, with inadequate or unknown column descriptions, where everyone is loath to remove them for the sake of some query that might need the content.  The result:  An initial physical data model that requires significant alteration once the forklift process is complete.

Teradata Columnar changes the game in migrating to Teradata through swifter model development, better initial performance, and increased user satisfaction allowing the legacy system to be shutdown more quickly.

Teradata Columnar changes the migration game!

Note: This was a 2012 Teradata Partners Conference Presentation.

Presenter: Geoffrey Plummer, PS Principal Consultant – Teradata Corporation

TD Geo Import/Export tool lets you translate ESRI Shape and KML files to TD format.

Teradata Express for VMware Player (TDE-V) is a free, fully operational Teradata Virtual Machine with up to one terabyte of storage. Imagine being able to install a fully operational Teradata database on your PC and be running queries in five minutes, easy as 1-2-3.

Image may be NSFW.
Clik here to view.After installing VMware Server/Player and downloading your choice of VM, this is all it takes:

1. Install the VM
2. Start the VM and Teradata
3. Use the Teradata Studio Express to run queries

To help you load data, the new Teradata EZLoader utility is included in the VM.

Depending upon your needs and the resources available on your PC, two versions of Teradata Express14.10 are available at this time. Please note that the resources needed for Teradata Express are in addition to those needed by the operating system on your PC:

• TD Express 14.10 with 40GB of storage with SLES 11 and without Viewpoint requires 2.0 GB of RAM for the Virtual Machine and can run on a host machine with 4 GB of RAM.
• TD Express 14.10 with 1TB of storage with SLES 10 and Viewpoint requires 4.0 GB of RAM for the Virtual Machine and therefore needs a host machine with 8GB of RAM.

A 64-bit virtualization-capable PC is required.  VMware provides a utility to check your system for 64 bit support at this link.

Please note that while the Teradata Express family of products is not officially supported, you can talk to other users and get help in the Cloud Computing forum. Note also that Japanese-language instructions for configuring TDE-V are available for download in PDF format.

Getting Started

The first task is to make sure you have a system capable of handling VMware and VM’s. There are plenty of details on the VMware site but here are some basic requirements that you should be aware of before getting started:

1. Since the SLES VM’s are 64-bit, your CPU must support 64-bit operation.
2. Your CPU must also support Virtualization. Generally there is a BIOS setting which enables this. Google the topic for your particular CPU for more information but most recent PC’s support both 64-bit and Virtualization.

As soon as you determine your system supports the requirements you can proceed:

It's time to run VMware Player and start Teradata Express.  From the VMware Player Welcome page, choose "Open a Virtual Machine" and click your way through your file directory to the Teradata Express folder, looking for the "TDExpress14.10_sles10.vmx" or "TDExpress14.10_sles11.vmx"file.   

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Figure 1. Loading the TD Express virtual machine in VMware Player

I MOVED IT!

This step is very important.  As you click through the virtual image directories, VMware is looking for the .vmx file, in order to start the image.  Once you find it, double-click or choose the 'Open' option.  VMware will now present you with a dialog box asking if you copied or moved this image.  Be sure to choose  'I MOVED IT'!

1. VMware Player and VMware Server are both available for free download from the VMware site and both will work. This tutorial describes using VMware Server (hosted on a Windows system). If you have not already done so, make your choice and install VMware on your system.
2. Disk space is a big consideration. 40GB and 1TB versions of TD Express are available depending on your resources and need. Typically you don't actually need the full amount of available disk space (although this would be advisable) to install and get started. Also, isolating VM’s on their own physical disks (if available) can improve performance. Some additional information about disk space is provided below.
3. Download the appropriate TD Express image from the downloads section.
4. If you do not already have 7-zip download it here
5. Create a directory on your C:\ drive named "virtual-machinesvirtual-machines". After unzipping (7-zip) the file you will end up with something like “C:\virtual-machines\TD14..”.
6. Now you need to add the VM to the VMware inventory. Using VMware Player (see Figure 1 above for reference):
   1. Click on Open A Virtual Machine
   2. Drill down under inventory, highlight the folder and item in contents (TDExpress14.10_sles11.vmx), OK
7. The VM will show up in the Library under the Home tab and can be started and stopped from there.
8. Double click on the TD Express image to start.
9. Login into the SLES VM with username rootand password root. root/root
10. Wait. The image will take some time to initialize.
11. Test with bteq (bteq is the standard Teradata command line query tool. It can be invoked from the Linux command line in the Gnome window as follows.
    1. From the shell prompt:TDExpress14.0_Sles10:~ # bteq
    2. When asked for your logon: .logon 127.0.0.1/dbc
    3. When asked for your password: dbc
    4. You should now be in the bteq session (you'll see a message *** Logon successfully completed).
    5. Now, let's execute some SQL. You should see results similar to below except the version will be 14.10.00.02:

       select * from dbcinfo;
       
        *** Query completed. 3 rows found. 2 columns returned.
        *** Total elapsed time was 1 second.
       
       InfoKey                        InfoData
       ------------------------------ --------------------------------------------
       LANGUAGE SUPPORT MODE          Standard
       RELEASE                        14.00.00.01
       VERSION                        14.00.00.01
       

    6. And you can now quit bteq by executing: quit

Image may be NSFW.
Clik here to view.

Figure 2. Testing Teradata using BTEQ

If you are running the SLES 11 image without Viewpoint, skip over this next section and go right to Loading Data.

Monitoring Teradata Express using Viewpoint

You have the option of running Viewpoint on TD Express 14.10 with the 1TB, SLES 10 image only. To see all you can do with Viewpoint look here.

To login to Viewpoint follow the steps below.

1. You need to start Firefox to run Viewpoint. Look for the "Computer" tab in the lower left hand corner of your VMware Player desktop. Under the "Applications" tab you see the icon to start Firefox.
   
   Image may be NSFW.
   Clik here to view.



2. Wait. Firefox can take several minutes to initialize. Even if you have sufficient VRAM allocated, you will have heavy CPU and disk I/O traffic. Just wait, it will come up.
   
   Image may be NSFW.
   Clik here to view.


3. The Login information is pre-populated for you. Just hit "Sign In".
4. The Set Up screen is already pre-populated for you. Hit "Back to Portal" to get from this screen to the main dashboard.
   
   Image may be NSFW.
   Clik here to view.


5. You are now ready to add portlets to your dashboard.
   
   
   Image may be NSFW.
   Clik here to view.

Loading Data

On the Teradata version 14.0 VM’s the new EZloader utility is included for fast and easy data loads. Here's an example of loading some data from a comma-separated file (i.e.. a CSV). From BTEQ, run the following:

CREATE user vmtest AS password=vmtest perm=524288000 spool=524288000;


CREATE SET TABLE vmtest.test ,
NO FALLBACK , 
NO BEFORE JOURNAL, 
NO AFTER JOURNAL, 
CHECKSUM = DEFAULT ( 
Test_field1 INTEGER,
Test_field2 INTEGER)
PRIMARY INDEX ( Test_field1 );

Create a file called testwith contents that look something like this:

1,1
2,2
3,3

Run the load utility:

/opt/teradata/client/13.0/tbuild/bin/tdload -f test -u vmtest -p vmtest -t test

That is it, data loaded!

Running Queries

You can use the Teradata Studio Express to run queries against the database. You can learn more about Teradata Studio Express, and download Teradata Studio Express versions for various platforms. Finally...

Please note that while Teradata Express for VMware is a free, unsupported product, you can talk to other users and ask for help over in the Cloud Computing forum. 

Teradata is announcing new Teradata Express 14.10 images. These new images are at patch level 14.10.00.02 which represents the current shipping version of Teradata 14.10. This gives you access to the recently released Teradata 14.10 database for your test and development needs.

Important

These images represent a departure from the from the TD 14.0 and TD 13.10 releases.

1. The SLES 11 image does not include Viewpoint. Viewpoint is not certified yet with SLES 11 so that it could not be included in the virtual container.


2. The SLES 10 image with Viewpoint requires a host computer with at least 8 GB of physical RAM. Viewpoint functionality has been greatly enhanced and now Data Labs portlets are included.


3. The SLES 10 image with Viewpoint is larger than previous TD Express images, 4.4GB compressed.


4. The installation instructions have been slightly modified. Please use the new version for TD 14.10.

New images:

• TD 14.10/SLES 11/40GB/No viewpoint, can run on a host machine with 4GB of RAM.
• TD 14.10/SLES 10/1TB/Viewpoint, requires a host machine with a minimum of 8GB of RAM.
   

A 64-bit virtualization-capable PC is required.  VMware provides a utility to check your system for 64 bit support at this link.

As before, 7-zip is required to uncompress TD Express images. Here

General details on the images remain the same as the original TD 14.0 and can be found here:

http://developer.teradata.com/database/articles/teradata-express-14-0-for-vmware-now-available

Instructions for running the images are slightly changed and can be found here:

http://developer.teradata.com/database/articles/teradata-express-14-0-for-vmware-user-guide

The new images are available at the down load page

Please note that while the Teradata Express family of products is not officially supported, you can talk to other users and get help in the Cloud Computing forum. Note also that Japanese-language instructions for configuring TDE-V are available for download in PDF format.

Statistics provides valuable information to the optimizer to make decisions on generating optimal explain plan.  The information about the statistics can be obtained by using the “Help Statistics” command however the displayed data cannot be used to join with other tables.  The article provides a java stored procedure and DDL which extracts the output of "Help Statistics" at Table and Column level and capture the data into tables. 

The captured data in the tables helps with:

1. Identifying old and stale statistics
2. Understand the data demographics in more detail
3. The data could be joined to DBQLObjTBL  for further analysis
4. The data could be used to generate test data
5. The data could be exported
6. Better understand the explain plan there is a detailed explanation of how the statistics are used in Teradata Manual “SQL Request and Transaction Processing”

Environment

The code was built and tested on:

• TD 13.10
• Linux 64-bit
• JDK 1.5

Installation & usage

1. Three files are provided in TeradataColumnStatistics.zip
   1. TeradataColumnStatistics.java(Java code)
   2. TeradataColumnStatistics.sql  (DDL to hold the table and column statistics)
   3. TeradataColumnStatistics.jar(JAR file of the compiled Java code)
2. Download the above files (always copy or move the TeradataColumnStatistics.jarfile in binary mode).
3. Make sure that the user has privileges to call SQLJ.INSTALL_JARand CREATE EXTERNAL PROCEDURE.
4. Create the two table provided in TeradataColumnStatistics.sql
5. Use bteq to execute the below commands:

   CALL SQLJ.INSTALL_JAR('CJ!/tmp/TeradataColumnStatistics.jar', 'TeradataColumnStatistics', 0); 
   
   /** Where /tmp is the directory the TeradataColumnStatistics.jar file resides */ 
   
   REPLACE PROCEDURE TableColumnStatistics
   
   ( INOUT db VARCHAR(32),INOUT tab VARCHAR(32) )
   
   LANGUAGE JAVA MODIFIES SQL DATA
   
   PARAMETER STYLE JAVA
   
   EXTERNAL NAME 'TeradataColumnStatistics:TeradataColumnStatistics.main';

6. To execute the JSP in bteq:

   CALL RETAIL.TableColumnStatistics('RETAIL','ITEM'); 
   
   /** RETAIL is the database name and ITEM is the table name */

7. Check the tables Help_Col_Statsand Help_Tab_Statsfor the data contents.

The java code could also be compiled on the Linux box

$/opt/teradata/jvm64/jdk5/bin/javac TeradataColumnStatistics.java

$/opt/teradata/jvm64/jdk5/bin/jar -cf TeradataColumnStatistics.jar TeradataColumnStatistics.class

Teradata Manual SQL External Routine Programming; Chapter 5 - Java External Stored Procedures discusses more about building and using Java stored procedures

Learn all about TD 14.10!

Learn about the new Optimizer enhancements, Incremental Planning and the anti-skew algorithm Partial-Redistribution and Partial-Duplication (PRPD), Teradata Intelligent Memory (TIM), Geospatial Indexing, Temporal Enhancements, Table Operators, SQL-H and Unity Source Link and other exciting capabilities. Teradata Database 14.10 represents the next major step in the evolution of data warehousing excellence.

Teradata Release Information: 14.10

Presenter: Rich Charucki, CTO Teradata Database – Teradata Corporation