Re: i 7.3 and COMMON -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Yeah, temporal support is known from the get-go to take more disk space - the historical data has to be kept somewhere.

Captain Obvious says, "Just don't set it up on a column that changes a lot!!" Price lists, dimension tables, that kind of thing - other suggestions?

Vern

On 4/13/2016 6:00 AM, Rob Berendt wrote:

I agree. Definitely more disk intense. CPU intense? IDK how one would
even begin to get that impression.

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: Arco Simonse <arco400@xxxxxxxxx> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> Date: 04/12/2016 04:41 PM Subject: Re: i 7.3 and COMMON Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> My feeling is that it is more diskspace intentse... We have done some homegrown temporal emulation in our shop, and the history writing (the way we did it) is just a bunch of triggers, not so cpu intensive. The querying is another story, and I guess they will have optimized the SQE for that :-) Regards, -Arco

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.