Teradata rolled out Teradata Data Labs (TDL) in Teradata 14. Though it is not a high-profile enhancement, it is worth understanding for not only Teradata data warehouse customers, but also for all data warehouse programs as a signal for how program architectures now look. Teradata Data Labs supports how customers are actually playing with their resource allocations in production environments in an effort to support more agile practices under more control by business users.
TDL is part of Teradata Viewpoint, a portal-based system management solution. TDL is used to manage "analytic sandboxes" by these non-traditional builders of data systems. Companies can allocate a percentage of overall disk and other resources to the lab area and the authorities can be managed with the TDL. By creating "data labs" and assigning them to requesting business users, TDL minimizes the potential dangers of the "can of worms" that has long been opened, supporting production create, alter and delete activity - not just select activity - by business users.
These sandboxes must be managed since resources are limited. Queries can be limited, various defaults set and, obviously, disk space is limited for each lab. Expiration dates can be placed on the labs, which is not dissimilar to how a public library works. Timeframes will span a week through a year. The users may also send a "promotion" request to the labs manager, requesting the entities within the lab be moved out of labs and into production.
Data labs can be joined to data in the regular data warehouse. One Teradata customer has 25% of the data warehouse space allocated to TDL.
TDL can support temporary processing needs with strong resources - not what is usually found in development environments. I can also see TDL supporting normal IT development. Look into TDL, or home-grow the idea within your non-Teradata data warehouse environment. It's an idea whose time has come.
TDL is backward-compatible to Teradata 13.
Posted April 17, 2012 9:38 AM
Permalink | No Comments |