RE: Temporal database feature on IBM i?

This sounds like you would need to keep all journals online for as far back as you might ever want to look at historical data. It sounds like a very useful function for us as Higher Education always has government reporting requirements that are based on a specific date. And data changes all the time so trying to reproduce a report that was based on data from a year or two ago on a specific date is very problematic.  I guess disk is cheap so we could get a few more terabytes to keep the journals online. 

Mike Cunningham 

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Friday, May 08, 2015 2:09 PM
To: Midrange Systems Technical Discussion
Subject: Re: Temporal database feature on IBM i?

Hi Matt

I really like the idea of temporal functionality - it'd be very cool for price change history.

The word from IBM about new development in database is as follows -

The DB2 for i technical leaders (Mark & Scott) regularly review and revise the DB2 for i product strategy and enhancement plan.
They just announced DB2 for i enhancements that are being delivered on the same cadence as TR2 (7.2) and TR10 (7.1).
Customers are encouraged to follow
www.developerworks.com/ibmi/techupdatesto stay current with IBM i enhancements.

I know that doesn't directly answer your question - still, the idea is to stay tuned on that site - and I believe you can post your thoughts there - maybe!!

HTH
Vern

On 5/8/2015 11:34 AM, Matt Olson wrote:
> 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/ima
> ge59.png
>
> http://i1.wp.com/blog.engineer-memo.com/wp-content/uploads/2015/05/ima
> ge61.png
>
> 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.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.