Peaceful Coexistence: Multiple SAS® Releases
It is possible to run multiple SAS®9 releases simultaneously on the same computer.
It is also possible to run SAS 9 on the same computer as SAS 8.2.
This topic lists all known issues, to help you avoid any conflicts.
Known Issues for Coexistence
- Data sets and other SAS files:
SAS strives wherever possible to support cross-release compatibility.
- Use the interactive Compatibility Calculator
to determine whether you can run your existing SAS files in a newer release without migrating
them to the new format (support.sas.com/rnd/migration/planning/files/calculator/).
- If needed, you can
regress a file to a previous version
- A few optional
SAS file features
make files incompatible with earlier releases (support.sas.com/rnd/migration/planning/files/forward.html).
- It is recommended to not store files from multiple releases in the same library.
The file extension remains the same as it has been since SAS 8.2.
Therefore you could accidentally overwrite an existing file with the same name that was created
under another release. Read about this and other details involved in
maintaining files from different releases
- If you make a copy of a data set to test the new release of SAS and
the data set is live (that is, continually updated), then you must either update
the two data sets concurrently or designate one data set to be frozen and later discarded.
- Syntax (PROCs, DATA steps, macros, and so forth):
You can use SAS or SCL code across multiple releases. However, behavior can change in later releases,
and new syntax is introduced that is not supported in earlier releases.
Research the known issues for
Base SAS and other SAS software
- Installation and configuration:
- If you are installing two or more releases, install the previous release first. Otherwise, you might run into problems
with the shared files directory.
- Install multiple releases in separate locations on the machine.
- Make sure the multiple releases use different TCP/IP port numbers.
- It is recommended that you use the SAS configuration file (sasv8.cfg or sasv9.cfg)
to separate the locations of SASWORK.
- You can add new orders within one release to a single SAS Software Depot, but do not
mix multiple releases in one Software Depot. For example, do not add a SAS 9.3 order to a
SAS 9.2 Software Depot.
- If you are migrating a metadata-based deployment to a new release,
use the same installer account and administrative accounts for both deployments to avoid permission issues.
- Operating environment:
- Some operating environments are no longer supported in later releases.
- Updates made to an operating environment for SAS
might conflict with earlier releases, although this has not been reported
- Running two versions of SAS on a machine might require additional disk space or CPU time.
- Invoking SAS:
SAS has developed coexistence guidelines for
Any new information will be made available from this page.
If you encounter problems in your deployment, please
contact SAS Technical Support
(support.sas.com/ctx/supportform/index.jsp) for assistance.