Teradata 13.10

download Teradata 13.10

of 43

  • date post

    20-Aug-2015
  • Category

    Documents

  • view

    19.131
  • download

    1

Embed Size (px)

Transcript of Teradata 13.10

  1. 1. Teradata Database 13.10 Overview Todd WalterCTO Teradata Labs
  2. 2. Fine Print
    • Nothing in this presentation constitutes a commitment to deliver any specific functionality at any specific time.
    • Current planning date for 13.10 release in Q32010.
  3. 3. Key Features
  4. 4. What is a Temporal Database Definitions
    • Temporal the ability to store all historic states of a given set of data (a database row), and as part of the query select a point in time to reference the data. Examples:
      • What was this account balance (share price, inventory level, asset value, etc) on this date?
      • What data went into the calculation on 12/31/05, and what adjustments were made in 1Q06?
      • On this historic date, what was the service level (contract status, customer value, insurance policy coverage) for said customer?
    • Three Types of Temporal Tables
      • Valid Time Tables
        • When a fact is true in the modeled reality
        • User specified times
      • Transaction Time Tables
        • When a fact is stored in the database
        • System maintained time, no user control
      • Bitemporal Tables
        • Both Transaction Time and Valid Time
    • User Defined Time
      • User can add time period columns, and take advantage of the added temporal operators
      • Database does not enforce any rules on user defined time columns
  5. 5. Temporal QueryProvide a list of members who were reported as covered onJan. 15, 2000 in the Feb. 1, 2000 NCQA report, with names asaccurate as our best data shows today. SELECTmember.member_id, member.member_nm FROMedw.member_x_coverageVALIDTIME AS OF DATE 2000-01-15 AND TRANSACTIONTIME AS OF DATE 2000-01-01 ,edw.member WHERE member_x_coverage.member_id = member.member_id; select member.member_id ,member.member_nm from edw.member_x_coverage coverage ,edw.member wherecoverage.member_id = member.member_id andcoverage.observation_start_dt '2000-02-01' or coverage.observation_end_dt is NULL) andcoverage.effective_dt '2000-01-15' or coverage.termination_dt is NULL) With Temporal Support Without Temporal Support
  6. 6. Temporal Update BiTemporal Table
    • With Temporal Support
    • UPDATE objectlocation
    • SET LOCATION = External
    • WHERE item_id = 125
    • AND item_serial_num = 102
    • Without Temporal Support
    • INSERT INTO objectlocation
    • SELECT item_id, item_serial_num, External, CURRENT_TIME, END(vt), CURRENT_TIME, Until_Closed
    • FROM objectlocation
    • WHERE item_id = 125 AND item_serial_num = 102
    • AND BEGIN(vt) CURRENT_TIME
    • AND END(tt) = Until_Closed;
    • INSERT INTO objectlocation
    • SELECT item_id, item_serial_num, location, BEGIN(vt), CURRENT_TIME, CURRENT_TIME, Until_Closed
    • FROM objectlocation
    • WHERE item_id = 125 AND item_serial_num = 102
    • AND BEGIN(vt) CURRENT_TIME
    • AND END(tt) = Until_Closed;
    • UPDATE objectlocation
    • SET END(tt) = CURRENT_TIME
    • WHERE item_id = 125 AND item_serial_num = 102
    • AND BEGIN(vt) CURRENT_TIME
    • AND END(tt) = Until_Closed;
    • INSERT INTO objectlocation
    • SELECT item_id, item_serial_num, External, BEGIN(vt), END(vt), CURRENT_TIME, Until_Closed
    • FROM objectlocation
    • WHERE item_id = 125 AND item_serial_num = 102
    • AND BEGIN(vt) > CURRENT_TIME
    • AND END(tt) = Until_Closed
    • UPDATE objectlocation
    • SET END(tt) = CURRENT_TIME
    • WHERE item_id =125 AND item_serial_num = 102
    • AND BEGIN(vt) > CURRENT_TIME
    • AND END(vt) = Until_Closed
    Current valid time, current transaction time Query Jeans (125,102) are sold today (2005-08-30)
  7. 7. Moving Current Date in PPI
    • Description
      • Support use of CURRENT_DATE and CURRENT_TIMESTAMP built-in functions in Partitioning Expression.
      • Ability to reconcile the values of these built-in functions to a newer date or timestamp using ALTER TABLE.
        • Optimally reconciles the rows with the newly resolved date or timestamp value.
        • Reconciles the PPI expression.
    • Benefit
      • Users can define with moving date and timestamps with ease instead of manual redefinition of the PPI expression using constants.
        • Date based partitioning is typical use for PPI.If a PPI is defined with moving current date or current timestamp, the partition that contains the recent data can be as small as possible for efficient access.
      • Required for Temporal semantics feature provides the ability to define current and history partitions.
  8. 8. Time Series Expansion Support
    • Description
      • New EXPAND ON clause added to SELECT to expand row with a period column into multiple rows
        • EXPAND ON clause allowed in views and derived tables
      • EXPAND ON syntax supports multiple ways to expand rows
    • Benefit
      • Permits time based analysis on period values
        • Allows business questions such as Get the month end average inventory cost during the last quarter of the year 2006
        • Allows OLAP analysis on period data
      • Allows charting of period data in an excel format
      • Provides infrastructure for sequenced query semantics on Temporal tables
  9. 9. Time series Expansion support
    • What will it do?
      • Expand a time period column and produce value equivalent rows one each for each time granule in the period
        • Time granule is user specified
        • Permits a period representation of the row to be changed into an event representation
      • Following forms of expansion provided:
        • Interval expansion
          • By the user specified intervals such as INTERVAL 1 MONTH
        • Anchor point expansion
          • By the user specified anchored points in a time line
        • Anchor period expansion
          • By user specified anchored time durations in a time line
  10. 10. Geospatial Enhancements
    • Description
      • Enhancements to the Teradata 13 Geospatial offering drastically increasing performance, adding functionality and providing integration points for partner tools
    • Benefits
      • Increased performance by changing UDFs to Fast Path System functions
      • Replace the Shape File Generator client tool (org2org) with a stored procedure for tighter integration with the database and tools such as ESRI ARCGIS
      • Provide geodetic distance methods SphericalBufferMBR()
      • WFS Server provides better tool integration support for MapInfo and ESRI products
  11. 11. ESRI ArcGIS Connecting to Teradata via Safe Software FME
    • FME connection in
    • ArcView
    • 2.Connect to Teradata via TPT API
    • Select Teradata
    • tables for ArcView analysis
  12. 12. Projection of Impact Zone& Storm Path to Google Earth Where do I deploy my cat management team.
  13. 13. Algorithmic Compression
    • Description
      • Provide the capability that will allow users the option of defining compression/decompression algorithms that would be implemented as UDFs and that would be specified and applied to data at the column level in a row. Initially, Teradata will provide two compression/decompression algorithms; one set for UNICODE columns and another set for LATIN columns.
    • Benefit
      • Data compression is the process by which data is encoded so that it consumes less physical storage space. This capability reduces both the overall storage capacity needs and the number of physical disk I/Os required for a given operation. Additionally, because less physical data is being operated on there is the potential to improve query response time as well.
    • Considerations
      • At some point, compressed data will have to be decompressed when