Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!apple!bionet!agate!pasteur!ucbvax!hplabs!pyramid!infmx!aland
From: aland@infmx.UUCP (Dr. Scump)
Newsgroups: comp.databases
Subject: Re: large informix databases
Summary: can distribute tables among file systems
Keywords: informix, unix, large database
Message-ID: <493@infmx.UUCP>
Date: 6 Oct 88 02:42:46 GMT
References: <4477@pdn.UUCP>
Organization: Informix Software Inc., Menlo Park, CA.
Lines: 40

In article <4477@pdn.UUCP>, yerneni@pdn.UUCP (Prasad Yerneni) writes:
> 
> Hello,
> I would like to know if anyone has tackled the problem of an Informix2.3 
> database, on a SYSV machine, growing beyond the volume size of the partition 
> that it is resident on.
> 
> The informix manuals don't tell me what happens in such a case, and since 
> Unix does not allow a file to be split between volumes is there any ingenious 
> method that someone has tried to overcome this problem? 

By using the IN <pathname> clause of the CREATE TABLE statement, you
can create any given table in another directory (which may reside on
another file system).  For example:

   create table foo (bar char(500)) in "/usr/othrdisk/foo";
   create table pingpong (doric char(500)) in "/usr2/wherever/pingpong";

The resulting file names for table foo are: 
     /usr/othrdisk/foo.dat
     /usr/othrdisk/foo.idx
     /usr/othrdisk/foo.lok    (if not a system call locking port)

The resulting file names for table pingpong are: 
     /usr2/wherever/pingpong.dat
     /usr2/wherever/pingpong.idx
     /usr2/wherever/pingpong.lok   (if not a system call locking port)

In the Turbo backend, tables can span chunks, so no special placement
commands are necessary.

> 
> Prasad.


-- 
 Alan S. Denney  |  Informix Software, Inc.  |  {pyramid|uunet}!infmx!aland
 Disclaimer: These opinions are mine alone.  If I am caught or killed,
             the secretary will disavow any knowledge of my actions.
 Santos' 4th Law: "Anything worth fighting for is worth fighting *dirty* for"