Licensing

[Mike Fedkiw]

Now I'm confused about the extent thing. If I just go into the directory that has the big key file and rename it how what do I need to do with the data file, rename that too. Also, how would I be able to get the x2 or x3 keys and data created? I'm running Windows server 03 and sorta lost trying to figure out what a separate file system could even be. 

Mike 

On Jul 1, 2014, "Brian K. White" <brian at aljex.com> wrote:
>On 6/28/2014 7:02 PM, Jean-Pierre A. Radley wrote:
>> Mike Schwartz propounded (on Sat, Jun 28, 2014 at 09:48:00AM -0500):
>> |
>> | >> Fp, in the days of smaller drives, allowed for adding key/data
>extents to
>> | the same or different drives.  Today with the larger drive
>capacity, the
>> | only time one would want to do this is when the file size is
>nearing the 2GB
>> | limit on a 32bit OS.
>> | >>
>> | >> I don't recall exactly what the naming convention is for these
>extents.
>> |
>> | > Yea, please explain what extents is.
>> | >
>> | > Thanks, Mike
>> |
>> |
>> |       At this point you will have a CUST file that has (roughly) a
>> | 1-Gigabyte "key" segment and a 1-Gigabyte "data" segment in it, but
>the file
>> | will contain all the data from your original CUST database and it
>willlook
>> | and operate exactly like your original CUST file did.
>> |
>> | Hope this doesn't confuse you further...
>>
>>
>> Well, it confused me, a bit...
>>
>> Mike, you took a database with a key file but a zero-length data file
>> and moved about half the key files's fields into the data file.  If
>you
>> reached an OS-imposed 2GB limit in the key file, sure, you would now
>> reach the 2GB limit on either the key file or the data file,
>>
>> But that's not what I ever understood by extents.  FilePro can
>generate
>> (in addition to key and data) keyx1 &datax1, keyx2 & datax2, keyx3 &
>> datax3. Instead of hitting a 2GB limit on on a single file, you will
>be
>> limited to 2GB on any one of the eight files, filePro sees the
>database
>> with such extents as having a big virtual concatenated key file (and
>if
>> present, a concatenated data file).
>
>Exactly.
>
>> You need to have additional filesystems to exploit this capability.
>
>We use extents without any extra filesystems.
>
>Or are you just saying the automatic creation only works on separate 
>filesystems?
>
>It may be that fp will do something a little more automatic like you
>described, automatically creating x2 & x3 if x1 exists and there are 
>extra filesystems listed in PFSOMETHINGOROTHER> I've never tried it.
>But 
>we just have one fs and we create the x files ourselves and it works.
>
>And I believe I was wrong about going up to x9. x3 only.

-- Sent with K-@ Mail - the evolution of emailing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20140701/1abaace4/attachment.html