SPD Server creates pathnames for table
data partition files and index files in this form:
table_name.file_extension.primary_path.n1.n2.spds9
It creates metadata
file pathnames and cluster table pathnames in this form:
table_name.file_extension.0.0.0.spds9
table_name
For a data file and
index file,
table-name is the
domain DATAPATH= or INDEXPATH= location where the table data file or index file is stored
and the table filename, unless the domain definition does not specify these options.
In that case,
table-name is
the domain PATHNAME= location and table filename.
For a metadata file
and cluster table,
table-name is the domain’s PATHNAME= location and the table filename. All metadata files are
stored in the
primary path of the domain. Information about any METAPATH= overflow files is stored in the metadata
file.
file-extension
specifies the
component file type, and for index files, also the index name. Valid extensions are .cdf, .dpf,
.idxindex-name, .
hbxindex-name, or .mdf.
primary-path
the PATHNAME= value for the domain.
n1
the component file number (if you have 20 .dpf files for a table, this will be 0-19).
n2
the update count for
the table. This field is not always used.
Here are examples of
component filenames that might be created for a table named Table1.
Metadata file:
UNIX and Windows:
table1.mdf.0.0.0.spds9
Data file:
UNIX:
table1.dpf._disk1_usertables.1.0.spds9
Windows:
table1.dpf.d__usertables.1.0.spds9
Index files:
UNIX:
table1.idxy._disk1_usertables.1.0.spds9
table1.hbxy._disk1_usertables.1.0.spds9
In this example,
the index name is Y.
Windows:
table1.idxy.d1__usertables.1.0.spds9
table1.hbxy.d__usertables.1.0.spds9
Note: The primary path portion
of Windows data and index filenames have a double underscore (_ _)
between the drive name and the directory name.
SPD Server provides a listing utility, spdsls, to enable you to list the component
files in
a domain.
For more information, see Domain List Utility.