Administrator Guide for SAS 9.1.3 Foundation for Microsoft Windows 73
Installing SAS 9.1.3
Installing SAS 9.1.3 on a server with Terminal Services is very similar to installing SAS on any
server. The key differences are managed by the install, including configuring SAS 9.1.3 for a
Terminal Services environment. There are several important steps to follow during the install:
1. When the Setup prompts for the Data Files Folder, be sure to accept the default value
provided by Setup. By accepting the default value for this dialog, Setup will be instructed
to use a variable path for the SASUSER location in the configuration file, ensuring a
separate SASUSER folder for each user of SAS.
2. When the Setup prompts for the Temporary Files Folder, be sure to accept the default
value provided by Setup. By accepting the default value for this dialog, Setup will be
instructed to use a variable path for the WORK location in the configuration file, ensuring a
separate WORK folder for each user of SAS.
Note : If SAS 9.1.3 will be installed on a server that has had SAS 9.1.3 installed before, the
SASUSER and WORK locations will default to the previously selected values stored in
the registry. These may not be the correct locations to ensure a separate SASUSER
and WORK folder. The sasv9.cfg file can be modified after the install to correct for
this. Refer to the section SAS System Support for Terminal Services on page 71 to
correct sasv
9.cfg.
Configuration and Performance Considerations
The following are additional steps to perform after installing SAS 9.1.3 on a server with
Terminal Services.
1. For optimal SAS 9.1.3 performance, it is recommended that the server have at least 32Mb
of memory available per concurrent user.
2. You can increase this amount based on the number of Terminal Server Client sessions
running SAS 9.1.3 and the amount of available memory on the server with Terminal
Services.
The WORK Directory
The WORK directory can be set to a common location because a work subdirectory is created
for each SAS session that is a unique name. The work directory can also have the
specifications ?CSIDL_PERSONAL or !USERPROFILE. This is an option if you wish to keep
track of which work directories belong to specific users.
This configuration is also useful if your users are spread across multiple drives and you have a
significant amount of hard drive space on each drive. The amount of drive spin is reduced,
which is a key factor in performance. If drive space is at a premium or if you have very fast
hard drives, then a common work directory may be to your advantage.
Your choice of strategy will depend on your computer hardware and your RAID settings. For
example, a RAID 0 drive is much faster than a comparable RAID 5 drive, but may not be as
fast as spreading the work directories across multiple drives. You should not place any
permanent data sets on a Raid 0 drive because these drives have no redundancy.
Memory
Since memory is important in performance, the system should have as much as possible.
Memory is much faster than your hard drive in manipulating temporary files and other
system operations. When computer memory is exhausted, the operating system is forced to
