This article is the official release announcement for Teradata Data Lab 14.01 (the second product release) with an effective release date of October 12th, 2012. As a reminder, Data Lab provides automation, management, and governance for sandboxing within a Teradata production system. Here's the link to the initial Data Lab 14.0 release article in case you want to review all the product features.  


The primary focus of this second release of Data Lab was addressing feedback from the early adopters inspiring Teradata to improve performance (more data caching), add a new automated lab deletion option, and a re-architecture of the Data Labs portlet interface to support ease-of-use and large numbers of labs. Worth noting, Teradata Data Lab 14.01 requires Viewpoint 14.01 release to run.

Lab Deletion

In the initial release of Teradata Data Lab, the product offered an expiration feature for automated management of labs in a lab group. This expiration, assuming there was no approved extension, would remove access permissions to the lab. As such, the deletion of a lab was always a manual operation. With Data Lab 14.01, we are complimenting the expiration with an automated deletion option. The new automated delete will offer a wait duration of an expired lab before automatically deleting it. The Lab Group Setup portlet below shows the options for wait times prior to an automated delete including a "Do not delete" for those that want deletions to remain a manual operation. 

Similar to the expiration email notification, an email notification is also sent to the lab owner informing them that their expired lab has now been deleted. 

Data Labs Update

The Data Labs portlet has some nice enhancements with the Data Lab 14.01 release for ease of use, better navigation, and support for large numbers of labs. Here is the new view of the Data Labs portlet "Monitoring" tab:

For comparison, below is a screen shot of the prior Data Labs "Monitoring" view. The first thing you may notice is that the revolving "cylinders" display has been replaced by a lab group space usage bar chart within a reporting column. As cool as the revolving cylinders were, they didn't scale well for large numbers of lab groups. The more lab groups, the more spinning one had to do which became cumbersome for navigation. With the new design, you not only can see more lab groups in a single view but can leverage the benefits of the newly implemented data grid architecture. If you already know Viewpoint, then the data grid architecture should be familiar to you (portlets like Query Monitor, Space Usage, Alerts Viewer, etc.). So you have all the data grid benefits now including filtering and sorting capability as well as display configuration customization (down arrow in the upper right of the grid) for selecting columns and display order. 

We didn't completely abandon the cool cylinders concept however as they reappear when one drills down into the lab or table detail views. As a reminder, the detailed views provide more information for labs and tables including a third level drill down that displays a sample of the table data. 

That is the new version of Data Lab 14.01. Let us know if you have additional ideas in how we can enhance this offering going forward.



bs520147 12 comments Joined 04/12
05 Mar 2013

How can I get this version?. I have a virtual Machine with viewpoint installed with the portlets related to Data Lab.

bs520147 12 comments Joined 04/12
05 Mar 2013

I don't know if the following problem is due to the version of my portlets of Data lab. I have 2 Lab Groups: 'Marketing' and 'Ventas'. Each Lab Group has an owner, this means I have 2 users. These 2 users have the 'Data Lab portlet' available.
When I access to viewpoint with the user of 'Marketing', I can see the 'Data Labs' defined for 'Marketing Lab group'. This is correct, but when I try to add a new Data lab, I can select 'Ventas Lab Group' as 'Lab group' associated to my new Data Lab. I consider that this is an error, because the 'Marketing user' isn't the owner of 'Ventas Lab Group'.

gryback 151 comments Joined 12/08
05 Mar 2013

For clarity, customers need to order the Data Lab product.

Regarding the second question, unless you make a Lab Group private, others can see it and submit requests.

12 Mar 2013

We're using Viewpoint V14.01.00.00-b29. An automated Data lab request failed (owner spool too small). Once we fixed the spool space error, it went thru OK. We received no notification of either event, so:
1. Should we have received notifications and,
2. If not, could this functionality be added?


gryback 151 comments Joined 12/08
13 Mar 2013

Currently, there is no mechanism in Data Lab to notify on spool space errors. We could consider this although it will take some analysis to see how the Teradata error would be passed back through Viewpoint. Please submit a Support Services incident to consider this enhancement request. Having it directly submitted by the customer will help in prioritization. Thanks.

ahnajeeb 2 comments Joined 03/11
28 Mar 2013

Teradata needs to add some requirements to next version.  VIEWPOINT GUI can not be the  only selling point.  Can it report on Capacity Usage (DISK/CPU-  The data is there in Viewpoint). Also more controls should be added for Access and Workload Management. Needs to have option to be hooked up with TASM more easily.


gryback 151 comments Joined 12/08
28 Mar 2013

Don't underestimate what the Viewpoint portlets enable. These are more than just a pretty face. 
You mention the need for access and workload management but that is already part of the architecture. You can distribute control of a lab group through Viewpoint access management, there's a privacy offering to restrict users / visibility into a lab group, and the ability to control Teradata users in a lab group or lab with read-only or update capabilities. This is all built-in features when creating a lab group.
For workload management, we didn't want to create another tool but do provide the prefix integration point to easily integrate into the associated workload management of the Teradata system simply through wildcards. So one can filter, throttle, assign resource priorities, or create exceptions for bad behaving queries in the data labs. If TASM workload definitions (WDs) are setup specifically for data lab access, one can then use the Workload Health portlet to chart metrics for Data Lab WD queries. 
Check out this most excellent DevX article on TASM integration:
Related to management is the governance features of Data Lab including optional lab automated expirations and deletions as well as space management features all of which are integrated with automated email notifications. Data Lab also sends you email providing status on your data lab requests and approvals. Lastly, we recently added the Data Lab easy loader / table creation tool into Teradata Studio Express. This is a huge enabler for those interacting with their labs.
We are always open to new requests but I do believe we have already addressed many of the items that you are asking for. The Data Lab user guide will cover all the aspects mentioned here in more detail to help with further understanding if necessary. 

You must sign in to leave a comment.