spdsserv -acl
-acldir InstallDir/site
-nameserver samson
-libnamefile libnames.parm
The following is an example of a libnames.parm file entry for a UNIX system:
libname=all_users pathname=/disk1/peruser_tables;
The following is an example of a libnames.parm file entry for Windows:
libname=all_users pathname=d:\peruser_tables;
When SPD Server users create new tables in a LIBNAME domain, there is a hidden system
detail to consider. The metadata component (.mdf) must start in the primary file system.
This detail is very important. If all of the available space in the primary file system is
consumed, SPD Server cannot create new tables until disk space becomes available.
Example 1 stores all the component files: metadata, data and index data in the primary file
system. This can present a problem if you use large tables. Large tables can quickly fill up
the primary file system.
We recommend storing the data and index components separately from the primary file
system. Example 2 shows how to do this using ROPTIONS= with your LIBNAME
statement in your libnames.parm file.
Example 2: Using ROPTIONS= to Store SPD Server Table Data and
Index Component Files in Other File Systems
The following SPD Server code invokes the libnames.parm file:
spdsserv -acl
-acldir InstallDir/site
-nameserver samson
-libnamefile libnames.parm
Sample libnames.parm for a UNIX System
libname=all_users pathname=/disk1/peruser_tables
roptions="datapath=('/disk2/userdata' '/disk3/userdata'
'/disk12/userdata' '/disk13/userdata')
indexpath=('/disk4/userindexes' '/disk5/userindexes'
'/disk14/userindexes' '/disk15/userindexes')";
Sample libnames.parm for a Windows System
libname=all_users pathname=d:\peruser_tables
roptions="datapath=('e:\userdata' 'f:\userdata')
indexpath=('g:\userindexes' 'h:\userindexes')";
In Example 2, the PATHNAME= directory stores metadata files for SPD Server tables in
the 'all_users' LIBNAME domain. The initial and overflow stores for the data and index
files are directed to other file systems. In Example 2, users who create large tables will not
quickly exhaust the primary file system. The reason: the primary file system is reserved
for only very small metadata files. The larger data and index files will be stored in the other
file systems specified with the DATAPATH= and INDEXPATH= options in the
LIBNAME parameter file.
Example 2: Using ROPTIONS= to Store SPD Server Table Data and Index Component
Files in Other File Systems 107
