FOCUS AREAS

Hot Topics

Related Links

Hardware

Migration

Taking Inventory of Hardware

To help you identify the locations where you will install the newer release of SAS, here is a list of typical SAS usage scenarios. You can also use this list as a starting place to discuss whether any new hardware is on order or must be purchased. If you plan to add or upgrade hardware, be sure to account for those tasks in your migration schedule.

    desktop or laptop machine
    server machine running SAS
    remote client has login access via a terminal emulator
    client is running Enterprise Guide for the front-end
    client is running a Web-based application for the front-end
    multitier or n-tier server environment via SAS/CONNECT or IOM or some other protocol

In a multi-tiered environment, part of the application runs on a desktop or laptop, and other parts run on one or more servers. In many cases, a front-end user interface runs on the desktop, the SAS compute server runs on a small server in the middle, and the data sits in a relational database management system (RDBMS) on a larger server in the back-end.

Additional Considerations

On top of the issues listed on the previous page, Hardware, you might need to plan for the following.

Client-Server and n-Tier Architecture

Take care to learn what SAS release the client and server tier are running, and also what release the files were created under. It is possible, for example, that a SAS/SHARE server is at a different release than a remote client machine, and, in addition, for a file to have been created under a different release than the current SAS session. You must consider both client-server compatibility and SAS file processing compatibility.

See the topic SAS/SHARE and SAS/CONNECT Software for a summary of inter-release compatibility via RLS, DTS, and Compute Services. See the SAS documentation for full details.

Extra Resources for Migration

Some sites run source and target in parallel while validating the target installation. This requires additional disk space and CPU time. See Running Source and Target in Parallel.

See also the installation setup step in the Best Practices Migration with PROC MIGRATE, where you are advised to set up the target SAS installation in an isolated environment from the source installation.