RE: Temporal database feature on IBM i?

Temporal Tables are introduced with Release 7.3:
Creating a system-period temporal table
http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/sqlp/rbafycrttempora
ltable.htm

Working with system-period temporal tables
http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzahf/rzahftemporalt
able.htm


Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Freitag, 16. Dezember 2016 13:46
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Temporal database feature on IBM i?

Matt,

I was reviewing an old subject you brought up: Temporal tables on IBM i.
I believe you even submitted an RFE on it.

Have you implemented some? If not why not?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Matt Olson <Matt.Olson@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/08/2015 12:35 PM
Subject: Temporal database feature on IBM i?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Midrange users,

SQL 2016 will be introducing a temporal database feature which appears to
be journaling on steroids.

Apparently oracle already has this feature.

Just wondering what is the feature equivalent on DB2 for the i?

Here are screenshots of the feature:

http://i0.wp.com/blog.engineer-memo.com/wp-content/uploads/2015/05/image59.p
ng


http://i1.wp.com/blog.engineer-memo.com/wp-content/uploads/2015/05/image61.p
ng


You basically add a clause to your SQL that says "FOR SYSTEM_TIME AS OF
'date/time value'" at the end of your SQL and voila, you get a picture of
your table(s) as of a particular point in time. No reading cryptic
squished together fields in journals, just natural queryable data!

Not only that you can "stretch" your database to the cloud, so all
historical data is housed off site in presumably cheaper compute/storage
infrastructure rather than your expensive on-premise database. Which makes
sense for historical data since you are likely not looking at it very
often.