Hello,

I need some help. My dad has data on dvd's that are 3-4 gigs each.

I checked on alpha 5 dbms and found out it can only handle up to 2
gigs at one time, is there a software program (any) that can handle
such a large volume of data like 5 gigs?

(we are getting an out of memory error when we try to run the 3-4
gig data dvd's in alpha 5)

Thank you!

In article <e0c5cee4.0312071017.4d39b618 (AT) posting (DOT) google.com>,
cactusjack222 <fowler22 (AT) bellsouth (DOT) net> writes

Take for example DOS - that used to be able to handle a maximum of
500Megs. SCO (spit!) can only handle 2 Gigs, along with a lot of older
unixes. Most modern OS's have no trouble with huge *disks*.

A lot of them, though, still need tweaking to handle *files* over 2Gb in
size.

My database of choice, UniVerse, will happily handle 2Gb per FILE (like
a SQL table), and loads of FILEs per db. And if 2Gb isn't enough, it's
easy to expand a FILE beyond this limit, even if it's a bit of hassle.

Cheers,
Wol
--
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
Witches are curious by definition and inquisitive by nature. She moved in. "Let
me through. I'm a nosey person.", she said, employing both elbows.
Maskerade : (c) 1995 Terry Pratchett

cactusjack222 schrieb:
I wouldn't store files that big in the database. Use the database to manage
the files and the related information (content, actors, whatever it is you
want to store together with the dvd's) but let the actual video streams be
managed by the file system of your OS.

Thomas

In an attempt to throw the authorities off his trail, "Anthony W. Youngman" <thewolery (AT) nospam (DOT) demon.co.uk> transmitted:
I wasn't aware that DOS ever had any such restrictions; I always
thought that depended on how many spindles of DASD you had hooked up.
The only problem with coping with 500MB would have been that your IBM
360 might not have had suitable channels to hook up that much disk.
But with 36 bits to play with, 500MB wouldn't make any sense as a
restriction. Unless IBM was specifically throttling the system so as
to not recognize >500MB. I don't recall hearing about that, though...

MS-DOS, a much more recent OS, had a restriction of 32MB, for quite
some time.

That sort of thing has been pretty common on Unix-like systems.
Filesystems have generally been able to cope with file sizes of
near-terabyte levels for quite some time now; the POSIX C APIs have
instead been the challenge.

At any rate, once you're looking at terabyte databases, the challenges
are likely to be in managing transactions rightly so as to be able to
pump the data in, and in building table schemas that allow efficient
retrieval of the data you want. The normally-simple things start
becoming hard because you have to think through the access methods
because they are immensely difficult to redo when there is so much
data.
--
output = ("cbbrowne" "@" "ntlug.org")
http://cbbrowne.com/info/languages.html
Jury -- Twelve people who determine which client has the better
lawyer.