Why use a multivolume database?
Reading the Progress documentation doesn’t go into much detail into why you would use a multivolume database, other then to say that it lets you make databases bigger than the allowed file system size (often 2GB nowadays). There are several other reasons to use this method to split your database up. Even if your database isnt over 2GB, you might want to put in on multiple disks anyway just to even out the accesses to it and improve performance. You can split your database in up to 99 pieces under V6, up to 256 pieces with V7. If you’re running UNIX, you’ll probably have to up the number of files that a single process can open, as discussed in the UNIX kernel section, if you start splitting the database into many pieces; otherwise, the server process wont be able to open the database. If you really want to get fancy, you can pick the locations of the extents in fancy ways so that disk contention is minimized further (for example, instead of putting extents 1-25 on disk 1 and 26-50 on di
