0 - 30 of 30 tags for temporal

Using Teradata Database 14.0.5 in a Virtual Machine and testing the following steps specified in a reference document, "Temporal Table Support" (Release 14.0) page 36 "Converting Period or DateTime Columns to a Transaction-Time Column", an error was encountered in an ALTER TABLE step to DROP the old PERIOD column: (Is there a missing step that will preven

Hi all,
I see some strange behaviour with some temporal operations which I can't explain myself.
I developed a macro to maintain a bi temporal table based on transaction data. 
The macro does the following steps:
1. delete all from a volatile temp table 
2. insert select from a non temporal table into the vt tmp table

I have a requirement to load the data from 2009 onwards and snapshots will be deilvered with a one week of gap starting from 2009-01-01. I am planning to use valid time temporal table to hold the data becuase business team wants to have time travel back capability in data. My input data snaps lookas as follows:
Data as of 2009-01-01

This error was received after executing the following DDL statement for bitemporal table:
 

CREATE MULTISET TABLE XXX.electronicaddress ,NO FALLBACK ,

     NO BEFORE JOURNAL,

     NO AFTER JOURNAL,

     CHECKSUM = DEFAULT,

     DEFAULT MERGEBLOCKRATIO

     (

      AddressId VARCHAR(100) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL,

Hi ,
  I am using SCD type 2 in my project.Below is the example of versioning which i maintain.
empno ename sal eff_dt  end_dt  curr_in rcv_in
1 a 100 2013-01-01 9999-12-31 1 1
Above is an active record because end_dt shows as high end date and curr_in shows as 1.

When during the course of a project, should you incorporate temporal features into the design of the database?  Should a roadmap be developed for projects to follow? 

Hello,

Data Warehouses are known for storing data over time, both historical point-in-time transactions as well as temporal data that is valid over a range of time...

When Teradata released its new temporal capabilities in 2010, it caused us all to start to thinking differently about the element of time in the Data Warehouse by providing powerful tools for managing and navigating temporal & bitemporal data structures. With the release of Teradata R14.10, we will be challenged still further.

Hi Everyone,
 
I am trying to write a SOFT RI between a bi temporal parent table and non Tempral child table but it is thoring me an error "Invalid referential integrity definition"
 

ALTER TABLE EMAIL

ADD CONSTRAINT ALE_SDRI_2  

 NONSEQUENCED VALIDTIME  

 FOREIGN KEY (LOCATION_ID) 

Hi
I need to track history of party addresses and created a temporal table for this.
CREATE MULTISET TABLE Employee_Addr_Hist (
Name varchar(100),
City varchar (100),
VT PERIOD(DATE) NOT NULL 
)
PRIMARY INDEX(name);

In this session, we explore the features and functions available in Teradata 14.0 that will have a direct impact on the business community.

Hi,
I have the following tables EMPLOYEE& DEPT.
I am writing the following query :
 
validtime as of date '2001-01-01'
select *
from SANDBOX.TEMPORAL_EMPLOYEE AS EMP
join SANDBOX.TEMPORAL_DEPT as dept
on emp.dept_id=dept.dept_id;
 
 

The Teradata Temporal feature, available with Teradata 13.10 allows the customer to capture, track, and analyze the full history of evolving business data rather than just the most current updates.

Hello,

I have a view that references a temporal table, i.e.

 

CREATE MULTISET TABLE P_SMA_T.myTable
(
    EffectivePeriod PERIOD(DATE) AS VALIDTIME
    ...
);

CREATE VIEW P_SMA.vt_myTable
AS
SELECT EffectivePeriod
    ...
FROM P_SMA_T.myTable;

 

Data Warehouses are known for storing data over time, both historical point-in-time transactions as well as temporal data that is valid over a range of time. Storing this data is one thing, but retrieving it to answer critical business questions can be a Structured Query Language (SQL) challenge...

I always get the 9388. error from the Teradata Database 13.10's Messages document:

I've found an appendix at the end of TD 13.10's "Temporal Table Support" reference, which contains some SQL code about how can you validating temporal referential integrity shown below. It works great until I want to embed it to a trigger's ...WHEN ( EXISTS (<here>))... section.

Teradata Database 13.10 is here and available today!

I've read the most relevant references from the TD 13.10 documents, but as I see, only soft RI-s are available with temporality - so you must do it yourself...

Which is the most acceptable (and also the simplest) solution maintaining RI's between temporal tables? TRIGGERs?

Learn how to make your Teradata Data Warehouse a virtual time machine!

The PERIOD data type was introduced in Teradata 13.0. This follow-on article builds on the first article (Exploring Teradata 13's PERIOD Data Type) and will again make heavy use of examples, but this time we will dig into the functions that are part of this new feature set.

If you have not read the first article, consider doing that now and then returning here. The examples here will use the tables introduced in the first article and add a few more.

This session describes the temporal database model. Temporal support is new to any major database vendor. Teradata 13.10 provides internal support for defining temporal objects such as tables, views, macros, and how to maintain and query them.

Dear Teradata fan community,

we know, that since release 13.10 there exists temporal capability within the database. My understanding specially about the transaction time is, that this data will be handled automatically within the DBMS as described as follow:

"A transaction-time column records and maintains the time period for
which Teradata Database was aware of the information in the row.
Teradata Database automatically enters and maintains the
transaction-time column data, and consequently automatically tracks
the history of such information."

The PERIOD data type was introduced in Teradata 13.0. This first article will use examples to dig into the concepts that are part of this new feature. The second article will use examples to examine all the functions available in version 13.0.

Time is one of the most powerful dimensions a data warehouse can support. Unfortunately it’s also one of the most problematic. Unlike OLTP environments that focus on only the most current versions of reference data, DW environments are often required to present data not only as it currently exists, but also as it previously existed. Implemented correctly, a data warehouse can support several temporal orientations, the three most common being “current,” “point-in-time,” and “periodic.” Implemented incorrectly, you will create a solution that will be impossible to maintain or support.

Time is one of the most powerful dimensions a data warehouse can support. Unfortunately it’s also one of the most problematic. Unlike OLTP environments that focus only on the most current versions of reference data, Data Warehouse environments are often required to present data not only as it currently exists, but also as it previously existed. Implemented correctly, a data warehouse can support several temporal orientations, the three most common being “current,” “point-in-time,” and “periodic.” Implemented incorrectly, you will create a solution that will be impossible to maintain or support.

While organizations store temporal data that is in effect over a period of time, efficiently querying that data to provide business insights can be a challenge.

More than likely, you need to keep track of the beginning and ending of some kind of an event. Maybe you track how long employees have been with your company, how much time users spend on a particular web site, or the duration of insurance policies.