Teradata Temporal Table Support

Planned

Comments

4 comments

  • Official comment
    Avatar
    Neil Buchwalter

    Burcu - 

    The upcoming version of erwin DM (r9.7) which is currently undergoing Customer Validation Testing will support this. Below is a picture of the model generated by your DDL.

     

    ***NEIL***

     

    Comment actions Permalink
  • Avatar
    Jason Shangold

    • Temporal is a very popular feature in Teradata. Erwin should be enhanced to support this new Teradata data type.

    • yvonne95

      We have recently been tasked to add temporal capabilities to our most recent data warehouse.  We are having to manually modify our DDL.  If someone finds a way to automate this update please reply to my comment.  thanks

      • RJ_Wood

        We have implemented the transactiontime by creating a Domain and then dragging that into each table.  Creating a Domain will allow you to populate all the values you need and then the DDL will create with the proper values.

        • mweaver.1

          Hey RJ!

           

          Thanks for the tip.  I’ll definitely have to try it out.  Sounds like a good work around until CA builds it into the tool.

           

          Mark

    • Burcu Orbay

      Hi All,


      Thank you so much for sharing the workaround.

      If I need both the ValidTime and the TransactionTime in a table, how do you recommend configuring the domains?

       

      In the below example, I cannot name the domain as "PERIOD FOR VALID_TIME" or "PERIOD FOR TRANSACTION_TIME"as ERwin converts the column names to "PERIOD_FOR_VALID_TIME" and "PERIOD_FOR_TRANSACTION_TIME", respectively.

       

      I am wondering if the best option is to handle this in fet templates.

       

      Thanks,

      Burcu

       

      CREATE  TABLE Staging_Bitemporal

      (

        SOME_CODE VARCHAR(10),

        VALID_START_TS       TIMESTAMP WITH TIME ZONE NOT NULL,

        VALID_END_TS         TIMESTAMP WITH TIME ZONE NOT NULL,

        START_TS             TIMESTAMP WITH TIME ZONE NOT NULL,

        END_TS               TIMESTAMP WITH TIME ZONE NOT NULL,

        PERIOD FOR VALID_TIME(VALID_START_TS, VALID_END_TS) AS VALIDTIME,

        PERIOD FOR TRANSACTION_TIME(START_TS, END_TS) AS TRANSACTIONTIME

      );

    0
    Comment actions Permalink
  • Avatar
    Tom Verstraete

    Neil Buchwalter, are these same datatypes available in 9.7 for SQL Server 2016?

    0
    Comment actions Permalink
  • Avatar
    Neil Buchwalter

    Only valid SQL Server 2014 datatypes are valid in r9.7 even for SQL Server 2016. We are planning on providing SQL Server 2016 feature/functionality support in our next product release. 

    ***NEIL***

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk