Teradata Data Lab and Viewpoint 14.0 releases
Teradata is very pleased to announce the official release of the new product offering called Teradata Data Lab. At this same time, Teradata is releasing the new Teradata Viewpoint 14.00 version. These are two separate offerings just released in the same timeframe as a matter of convenience. Read below for information on both of these new Teradata offerings.
The primary goal of Teradata Viewpoint 14.0 is to support the Teradata Database 14.0 releases, both TD 14.0 on SLES10 and TD 14.0 on SLES11. The majority of this work was to provide the enabling interfaces for the TD 14.0 SLES11 new workload management stack. As such, the amount of "general" features was limited but there are still some additions of interest. Check out the Teradata Viewpoint 14.0 section below for more details. Lastly as always, the new Viewpoint release represents an integration of patch releases into the base release.
Aligned with this Viewpoint release is the very exciting new Teradata offering called Teradata Data Lab. Teradata Data Lab refers to work spaces or maybe better known as "sandboxes" within the data warehouse where users can explore, analyze new data, and test data value theories. Teradata Data Lab is a separately sold product that provides Viewpoint portlets that assist in governance, auto-provisioning, and monitoring of these "sandboxes". See below for more details on Teradata Data Lab and the Lab Group Setup and Data Labs portlets in this initial release.
As mentioned, Viewpoint 14.0 main focus was on the interface support of the Teradata Database 14.0 releases, and in particular the new workload management coming with TD 14.0 SLES11. Additional details on this new foundation will be included in future article aligned with the actual Teradata DB 14.0 SLES11 release. However there are other items of interest in this release. First related to Teradata DB 14.0 release, is the introduction of a significant number of new TASM state matrix events. As a quick review, the state matrix allows automated adjustment of TASM ruleset values associated to a state change, being either planned or unplanned. The new state matrix events are:
- System CPU Utilization
- System-wide Node Skew
By Workload Definition (WD) Events:
- CPU Utilization
- Missed Service Level Goal (SLG)
- Arrival Rate
- Concurrent Active Requests
- Delay Queue Size
- Delay Queue Depth
- Message Delay Time
The skew tab is a new option in the Query Monitor and My Queries portlets details view that provides CPU and I/O skew information and how it relates to specific AMPs. It lists the high and low impacted AMPs as well as an overall AMP participation count. So drilling down on a skew query provides you the new skew tab which will present information as shown below.
A challenge for any organization with a production data warehouse is how to allow for data proofing and new data value investigations while maintaining the relationships to production data. Bringing this concept data into production often becomes a contention between the need for flexibility and the IT processes necessary for protecting and staging data in the production environment. There is also the obstacle of the DBA feeling that they cannot take on the additional responsibility of managing a development environment and in particular, one that may have negative impact on production operations performance and service levels.
The end result often becomes exporting the production data out of the data warehouse consuming precious resources with very little value to the production environment itself. This data then moves into hidden infrastructure servers and client systems resulting in stale data, conflicting reports, outdated data models, as well as security and privacy adherence concerns.
Teradata Data Lab advocates providing space in the production environment for this effort with automated and distributed management and protected by built-in hooks into Teradata workload management strategies. Email is leveraged for notifications and intuitive Viewpoint portlet interfaces for everything. That's Teradata Data Lab. Continue reading for more details on the available portlets for this initial product release.
The first Data Lab portlet to discuss is the setup and configuration portlet called Lab Group Setup. Upon loading of this portlet, it will ask for Teradata credentials as you will need the necessary Teradata system permissions to define the lab space. Clicking on the "Add Lab Group" gets you started and then leads you through an easy five step process for setting up the lab group. As shown below, the first step allows configuration of the name, available space, default lab size, and a lab prefix that will be an easy integration mechanism with Teradata workload management.
Also notice the email notifications setup for easy automated "hands free" communications to the Data Labs users. Subsequent steps will allow configuration of Viewpoint ownership users and roles as well as Teradata user and roles access. Lastly step #5 will be setup of thresholds and approvers for various requests. This is where you decide on how open or controlled the lab is going to be. The example below is a mix of automation and manual controls.
If you have a plan on how you want the data lab environment to be established, setup through this Viewpoint portlet takes just a few minutes to complete. You can return to this portlet any time you need to view, edit, or delete lab group environments.
The Data Labs portlet will be used by DBAs, lab group owners, and user/consumers of data labs for creation, monitoring, and administration of data labs, in other words the on-going operations. Once connected to the associated Teradata system, the Data Labs portlet offers three main tabs (Monitoring, Approvals, Requests).
The Monitoring tab provides views at the lab group, lab, and table levels through easy point and click operations. Specific information is given at each of the levels for things such as size, ownership, expirations, etc accompanied by cylinder views for space usage. This is a view at the lab level:
The Approvals tab is what you would expect it to be. When a data lab request is made, it is added to a request queue for approval. You can view these unapproved requests within this tab if you are a lab group or lab owner. This is also where approvals or denials of requests are managed.
The third tab, Requests, is also what you might anticipate it is. This portlet is going to be commonly used by the user/consumers of data labs. Requests can be for a variety of data lab operations and necessities including:
- Add or delete labs
- Increase or decrease lab size
- Add or remove users from labs
- Add or remove owners from labs
- Extend lab expiration dates
- Promote or drop tables
- Change lab details
- Send other requests
Users can also review their requests within this portlet to understand status. Has it been approved, denied, or still pending? The portlet provides pull downs for easy lab group and lab filtering as well as operations for managing your requests. A simple example is shown below with various requests, in different states, and preparation for deleting one of the older requests.
One last item worth noting. The preferences for both Lab Group Setup and Data Labs portlets allow setting of thresholds for highlighting in the portlet views as well as configuration of optional email notifications.
That's Teradata Data Lab! See the Teradata Data Lab User Guide for more information.