FOCUS AREAS
Hot Topics
- Migration for Metadata-Based Deployments (February 2009)
The SAS Migration Utility analyzes and prepares your SAS 9.1.3 deployment for migration. See SAS Intelligence Platform: 9.1.3 to 9.2 Migration Guide for a complete guide to planning and execution.
- The SAS 9.2 Value Proposition
- Coexistence
Read about running multiple versions of SAS on one computer. - Sample Validation SOP
See an example SOP: SAS Installation Qualification / Operational Qualification (PDF) (updated 19 May 2008) for the pharmaceutical industry.
- Calculators
- SAS Notes
Related Links
Inventory of SAS Files for PROC MIGRATE
|
Migration
Inventory of SAS Files for PROC MIGRATE: Details
This page contains details about the different kinds of files you can migrate to the target installation. The previous page, Taking Inventory of Files, briefly outlines the files that can be migrated with PROC MIGRATE and those that cannot. (Strictly speaking, when you use PROC MIGRATE, you migrate a SAS data library and not individual library members; see the PROC MIGRATE documentation.)
- data file
- is a type of SAS data set that contains both descriptor information about
the data and the data values themselves.
When you use PROC MIGRATE to
migrate a data file, you are also migrating the following:
alternate collating sequence, audit trails, compression, created and modified datetimes,
deleted observations, encryption, generations, indexes, integrity constraints, and passwords.
- data view
- is a type of SAS data set that retrieves data values from other files.
A data view contains only descriptor information and is dynamic where a
data file is static. See the SAS online documentation for more
distinctions between data views and data files.
PROC MIGRATE does not change any of the internal librefs used by a view.
- PROC SQL view
- is covered by PROC MIGRATE with no known exceptions.
- DATA step view
- is covered by PROC MIGRATE if it is from SAS Version 8 and later,
and only if the source was saved in the view.
Otherwise, it must be recreated from source.
- SAS/ACCESS view (also called view descriptor)
- is covered by PROC MIGRATE if the view descriptor was
written with the Oracle, Sybase, or DB2 access engine. PROC MIGRATE automatically uses the CV2VIEW procedure,
which converts SAS/ACCESS views into SQL views. Migrating SAS/ACCESS views to a different operating environment
is not supported. For more information about the conversion, see
Overview
of the CV2VIEW Procedure in SAS/ACCESS for Relational Databases: Reference.
- SAS catalog
- is covered by PROC MIGRATE with the same capabilities and limitations
as PROC CPORT and PROC CIMPORT, which are automatically called by PROC MIGRATE.
Catalogs cannot be migrated from a sequential library.
See a special topic
for details about catalogs from specific operating environments.
The User Profile catalog is a special case. It contains function key definitions, window attributes, and other information for interactive windowing tasks. If an individual hasn't made many customizations, they might not care to migrate their user profile catalog. It is possible for an individual to have a user profile catalog other than the default, in a different place or under a different name.
- MDDB file
- is covered by PROC MIGRATE if it is not a
Version 7 MDDB. See
additional information
about using MDDBs in SAS 9.
- DMDB file
- is covered by PROC MIGRATE with no known exceptions.
- item store
- is covered by PROC MIGRATE with the following exceptions:
- when migrating from 32-bit to 64-bit operating environment (This does not result in an error to the SAS log, but item stores might not work correctly in the target.)
- when item stores are in a sequential library
- when either the target or source library is assigned through a remote server
- ODS template
- is an ODS table, style, or tagset template, or an ODS documents
registry. Use PROC MIGRATE under the item store restrictions that are noted above.
If your user-defined or user-modified templates aren't covered by PROC MIGRATE, see a special topic about migrating ODS templates.
- SAS registry file
- contains information about SAS session
applications. These are covered by PROC MIGRATE under the item store restrictions
that are noted above. However, you should not
migrate the SAS registry. Instead, see where it is mentioned under
Customizing SAS Configuration Settings.
- stored compiled DATA step program
- is not covered by PROC MIGRATE. Instead, move
the source code to the target where you can compile it and store it. (See
the online documentation, "Stored Compiled DATA Step Programs.")
- stored compiled macro
- is not covered by PROC MIGRATE. Instead, move the macro
source code to the target, where you can compile and store it. (See SAS
Macro Language: Reference.)
- SPD engine (Scalable Performance Data engine) data set
- is not covered by PROC MIGRATE. Use PROC CPORT and PROC CIMPORT. See also the topic about
SPD engine.
- external file
- is any file that is not stored in a SAS library. That is, it's
maintained by your operating environment and not by SAS. A file that is not a member of a
SAS library is not covered by PROC MIGRATE.
- SAS program
- is a combination of DATA steps, PROCs, and so forth.
The file extension should be .SAS. These are not covered by PROC MIGRATE.
Probably no changes will be necessary in order to use your
programs in the new installation, but see Updating Base SAS
Code for issues.
- SAS autoexec file
- contains SAS
statements that execute immediately after SAS initializes.
The file extension should be .SAS. Multiple files are possible,
and individuals can have SAS autoexec files other than
the default, in a different place or under a different name. A SAS
autoexec file is not required to run SAS, so it may be absent.
Individuals should examine the autoexec file's code carefully before copying the file to the target, because behavior might have changed in the new release.
- output
- from a SAS procedure, includes regular list output (.LST)
and ODS output. If you use the ODS MARKUP destination, there
is no limit to the different kinds of output files you can generate.
These are not covered by PROC MIGRATE.
- transport file
- is output from
- XPORT engine with PROC COPY
- PROC CPORT
- SAS configuration file
- is not covered by PROC MIGRATE and should not be copied to the target; see
Customizing SAS Configuration Settings
for a safe way to duplicate your settings after
installation. It is possible for individuals to have configuration files other
than the default, in a different place or under a different name.
- SASHELP, SASUSER, and WORK libraries
- Although the members of the libraries might be supported by PROC MIGRATE, you are advised not to migrate them. See SAS Language Reference: Concepts for details about these libraries. The WORK library contains temporary files. SASHELP and SASUSER store information and personal settings that might not be best for the new release of SAS.
