The Teradata Data Lab 15.11 release is now available with formal GCA release in early November 2015. This article will discuss the latest enhancements. Note that Data Lab 15.11 was a relatively "light" release due to the significant changes made in the Teradata Data Lab 15.10 release in both visualization as well as feature functionality. There is still some good stuff here however so read on.
To review, the key concept around Teradata Data Lab is to stop moving production data out of production to feed analytical islands, such as spread marts or data marts. Instead, move the analytical proofing data into a production intelligent sandbox environment where Data Lab provides production protection for the DBA while allowing self-service provisioning and governance capabilities desired by the analytical community. A much better approach in terms of data security, user efficiency, system resource usage, and proofing confidence to name just a few of the benefits.
This latest release of Data Lab provides some nice updates but as mentioned was a light release to allow some settling due to the extensive changes in the Data Lab 15.10 release. This article will discuss four new features released with Data Lab 15.11, those being:
So let's take a look at each of these in more detail.
Teradata Data Lab has always had the concept of an “expiration date” for data labs which included the ability to request an extension to postpone the expiration. However some customer situations encountered where the expiration date actually wanted to be moved in instead of moved out. For instance, when a lab group owner inadvertently approves a longer extension than desired. When this happened in previous releases, there was no easy way to expedite or pull in that extended date. This new feature allows data lab owners to change the expiration date to an earlier date through a simple menu modification option. This new feature however does not allow one to extend the date. In short, the data lab extensions work the same as they did before. This new option is offered as part of the Edit Lab Details selection as shown below which is only visible if you have full permissions to the data lab. Note the expiration date for the Americas data lab is a year later than the Asia and Europe data labs and let's say therefore needs an adjustment.
Below is the updated "Edit Lab Details" screen including the new section stating the existing data lab expiration date and the ability to set a new expedited (earlier) expiration date. A request for a later date will result in an error stating that the "New expiration must predate current expiration".
Teradata Data Lab offers two types of access (read-only or full permissions) at two different levels (lab group or data lab). The ability to easily view these access levels was added in the Data Lab 15.10 release through the "View Lab Group Details" and "View Lab Details" requests. Worth reminding everyone that these views are not defaults and need to be enabled within the configuration of each lab group through a simple checkbox. With Data Lab 15.11 release, we modified the "View Lab Details" to display two sections, one for access at the data lab level and another for displaying access from the lab group level. This now presents a full view of who has access and from what level has it been granted. Here is an example of the new "View Lab Details" access display:
The new Data Lab “Access Reports” (offered as a new tab in the Data Labs portlet) provide an easy way for permission enabled users to understand Teradata Database access rights within the Teradata System Data Lab infrastructure. So the ability to easily see user access across all aspects of a lab group or lab groups without the need to individually look at each data lab for understanding set access. The “Report type” includes three options: User, Role, and Lab group to report on user access, role access, or all access within a specified lab group or groups. One could use these new reports for example to get an access layout of an entire lab group or to understand where a particular user has access to across all lab groups. As an example, here is creation of a report to determine where Ann and Sam have access and associated permission:
And the resulting report. Note there is an export option if this information needs to be used outside of Viewpoint.
As mentioned, viewing Data Lab Access Reports is a permissioned operation within Viewpoint Administration - Roles Manager and specifically within the Data Lab settings. This is the same location for granting lab group modification privileges.
This new process solution leveraging the new “migratedatalabssystem” command can be used in conjunction with Teradata DB System “floor sweeps / system migrations” where a new Teradata Database System is replacing an older Teradata Database System and where the customer also wants their Data Lab environment to migrate to the new system. There are two parts for success here. The first is that the Teradata DB system – Data Lab objects, users, roles, etc. must move over as part of the Teradata DB system NPARC. The second portion is a migration of the Viewpoint “Data Lab” infrastructure within the Viewpoint instance (must be Viewpoint / Data Lab 15.11 version). This is the new process where we can now automatically migrate the “Data Lab” infrastructure with the floor sweep. Some points to understand about this new feature. The Viewpoint “Data Lab” migration must occur on the same Viewpoint instance so there is no export / import from one Viewpoint instance to another. Also this feature should not be perceived as a “quick start” way to implement a new Data Lab environment as it is a transfer of the infrastructure, not a copy. The process for a Data Lab migration is documented in the Teradata Viewpoint Software Installation, Configuration, and Upgrade Guide for Customers, Release 15.11.
Some compatibility aspects worth mentioning. Data Lab 15.11 requires Viewpoint 15.11 and vice versa. Viewpoint and Data Lab 15.11 are supported with the following versions of Teradata Database (15.10, 15.00, 14.10, 14.00, 13.10). Teradata Data Lab is not currently offered with Aster or Hadoop systems.
Thanks for taking the time to peruse this article!
I have 2 questions on Data Lab:
Q1: is it compatible with (meaning is it installable on) appliances (say 2750, for instance) ?
Q2: is Data Lab free of charge for existing Teradata Customers or do we need to buy extra licensing ?
We have a lot of existing sand box databases in prod for developers, is there anyway to move these databases to a lab group or lab and then have the objects or administration of the databases available through the data labs portlet ? From what I can see I don't think it's possible, but thought I'd ask first. If I GIVE an existing database to a lab, it's objects are not visible to the lab through the portlet, so I think the only way would be to recreate all the objects from the existing database to a new lab database, however then this causes issues with having to grant security rights to the new lab as well.
Probably best to leave existing sand boxes as is and all new ones to be created through data labs.