Using stacks as a database for very large data sets

[Klaus Major]

Hi Jonathan,

> I guess huge is relative to the speed of one's system and network. The
> stack I am dealing with is only 4.74mb - yet, it still takes a couple
> minutes to save across the network.
>
> That's no big deal - but a year from now the same stack will be 20meg,
> and will take 8 minutes to save. I am planning on working out an
> archiving system before I get to that point.
>
> Separate monthly stacks is probably my easiest and best bet. I was just
> wishing for the ideal - the ability to have a 40 gig database in a
> single stack, with all the easy searching and reprogramming that would
> go with that.
>
> Maybe for Rev 3.0 they will work out such a thing.

just an idea:
Does copying a file also take that long over the network?
I guess not, i think i read "Gigabit" somewhere...

In that case you could copy the file onto your HD temporarily, edit
and then copy it back to the server...

Or am i missing something here?


Regards

Klaus Major
klaus at major-k.de
http://www.major-k.de