FOCUS AREAS

Hot Topics

Updates for SAS 9.2 (March 2008)
See the compatibility calculator to determine whether you need to migrate your libraries to SAS 9.2. Use the PROC MIGRATE calculator to find the right example code for your migration.
Get a Smarter COMPARE
Validation tools for the MIGRATE procedure now work with CEDA and provide additional details about catalogs, indexes, and integrity constraints.
Start Planning
See Getting Started for the most efficient pathway through all of the SAS®9 migration documentation.
Coexistence
Many SAS®9 products can install side-by-side with SAS 8.2 with very good compatibility. See Peaceful Coexistence: SAS®9 and SAS 8.2 for details.
Sample Validation SOP
See an example SOP: SAS Installation Qualification / Operational Qualification (PDF) for the pharmaceutical industry.

Migration

Execution: Create Backups and Benchmarks

Step 1: Create an Active or Restorable Backup Image

Keep a backup copy of the source installation until you confirm that the target SAS installation works correctly and produces the same results as the source installation. A backup image is handy for reference and is essential for disaster recovery.

Backing Up SASROOT

Use standard utilities, such as tar or cpio under UNIX, to back up all the files in the SASROOT directory and subdirectories. Be sure to include the hidden directories (for example, .install). For data integrity reasons, make sure all SAS sessions are terminated before you begin the backup. Consult your system administrator or operating environment vendor for more information.

Best practices

In the backup, include the SAS source code for creating the following:

SQL views
DATA step views
ODS templates
stored, compiled macros
stored, compiled DATA steps.

This provides an additional level of backup and also can be used to address any concerns about validity or integrity of the target installation.

Document the architecture of any custom SAS application and its environment. In an organization with strong coding practices, such a document is likely to already exist. This can be particularly helpful when the custom application includes third-party software, or, for example, when a large team undertakes the site migration and each individual must understand his or her responsibility.

Document system requirements for the source installation. Include detailed reference information about autoexec files, autocall macro libraries, configuration files, and system options. These attributes' impact on behavior is often underestimated. Because defaults and system options might be different in the target installation, you must understand the underlying reasons for settings and customizations.

Proceed to step 2.