10-16-2013 01:02 PM
Yes, side-by-side installations of different versions of SAS are supported on all operating systems.
With UNIX and z/OS, there's really no overlap as long as you use different installation locations.
For Windows, the most recent one installed is the one which will be associated with file extensions like .sas in the Windows registry. Only one version can be "registered" in this way at a time [makes sense since you probably wouldn't want to bring up both versions of SAS when double-clicking on a .sas file]. However, even though only one version can be registered for filetype associations, both versions are fully functional.
10-24-2013 09:33 AM
I read that too that for having side-by-side installations that all you need to do is use different installation locations but you need to specify different ports too (This how we did for RHEL). And if using the Grid, you'll need side-by-side of Platform Computing installed.
10-24-2013 10:05 AM
If you want to run two versions of the SAS Platform for Business Analytics side by side then you have to run the second instance using a different set of ports for the SAS Servers like: Metadata Server, OLAP Server, Object Spawner, etc.
On Windows you can only have one version of SAS active at a time due to the fact that the Windows Registry holds values for locations of the SAS executables and servers, etc.
10-24-2013 10:26 AM
The Windows registry is used for file type associations. You should be able to have 9.3 and 9.4 versions of SAS deployed and active on the same Windows machine. As mentioned earlier in the thread, if your deployment involves SAS servers (e.g., Metadata, Workspace, and Stored Process), you need to make sure the two sets of servers are talking on different TCP communication ports. If you're not aware of using ports, you're probably not using these SAS Servers as the need for ports is included in preinstall checklists associated with "planned" (i.e., Metadata Server-based) deployments. The port numbers are prompted for during execution of the SDW.
10-24-2013 11:52 AM
In Windows I have routinely had multiple versions of SAS running. The last time I tried to do this with SAS 9.2 and 9.3, the OQ script generated several errors after the 9.3 install. After going back and forth with SAS tech support, they remotely logged into my PC, uninstalled SAS 9.2, deleted some other .DLLs, and finally managed to get 9.3 running right. This took a lot of my time and made me wonder whether running two versions of SAS is really worth risking this kind of headache.
10-24-2013 12:07 PM
last time I tried to do this with SAS 9.2 and 9.3, the OQ script generated several errors after the 9.3 install. After going back and forth with SAS tech support, they remotely logged into my PC, uninstalled SAS 9.2, deleted some other .DLLs, and finally managed to get 9.3 running right. This took a lot of my time and made me wonder whether running two versions of SAS is really worth risking this kind of headache.
You are assuming that the problem with the 9.3 install had something to do with 9.2, and I don't think that is always the case. Could have been a lot of things.
Nevertheless, I have had two versions of SAS installed and running simultaneously, and never had "this kind of headache". I do this so I can test my production code in the new version, while continuing to run the code in the older version. I have done this with every upgrade and never had a problem of this type. SAS Institute, of course, has to write their code in such a way as to allow this type of situation with two versions of SAS installed and running.
10-24-2013 04:24 PM
My experience has been the same as PaigeMiller. I usually have multiple versions of SAS installed and can run them simultaneously without any issues. But I'm only running Foundation SAS.