with the name server. When a SAS LIBNAME statement contains the domain name 'asia'
in combination with the appropriate name server, it will locate SPD Server tables in the
directory
/spds
on machine
asiacpu
. The SAS LIBNAME statement that invokes the
SPD Server engine and makes this association is
libname asialib sasspds 'asia' server=namecpu.spdsname;
Note that the value that follows the LIBNAME server specification is the same in all these
LIBNAME statements. The reason is that both SPD Servers use a common name service.
Asia departmental users do not need to know the name of the machine that provides storage
for their domain.
Which SAS Program Statement Runs Where?
Assume a user in the Asia department needs to create an SPD Server table on the
departmental server
asiacpu
. This task requires data to be extracted from an SPD Server
table named
alldata
. The user knows that the
alldata
table resides in the domain 'world.'
The user submits the following SAS code on a desktop SPD Server client:
libname worldlib sasspds 'world' server=namecpu.spdsname;
libname asialib sasspds 'asia' server=namecpu.spdsname;
data asialib.mydata;
set worldlib.alldata;
where region='Asia';
if country='Japan' then
subreg=1;
run;
The submitted code extracts records from an SPD Server table named
alldata
which resides
in the domain 'world.' The 'world' domain is stored on machine
worldcpu
in the
directory
/spds
. Because the
alldata
table resides on
worldcpu
, and SPD Server
processes certain SAS WHERE clauses, the search for the value 'Asia' is performed on
worldcpu
.
The SAS program runs on the Asia user's desktop machine. The desktop machine scans
each row in the
alldata
table, looking for the string 'Japan'. If the string is found, the desktop
client then forwards the row to the machine where the output table resides, which is
asiacpu
in this example.
Disk space for the output table
mydata
is allocated in the
/spds
directory on
asiacpu
.
The processing work, transferring data received from the user's desktop machine to the
SPD Server table, is performed by
asiacpu
as well.
The processing that was required to create the output SPD Server table was distributed
across three machines. However, the user's desktop machine requires no permanent disk
space, because SAS WHERE clauses execute on the machine that stores the source table.
Only the selected rows that matched the submitted WHERE clause are sent over the network
to the desktop client. This strategy significantly reduces network traffic, as well as the time
that is needed to complete a SAS program.
Which SAS Program Statement Runs Where?
69
Summary of Contents for Scalable Performance Data Server 4.5
Page 1: ...SAS Scalable Performance Data Server 4 5 Administrator s Guide...
Page 7: ...Part 1 Product Notes Chapter 1 SPD Server 4 5 Product Notes 3 1...
Page 8: ...2...
Page 12: ...6...
Page 63: ...Part 3 Migration Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility 59 57...
Page 64: ...58...
Page 70: ...64 Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility...
Page 72: ...66...
Page 76: ...70 Chapter 6 Using the SPD Server Name Server to Manage Resources...
Page 94: ...88 Chapter 7 Administering and Configuring SPD Server Using the SAS Management Console...
Page 98: ...92 Chapter 8 SPD Server SQL Query Rewrite Facility...
Page 116: ...110 Chapter 10 Configuring Disk Storage for SPD Server...
Page 128: ...122 Chapter 11 Setting Up SPD Server Parameter Files...
Page 154: ...148...
Page 198: ...192 Chapter 14 ACL Security Overview...
Page 212: ...206 Chapter 15 Managing SPD Server Passwords Users and Table ACLs...
Page 214: ...208...
Page 224: ...218 Chapter 16 SPD Server Operator Interface Procedure PROC SPDO...
Page 236: ...230 Chapter 18 SPD Server Table List Utility Spdsls...
Page 256: ...250 Chapter 19 SPD Server Backup and Restore Utilities...
Page 264: ...258 Chapter 20 SPD Server Directory Cleanup Utility...
Page 270: ......