For most object types,
the export and import wizards (and the batch export and import tools)
promote both the physical content and the metadata. When you use the
batch tools, the promotion automatically includes all associated physical
content except tables and external files. When you use the wizards,
you can choose whether to include or exclude some of the content types
by using the
Options tab.
The following table
lists the types of physical content that are exported and imported
with metadata objects.
Promotion of Physical Content with Metadata Objects
|
Associated Physical
Content
|
|
|
Packages published to
the channel's archive or WebDAV location
|
Associated physical
content is always promoted with batch tools and is optionally promoted
with wizards.
|
|
Cube header files, MOLAP
aggregation tables, drill-through tables, and ROLAP aggregation tables
|
Associated physical
content is not promoted. For details, see the SAS OLAP Server: User's Guide.
|
|
|
Associated physical
content is not promoted with batch tools and is optionally promoted
with wizards.
|
External format file
(EFF)
|
Associated physical
content is not promoted with batch tools and is optionally promoted
with wizards.
|
|
Custom code, preprocesses,
and postprocesses
|
Associated physical
content is always promoted.
|
|
XML files and XML maps
that are contained in the library
|
Associated physical
content is always promoted with batch tools and is optionally promoted
with wizards.
|
|
Physical files that
are associated with File or directory prompts
|
|
|
XML (.srx) file that
defines the report
|
Associated physical
content is always promoted. The target is the path on the SAS Content
Server that is mapped to the target metadata folder via content mapping.
|
|
|
Associated physical
content is optionally promoted with the wizards and is always promoted
with the batch tools. The target is the source code repository that
you designate in the wizard dialog box. If the repository definition
does not exist on the target system, the import wizard enables you
to add it.
When you use the batch
import tool, you can use the substitution file to designate the source
code repository and to specify that the repository definition is to
be created if it does not exist.
|
|
|
Associated physical
content is not promoted with the batch tools and is optionally promoted
with the wizards.
Use this option with
small data sets only. Since data sets are packaged in the .SPK file,
large data sets could require lengthy processing times.
|