The Migration focus area at support.sas.com/rnd/migration provides detailed
information about SAS migration and
cross-release compatibility.
The idea is to document every known issue together with their fixes and
best practices. This gives the customer a sense of
confidence that possible obstacles have been anticipated and
resolved ahead of time. With proper planning, the site's resources can be maximized,
the migration can proceed more smoothly,
and the customer can start using the enhanced power of a new SAS release.
Because SAS installations can vary so widely, it is not possible for SAS
to provide
a one-size-fits-all migration timeline. Instead, this document is
a framework for your research and planning.
The first two steps help you to collect basic information about your site.
Then you use our interactive calculators to learn whether you need
the MIGRATE procedure and how to use it. The remaining steps alert you to
possible issues that can affect your migration timeline.
A number of SAS employees in the field helped to gather information
from customer sites, so this document includes
a variety of possible issues. You should be able
to cross off many of them as not applicable.
Step 1: Inventory the Hardware
This step gathers information about your current operating environment and target operating environment. Note any necessary upgrades as tasks in your migration plan.
You will also need this information in step 3.
Is the operating environment supported in your target SAS release? Are you changing to a different oeprating environment? Are you changing from 32-bit SAS to 64-bit SAS?
(support.sas.com/documentation/installcenter/)
Files that were created under different SAS versions could be stored together.
Are all library members from the same release? All libraries from the same release?
If you want to use cross-environment compatibility rather than migrating libraries to the newer release, determine what kind of processing you need - input (read), update (modify), output (create).
If you want to use cross-environment compatibility, do you need access to
SAS catalogs, indexes, integrity constraints, DATA step views, SAS/ACCESS views that are not for SAS/ACCESS for Oracle or SAP, stored compiled DATA step programs, item stores, DMDB files, FDB files, or any SAS file that was created prior to SAS 7?
The MOVE option is not recommended with PROC MIGRATE.
Do you have enough disk space to validate the
migration in the target library before you delete the source library?
(support.sas.com/rnd/migration/procmigrate/validtools.html)
The migration instructions will tell you whether you need to use
RLS, a feature of SAS/SHARE and SAS/CONNECT software. If you don't have access
to SAS/SHARE or SAS/CONNECT software, contact the Customer Interaction Center
(phone 1-800-727-0025 or send e-mail to CICenter@sas.com).
Review your decisions and your timeline.
This is advisable because many planning decisions are interdependent;
that is, one decision can affect multiple areas of planning.