Databases Reference
In-Depth Information
transformation specifies how to extract data, transform data, or load data into data
stores. Each transformation generates or retrieves SAS code. In most cases, you will
want SAS Data Integration Studio to generate code for transformations and jobs, but
you can specify user-written code for any transformation in a job, or for the entire job.
How Jobs Are Executed
In SAS Data Integration Studio, you can execute a job in the following ways:
use the
Submit Job
option to submit the job for interactive execution
use the
Deploy for Scheduling
option to generate code for the job and save it to
a file; the job can be executed later in batch mode
use the
Stored Process
option to generate a stored process for the job and save it
to a file; the job can be executed later in batch mode by a stored process server
Identifying the Server That Executes a Job
In SAS Open Metadata Architecture applications such as SAS Data Integration
Studio, a SAS Application Server is a metadata object that can provide access to several
servers, libraries, schemas, directories, and other resources. An administrator typically
defines this object and then tells the SAS Data Integration Studio user which object to
select as the default.
Behind the scenes, when you submit a SAS Data Integration Studio job for execution,
it is submitted to a SAS Workspace Server component of the relevant SAS Application
Server. The relevant SAS Application Server is one of the following:
the default server that is specified on the
SAS Server
tab in the Options window
in SAS Data Integration Studio
the SAS Application Server to which a job is deployed with the
Deploy for
Scheduling
option
It is important for administrators to know which SAS Workspace Server or servers will
execute a job in order to do the following tasks:
store data where it can be accessed efficiently by the transformations in a SAS
Data Integration Studio job, as described in “Supporting Multi-Tier (N-Tier)
Environments” on page 64
locate the SAS Work library where the job's intermediate files are stored by default
specify SAS options that you want to apply to all jobs that are executed on a given
server, as described in “Setting SAS Options for Jobs and Transformations” on
page 189
To identify the SAS Workspace Server or servers that will execute a SAS Data
Integration Studio job, administrators can use SAS Management Console to examine
the metadata for the relevant SAS Application Server.
Intermediate Files for Jobs
Transformations in a SAS Data Integration Studio job can produce three kinds of
intermediate files:
procedure utility files that are created by the SORT and SUMMARY procedures, if
these procedures are used in the transformation
transformation temporary files that are created by the transformation as it is
working
Search WWH ::
Custom Search