Re: The problem with SAVCHGOBJ . . .

Regarding B...

Someone will correct me if I'm wrong, but IIRC if you happen to have
those history files set up as multi-member (ideally as a SQL
partitioned file) then a SAVCHGOBJ will only save the member(s) that
have changed.

So you could conceivable cut way down on the "changed" data being save
vs. a full save.

HTH,
Charles

On Mon, May 10, 2010 at 1:18 PM, <rob@xxxxxxxxx> wrote:

What is one's restore plan with SAVCHGOBJ?

Scenario 1:  Hosed up file A in library B.
Check out the last save date.  Use media from that time period.

Scenario 2:  Have to restore an entire library.
Restore from GO SAVE 21.  Restore from every daily SAVCHGOBJ starting with
oldest to newest?

We briefly looked at SAVCHGOBJ.  We decided that
A - It complicated a restore.
B - So many things are changed daily that it really didn't save us much
time.  For example, let's say the biggest items in your file library are
the item master, item history, sales history, customer order and customer
order line file.  Can anyone imagine a "going concern" not having those
changed on a daily basis?

However, I ran a little sql.  Apparently 85% (by size) of our objects are
not changed daily.  And that's just in our file library for BPCS.


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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.