Very helpful Stuart (and Brian) thanks.
1 follow-up question: given your algorithm below, when you edit or copy those
records over, what does the key look like. E.g. do you have to prefix the key
generated by your algorithm, with the part file number or name? To edit the
record would you
Hi Baker
Unless I misunderstand the question - it don't work like that :)
UniVerse uses the partitioning algorithm to determine which part file the
record goes into, based on some operation performed on the key that must
yield as its result a valid part file number. So you could, for example,
In message
0f0fc5f04b472746b01fa2c4897cf972beb5364...@excl01.mouser.lan, Baker
Hughes baker.hug...@mouser.com writes
Very helpful Stuart (and Brian) thanks.
1 follow-up question: given your algorithm below, when you edit or copy
those records over, what does the key look like. E.g. do you
We use one part file made up of 13 different files. The record key makes it
easy for us because they are all numeric. We just made the algorithm
MOD(key,13) + 1. The reason for 13, it's a prime number and the number of
records per file seem to come out about equal. Of course we don't have a
I will be out of the office starting 05/28/2009 and will not return until
06/08/2009.
I will respond to your message when I return.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
It's really useful for archiving if the key contains a date - build the
algorithm on the date in the key and have a separate partfile for each year
(or quarter or month - you get the idea),
When you want to archive old data you just drop the partfile concerned -
remembering to add new partfiles
Thanks JayJay, Wol, Jerry Brian for enlightening. The UV docs on distributed
files are extremely sparse, so the peer experiences are essential to a good
strategy.
JJ's comment about adding archive part files whose key does not fit the
algorithm already in place is what I ran into.
-Baker
Hi All
I am trying to resize a large dynamic Unidata file for a customer but am
struggling to determine the best modulo/seperation figures to use. I
was under the impression that I should try and minimise the amount of
overflow files but my latest attempt just seems to have made the file
worse.
Try the HASH.HELP command (and related commands)
--B
-Original Message-
From: owner-u2-us...@listserver.u2ug.org
[mailto:owner-u2-us...@listserver.u2ug.org] On Behalf Of Andrew Nicholls
Sent: Thursday, May 28, 2009 6:17 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] Resize of large
The keys never change.
AE HAIRY.PF.NAME B123456 is always AE HAIRY.PF.NAME B123456 until the
part file is archived off. Then it disappears from the DF.
Just to clarify, this part algorithm for this DF assumes you have
sequential keys and have created parts 1-20. It takes the 6th most
significant
We too do not use memresize to rebuild dynamic files. We have a process
that select the original file, breaks the subsequent list up into parts
and have phantom simultaneously copy records into the new file based on
the portion of the original list that that an individual phantom is
given. We have
11 matches
Mail list logo
