Migration

SAS Intelligence Platform and Business Intelligence

This topic lists the available compatibility and migration documentation for metadata-based deployments. These deployments can contain SAS Business Intelligence, Data Integration, or Solutions with metadata that is stored by a SAS Metadata Server.

SAS® 9.3

See SAS 9.3 Intelligence Platform: Migration Guide for migrating to SAS 9.3 from SAS 9.2 or from SAS 9.1.3.
Additional issues are mentioned in SAS 9.3 Guide to Software Updates.

SAS® 9.2

See SAS Intelligence Platform: 9.1.3 to 9.2 Migration Guide.
Additional issues are mentioned in Special Considerations for Customers Upgrading to SAS® 9.2.
If you are migrating to a maintenance release of SAS 9.2, see also Maintenance Release Announcement for SAS 9.2.
The SAS 9.2 Metadata Model has several new and deprecated metadata types. This change affects custom metadata programs only. For more information, see "What's New" topics in Open Metadata Interface: Reference and Usage and in SAS 9.2 Metadata Model: Reference.

SAS® 9.1.3

See Upgrading SAS BI Applications. See also Appendix 3, "Upgrading a SAS 9.1 or 9.1.2 System to a SAS 9.1.3 System" in SAS Intelligence Platform: Administration Guide.

Converting SAS Programs to Leverage SAS BI Architecture

Peaceful Coexistence: SAS 9.2 and SAS 9.1.3 for Metadata-Based Products

Some sites perform a phased migration to SAS 9.2. In other words, you install SAS 9.2 on the same computer with SAS 9.1.3 and move your applications gradually rather than all at once. Here are some issues that are specific to metadata-based SAS Business Intelligence, Data Integration, and Solutions:

On Windows, if you plan to run both a SAS 9.1 and a SAS 9.2 Connect spawner on the same computer, then apply hot fix E9BC13 for Base SAS to the SAS 9.1.3 environment before you install SAS 9.2.
On Windows, due to the use of the Windows registry and services, you are advised to not run SAS 9.1.3 and SAS 9.2 metadata-based SAS Business Intelligence, Data Integration, and Solutions concurrently (at the same time) on the same Windows computer. You can avoid problems by using scripts to switch between the two instances.
SAS 9.1.3 uses the Java_Home environment variable. SAS 9.2 installs the new Java JRE (jre1.5.0_12) under C:\Program Files\Java. See a tip in the peaceful coexistence topic about a script that sets the environment variables when SAS is invoked.
Third-party products might have different requirements for the two deployments. Web application servers, JDKs, and JREs are at different versions for SAS 9.2 than for SAS 9.1.3. If you experience problems running two versions on one computer, you might have to request support from the vendor.
Platform Suite for SAS can be shared by SAS 9.2 and SAS 9.1.3. Be careful not to collide on the naming of scheduled flows. This is usually avoided by using a different user ID for the two versions of SAS.
SAS 9.1.3 clients cannot connect to a SAS 9.2 Metadata Server. SAS 9.2 clients cannot connect to a SAS 9.1.3 Metadata Server. Similarly, if you apply maintenance in a multi-tier environment, you must apply that maintenance to all tiers.
You can install multiple versions of SAS Management Console and BI clients, although some clients cannot run concurrently. Check the peaceful coexistence topic for more general advice (for example, separate ports and JDKs, updates to syntax) and specific known issues for components of your BI deployment.
Web-based applications (for example, SAS Web OLAP Viewer for Java, SAS Information Delivery Portal) support multiple versions. Use a unique URL for each version. For example:

SAS 9.1.3: http://myserver-1.com:8080/SASPortal
SAS 9.2: http://myserver-2.com:8080/SASPortal
or

SAS 9.1.3: http://myserver.com:8080/SASPortal
SAS 9.2: http://myserver.com:8001/SASPortal

E-mail This Page

FOCUS AREAS

Resources for Intelligence Platform Migration

Quick Links