MVISAM Advice solicitation

[Ben Duncan]

Boils down to this:

One File Method:

PROS's: Record locking and file access simplier to implement
and maintain. Less code to produce, lower memeory overhead from not
having multiple buffers to maintain. Easier to transport from
on machine to another or one partition to another.

CON's: Get beaten to death when multi users are accessing, due to
head movement all over the place. IF/When corruption occurs, is a
major BITCH to recover due to co-mingled index and data nodes.

Two File Method:

PROS': Seperate Index and Data nodes mean in the event of a
corruption, is easier to recover by simple parsing and rebuilding
from the data file. Does not get beaten to death so bad when
in multi user mode. Index File can be totally memory mapped.

Cons's: All code will have to have been duplicated. Once for the
Index access and one set for the data access. Record and file locking
will be more complex due to 2 file structure. Copying / Moving
data files around will require the user be aware of two files,
instaed of one.


Any more Pro/Cons anyone can see?

Thanks ...

Mike Reinehr wrote:
> On Monday 30 October 2006 12:36, Ben Duncan wrote:
<SNIP>
> 
> That's good to know. I guess the answer to your quesition is, as usual, it 
> depends upon the application.
> 
> Cheers!
> 
> cmr

-- 
Ben Duncan   - Business Network Solutions, Inc. 336 Elton Road  Jackson MS, 39212
"Never attribute to malice, that which can be adequately explained by stupidity"
        - Hanlon's Razor