home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.databases:6492 bit.listserv.dbase-l:893
- Newsgroups: comp.databases,bit.listserv.dbase-l
- Path: sparky!uunet!munnari.oz.au!metro!cs.uow.edu.au!cc.uow.edu.au!u9048979
- From: u9048979@cc.uow.edu.au (glen eastment)
- Subject: Re: Clipper: Backup/Restore routines for BIG files...
- Message-ID: <1992Sep2.024136.8943@cc.uow.edu.au>
- Organization: University Of Wollongong
- References: <1992Sep1.114959.11104@cs.tu-berlin.de>
- Date: Wed, 2 Sep 92 02:41:36 GMT
- Lines: 38
-
- schli@cs.tu-berlin.de (Wolfram Schlickenrieder) writes:
-
-
- > Hi there...
-
- > I'm stuck: I wanted to write a backup & restore routine for an
- > application I wrote before, but I have got a few data bases
- > which are HUGE (2-4MB) and therefore won't fit on a single
- > disc. Has anyone out there done that before from within a
- > Clipper application (without using "run backup ..." of
- > course)?
-
- > Any help is appreciated...
-
- > ...Wolfram
-
-
- If your data can be split up in some way, eg. a range in customer number,
- then you can split up sections of the database onto various disks.
-
- eg. disk 1 - cus no. 0000-1000
- disk 2 - cus no. 1000-2000....etc.
-
- This is really just about the only way I can think of splitting the database
- without using external commands (eg. 'run backup....').
-
- The problem with this is that you'd want there to be a relatively even
- distribution of data items - this is not always the case.
-
- Putting it together again, should be just about as easy as taking it apart.
-
- Hope this helps - if you think of a better solution, let me know, because
- I may have the same problem oneday myself :-) .
-
- Cheers!
-
- <GE> a.k.a. u9048979@wampyr.cc.uow.edu.au
-
-