SAS 9.4 Data Administration Guide Intelligence Platform User Guide

Special Considerations for Information Map Tables

Information Map

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . .

Establishing Connectivity to an ODBC Database

Using Microsoft Windows NT Authentication

. . . . . . . . . . . . . . . . . . . . . . .

Overview of Establishing Connectivity to an

ODBC Database Using Microsoft Windows NT

Authentication

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Prerequisites

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 1: Configure an ODBC Data Source Using

Microsoft Windows NT Authentication

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 2: Create a Library By Submitting a

LIBNAME Statement with the ODBC Engine

. . . . . . . . . . . . . . . . . . . . .

Stage 3: Register a User

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 4: Register the ODBC Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 5: Register the ODBC Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Establishing Connectivity to an OLE DB

Database Using Microsoft Windows NT Authentication

. . . . . . . .

100

Overview of Establishing Connectivity to an OLE

DB Database Using Microsoft Windows NT Authentication

. . .

Stage 1: Register the OLE DB Server

Prerequisites

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

101

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

102

Stage 2: Register the OLE DB Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

105

Stage 3: Verify That the SQL Server Tables Are

Listed in the SAS Explorer

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

107

Contents

Stage 4: Register the SQL Server Tables

. . . . . . . . . . . . . . . . . . . . . . . . .

107

Establishing Connectivity to a Teradata Database

. . . . . . . . . . . . . . .

108

Overview of Establishing Connectivity to a Teradata Server

. . . .

Stage 1: Register the Teradata Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

109

Stage 2: Register the Teradata Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111

Establishing Connectivity to an Oracle Database

. . . . . . . . . . . . . . . .

114

Overview of Establishing Connectivity to an Oracle Database

. .

114

Prerequisites

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

114

Stage 1: Register the Oracle Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 2: Register the Oracle Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of Establishing Connectivity to a

Establishing Connectivity to a Microsoft Access

Database By Using ODBC

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

119

Microsoft Access Database By Using ODBC

. . . . . . . . . . . . . . . . . . .

Stage 1: Define the ODBC Data Source

. . . . . . . . . . . . . . . . . . . . . . . . . . .

120

Stage 2: Register the ODBC Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 3: Register the ODBC Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Establishing Connectivity to a SAS Federation Server

. . . . . . . . .

124

Stage 1: Register the SAS Federation Server

Federation Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

124

. . . . . . . . . . . . . . . . . . . .

125

Stage 2: Register the SAS Federation Server Library

. . . . . . . . . . .

Special Considerations for SAS Federation Server Libraries

. . .

128

Establishing Connectivity to a SAS Scalable

Performance Data Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

129

Scalable Performance Data Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

129

Stage 1: Configure the libnames.parm File

. . . . . . . . . . . . . . . . . . . . . . . .

Stage 2: Register the SAS Scalable

Performance Data Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 3: Register the SAS Scalable

Performance Data Server Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

132

Chapter 4 / Connecting to Common Data Sources

Establishing Connectivity to an SAP Server

. . . . . . . . . . . . . . . . . . . . . .

134

Overview to Establishing Connectivity to an SAP Server

. . . . . . .

134

Stage 1: Register the SAP Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

135

Stage 2: Register the SAP Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

137

Stage 3: Extract SAP Metadata

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Special Considerations for SAP

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview to Establishing Connectivity to an SAP

Establishing Connectivity to an SAP HANA Server

. . . . . . . . . . . . . .

139

HANA Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 1: Register the SAP HANA Server

. . . . . . . . . . . . . . . . . . . . . . . . . .

141

Stage 2: Register the SAP HANA Library

. . . . . . . . . . . . . . . . . . . . . . . . .

143

Establishing Connectivity to an Impala Server

. . . . . . . . . . . . . . . . . . .

144

Overview of Establishing Connectivity to Impala

. . . . . . . . . . . . . . . . .

144

Stage 1: Register the Impala Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

145

Stage 2: Register the Impala Library

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

147

Establishing Connectivity to Hadoop

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

148

Overview of Establishing Connectivity to Hadoop

. . . . . . . . . . . . . . . .

148

Hadoop Configuration Resources

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 1: Register the Hadoop Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 2: Register the Hadoop via Hive Library

. . . . . . . . . . . . . . . . . . .

Special Considerations for Hadoop via Hive Tables

. . . . . . . . . . . . .

Establishing Connectivity to a SAS LASR Analytic Server

. . . . .

157

LASR Analytic Server

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 1: Register a SAS LASR Analytic Server

Using SAS Management Console

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

159

Stage 2: Register a SAS LASR Analytic Server

Library Using SAS Management Console

. . . . . . . . . . . . . . . . . . . . . . .

160

Stage 1: Register a SAS LASR Analytic Server

Using SAS Environment Manager

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

162

Stage 2: Register a SAS LASR Analytic Server

Library Using SAS Environment Manager

. . . . . . . . . . . . . . . . . . . . . . .

165

Special Considerations for SAS LASR Analytic Server

. . . . . . . . . .

Overview of Establishing Connectivity to a SASHDAT Library

Overview of Connecting to Common Data Sources

Establishing Connectivity to a SASHDAT Library

. . . . . . . . . . . . . . . .

167

. .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

168

Registering and Verifying Tables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

171

Overview to Registering Tables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Stage 1: Register the Tables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

172

Stage 2: Verify Access to the Data in a SAS Application

. . . . . . . .

common data sources introduced in Chapter 1, “Overview of Common Data Sources,” on page 1

Read-only Access for Reporting Libraries

. . . . . . . . . . . . . . . . . . . . . . . . .

173

Setting UNIX Environment Variables for SAS/ACCESS

. . . . . . . . .

174

Troubleshooting SAS/ACCESS Connections to

Relational Databases

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

175

Overview of Connecting to Common

Data Sources

This chapter consists of detailed examples for establishing a connection to each of the

. Some of the connection processes covered in this chapter have common elements that might be applied to similar data sources. For example, the description of the process of using SAS/ACCESS to connect to an Oracle database might be useful when you connect to other relational databases such as DB2, Sybase, and Informix.

Also, the description of ODBC connections to a Microsoft Access database and the account of the connection to an SAP source can be helpful when you connect to similar data sources.

In order to perform the procedures for registering libraries, you must have

ReadMetadata and WriteMetadata permission for the repository and the SAS

Application Servers that the data library is assigned to. You must also have

WriteMemberMetadata permission for the folder into which the library and its tables are registered.

Chapter 4 / Connecting to Common Data Sources

This chapter also explains the process that registers tables as metadata from the data sources. Registering a table in metadata enables you to view the data in a SAS

application. For more information about managing table metadata, see Chapter 2,

“Managing Table Metadata,” on page 23

Overview of SAS/ACCESS Connections to Relational Databases

Process Overview

This section provides generic instructions for using SAS Management Console to configure access to a database. SAS/ACCESS must be licensed and configured before using SAS Management Console to register the library that holds the tables. The generic task has three stages:

Define the DBMS user or user group.

Define the DBMS User

User definitions can be set up using SAS Management Console or SAS Environment

Manager.

The User Manager is a SAS Management Console plug-in that provides functions to manage metadata definitions for users and user groups. Each user and user group that accesses secure resources on a SAS Metadata Server must be represented by an identity on the server. Individual users are represented by Person objects, and groups are represented by Identity Group objects.

To define a user using SAS Management Console, perform the following steps:

Start SAS Management Console using your administrator account.

Overview of SAS/ACCESS Connections to Relational Databases

2 From SAS Management Console navigation tree, right-click the User Manager icon.

Then select New  User , which displays the New User Properties dialog box.

On the General tab, enter your name in the Name field. Note that you can enter any user name that you want to use (for example, a single name, your full name, and so on). Display Name, Job Title, and Description are optional.

Click the Accounts tab and click New to display the New Login Properties dialog box.

Enter your Windows domain and user ID (WindowsDomain\user) and the password.

Select DefaultAuth as the authentication domain.

Click OK to add the login to the user.

Click OK to close the New User Properties dialog box.

Click User Manager to verify that the name appears in the user name list.

The SAS Environment Manager Users module supports some of the user administration tasks that are provided by the User Manager plug-in to SAS

Management Console, including the following: n creation and maintenance of users, groups, and roles n management of group and role memberships n management of logins and internal accounts

For more information about the SAS Environment Manager Users module, see

“Managing User Access” in SAS Environment Manager Administration: User's Guide.

Define the DBMS User Group

User group definitions can be set up using SAS Management Console or SAS

Environment Manager.

To define a user group using SAS Management Console, perform the following steps:

Chapter 4 / Connecting to Common Data Sources

1 Start SAS Management Console using your administrator account.

2 From SAS Management Console navigation tree, right-click the User Manager icon.

Then select New  Group, which displays the New User Properties dialog box.

Click the General tab, enter the group name in the Name field. Note that you can enter any group name that you want to use. Display Name and Description are optional.

Click the Groups and Roles tab and add the appropriate users and groups.

Click the Accounts tab and click New to display New Login Properties dialog box.

Enter your domain and user ID (WindowsDomain\user) and the password.

Select DefaultAuth as the authentication domain. Click OK.

Click the Members tab and add all of the users that need to access this library. To provide access for all registered users, give logon access to the SASUSERS group by moving it from the Available Identities box to the Current Members box. Then click OK.

Click User Manager to verify that the name appears in the user group name list.

The SAS Environment Manager Users module supports some of the user administration tasks that are provided by the User Manager plug-in to SAS

Management Console, including the following: n creation and maintenance of users, groups, and roles n management of group and role memberships n management of logins and internal accounts

For more information about the SAS Environment Manager Users module, see

“Managing User Access” in SAS Environment Manager Administration: User's Guide.

Register the DBMS Server

To register a DBMS server, perform the following steps:

Overview of SAS/ACCESS Connections to Relational Databases

1 Right-click Server Manager and select the New Server option to access the New

Server wizard.

2 Select the database server type from the Database Servers list. Then, click Next.

3 Enter an appropriate server name in the Name field. Click Next.

4 Accept the defaults for the server properties. Click Next.

5 Specify the database vendor-specific values on the connection properties page. If the user credentials for the database are different from the credentials used to log on to SAS, then you must create an Authentication domain to store valid database credentials. For more information, see “How to Store Passwords for a Third-Party

Server” in SAS Intelligence Platform: Security Administration Guide .

Click Next.

6 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Register the DBMS Library

To register a DBMS library, perform the following steps:

1 In SAS Management Console, expand Data Library Manager. Right-click Libraries and select the New Library option to access the New Library wizard.

2 Select the database type from the Database Data list. Click Next.

3 Enter an appropriate library name in the Name field. Click Next.

4 Select an application server from the list, and use the right arrow to assign the application server. This step makes the library available to the server and makes the library visible to users of the server. Click Next.

5 Specify a libref on the library properties page. You can also click Advanced Options to perform tasks such as pre-assignment. Pre-assigning a library is valuable if your clients include SAS Enterprise Guide or SAS Add-In for Microsoft Office. Some SAS

Chapter 4 / Connecting to Common Data Sources

solutions require that libraries accessed from their client applications be preassigned (check the documentation for your specific solution for details). For more

information, see Chapter 3, “Assigning Libraries,” on page 43

. Click Next to access the next page of the wizard.

6 On the server and connection page, select the database server from the previous stage. Contact your database administrator if you are unsure of the correct value for the schema field. Click Next.

7 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings. At this point, register tables as

explained in “Registering and Verifying Tables” on page 171

Using the Folders Tab in SAS

Management Console

All SAS folders that the user has permission to view are displayed in the Folders tab of

SAS Management Console and in the Folders view of the Administration tab in SAS

Environment Manager. Most other client applications display SAS folders only if they contain content that is relevant to the application, subject to the user's permissions. For more information, see “Working with SAS Folders” in SAS Intelligence Platform: System

Administration Guide

Establishing Connectivity to a Library of

SAS Data Sets

Overview of Establishing Connectivity to a

Library of SAS Data Sets

The following figure provides a logical view of accessing a library of SAS data sets.

Establishing Connectivity to a Library of SAS Data Sets

Figure 4.1 Establishing Shared Access to SAS Data Sets

SAS Data

Integration Studio

Workspace Server

Base SAS Engine

Library of

SAS Data Sets

Data (Local or Remote) Client SAS Application Server

After you have installed the required SAS software, you need to set up a connection from a SAS server to a SAS data set. This connection requires that you register the

Base SAS library with the SAS Metadata Server. In addition, you must import any userdefined formats that have been created for the data set in order to view or operate on the data. Assume that the SAS software has already been loaded by using the standard installation wizard and that the data set is stored in a location that can be accessed.

This metadata enables your SAS applications to access the data sets that you need to work with. For this example, the data set contains information about customers of the

Orion Gold enterprise.

Register the Base SAS Library Using SAS

Management Console

To register a Base SAS library, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the first page of the New Library wizard.

Select Base SAS Library from the SAS Data list. Click Next.

Chapter 4 / Connecting to Common Data Sources

3 Enter an appropriate library name in the Name field (for example, Orion Gold

Customers). Note that you can supply an optional description if you want. Click Next.

Select the appropriate server from the Available servers list and move it to the

Selected servers list. For this example, use SASApp. Click Next.

Enter the following library properties:

Table 4.1 Library Properties

Field

Libref

Engine

Path Specification

Sample Value

ORGOLD

BASE

Select from the Available items or click New to enter a path (for example,

C:\SAS\Config\Lev1\SASApp

\Data

). (Enter the fully qualified path to the library.

This path is specified differently in different operating systems. Make sure that the appropriate path is displayed in the Selected items field.)

You can also click Advanced Options to perform tasks such as pre-assignment and setting host-specific and LIBNAME options. Click Next to access the next page of the wizard.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

At this point, register tables as explained in “Registering and Verifying Tables” on page

At this point, register tables as explained in “Registering and Verifying Tables” on page

. If registering tables fails, check that the user account has host access permission to the path.

Register the Base SAS Library Using SAS

Environment Manager

To register a Base SAS library, perform the following steps:

Establishing Connectivity to a Library of SAS Data Sets

1 Click the Administration tab.

2 Click the Side Menu icon in the upper left corner of the window.

3 Click Libraries.

4 Click the New Library icon .

5 Enter a library Name (for example, Orion Gold). The name cannot contain a forward slash or a backslash. If necessary, change the Location. Click SAS Base

Library. The Options dialog box appears.

In the Options dialog box, enter the Libref.

Field

Libref

Engine

Sample Value

Enter an identifier of your choice (for example,

OrGold

). The libref name cannot contain spaces. The first character must be a letter or an underscore and all other characters can be either letters, underscore, or numbers.

Click the down arrow at the right of the field. From the resulting dropdown list, select an engine. For this example, the value (

Base

) is the engine name.

If you need WebDAV support, select the check box.

Enable

WebDAV support

Specify the path to the library

For this example, select the /install/data/SAS check box.

Click OK.

Examine the page to ensure that the proper values have been entered. Enter the

Description. Click the Save icon to save the new library.

Chapter 4 / Connecting to Common Data Sources

Working with User-Defined Formats

Choices for Working with User-Defined Formats

If you have existing SAS data sets, you might also have a catalog of user-defined formats and informats. You have two options for making these formats available to applications such as SAS Data Integration Studio and SAS Information Map Studio: n

Give the format catalog a standard name and place it in an expected location. This is the preferred method.

Create a user-defined formats configuration file, and use the FMTSEARCH system option to point to the format catalog.

Use a Standard Name and Location for the Format Catalog

To make the format catalog available, in the preferred method, perform the following steps:

1 Name the format catalog formats.sas7bcat.

2 Place the catalog in the directory SAS-configuration-directory\Lev1\SASApp

\SASEnvironment\SASFormats.

Create a User-Defined Formats Configuration File

Alternatively, you can create a user-defined formats configuration file in which you point to the location of the formats catalog.

To make a format catalog available using the alternative method on Windows and UNIX systems, perform the following steps:

To the SAS configuration file SAS-configuration-directory\Lev1\SASApp

\sasv9_usermods.cfg, add the CONFIG system option, and use it to point to the user-defined formats configuration file:

-config "SAS-configuration-directory\Lev1\SASApp\userfmt.cfg"

Then, use the FMTSEARCH system option in the same SAS configuration file to point to the format catalog:

Establishing Connectivity to a Library of SAS Data Sets

-set fmtlib1 "SAS-configuration-directory\Lev1\Data\orformat"

-insert fmtsearch (fmtlib1.orionfmt)

In this example, SAS-configuration-directory\Lev1\Data\orformat is the location of the format catalog, and orionfmt (filename orionfmt.sas7bcat) is the name of the format catalog. If you have more than one catalog to list, leave a space between each catalog name.

Note:

On UNIX systems, you must enter the environment variable name in uppercase. For example, you enter FMTLIB1 instead of fmtlib1.

To make a format catalog available using the alternative method on z/OS systems, perform the following steps:

1 Add the AUTOEXEC system option to the SAS launch command as shown in the following example:

SAS-configuration-directory/Lev1/SASApp/startsas.sh

o("autoexec="./WorkspaceServer/userfmt.sas"")

In this example, startsas.sh is your SAS launch command script, and userfmt.sas is the name of the SAS autoexec file. When you enter the command, you must enter it all on one line.

In the autoexec file, use the LIBNAME statement to assign the format library and the

OPTIONS statement to set the FMTSEARCH system option. For example, you might specify the following statements:

LIBNAME fmtlib1

'SAS-configuration-directory/Lev1/Data/orformat'; options fmtsearch=(fmtlib1.orionfmt);

Chapter 4 / Connecting to Common Data Sources

Establishing Shared Access to SAS

Data Sets

Overview of Establishing Shared Access

The following figure provides a logical view of accessing SAS data sets through a

SAS/SHARE server.

Figure 4.2 Establishing Shared Access to SAS Data Sets

SAS Data

Integration Studio

Workspace Server

SAS/SHARE

Server

SAS/SHARE

REMOTE Engine

Base SAS Engine

Library of

SAS Data Sets

Data Server Client SAS Application Server

Base SAS libraries allow the following access: n

Any number of users can read data.

A single user can write or update data.

This access can be extended through the use of the SAS/SHARE server. A

SAS/SHARE server permits multiple users to update the same items in a SAS library.

You can share access to a library of existing SAS data sets by using a SAS/SHARE server to manage access to the data. Assume that the SAS/SHARE software has already been loaded by using the standard installation wizard, and that you have registered a SAS/SHARE server in metadata (for example, SHAREServer) that was created by the wizard. Configuring shared access is a two-stage process:

Establishing Shared Access to SAS Data Sets

1 Create a SAS/SHARE REMOTE Engine Library. This library is assigned to a SAS

Application Server, as shown in the previous figure.

2 While creating the SAS/SHARE REMOTE Engine Library, choose the option to register a new library to the SAS/SHARE server. This is shown in the previous figure as a Base SAS library. It is very important to pre-assign this library and to assign it to the SAS/SHARE server.

Create a SAS/SHARE Remote Engine Library

Using SAS Management Console

To create a SAS/SHARE Remote Engine library, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

Select SAS/SHARE REMOTE Engine Library from the SAS Data list. Click Next.

Enter an appropriate library name in the Name field (for example,

SharedAccessToOrionGold). You can supply an optional description. Click Next.

Select the appropriate server from the Available servers list and move it to the

Selected servers list. For this example, use SASApp. Click Next.

Enter a value for Libref and click Next.

Enter the following library properties:

Table 4.2 Server and Connection Information

Field

SAS/SHARE Server

SAS/SHARE Server Library

Sample Value

SHAREServer

Click New to register a new library such as a Base

SAS library. Assign the new library to the

SAS/SHARE Server and set the library as preassigned.

Chapter 4 / Connecting to Common Data Sources

Sample Value Field

Connection

Default Login (None)

(This default login is used to resolve conflicts between multiple logins to an authentication domain.

In such cases, the default login is used.)

Click Next.

Examine the final page of the wizard (for the SAS/SHARE REMOTE Engine Library) to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Restart the SAS/SHARE server.

At this point, register tables as explained in “Registering and Verifying Tables” on page 171

Create a SAS/SHARE Remote Engine Library

Using SAS Environment Manager

To create a SAS/SHARE Remote Engine library, perform the following steps:

Click the Administration tab.

Click the Side Menu icon in the upper left corner of the window.

Click Libraries.

Click the New Library icon .

Enter a library Name (for example, SharedAccessToOrionGold). The name cannot contain a forward slash or a backslash. Change the Location using Browse to /

Shared Data. Click SAS Base Library. The Options dialog box appears.

In the Options dialog box, enter the Libref.

Field

Libref

Engine

Establishing Connectivity to a Microsoft Excel File

Sample Value

Enter an identifier of your choice (for example,

ShareLib

). The libref name cannot contain spaces. The first character must be a letter or an underscore and all other characters can be either letters, underscore, or numbers.

Click the down arrow at the right of the field. From the resulting dropdown list, select an engine. For this example, the value (

Base

) is the engine name.

If you need WebDAV support, select the check box.

Enable

WebDAV support

Specify the path to the library

For this example, select the /install/data/SAS check box.

Click OK.

Examine the page to ensure that the proper values have been entered. Enter the

Description. Click the Save icon to save the new library.

Establishing Connectivity to a Microsoft

Excel File

Overview of Establishing Connectivity to an

Excel File

The following figure provides a logical view of using an Excel file as a data source.

Chapter 4 / Connecting to Common Data Sources

Figure 4.3 Establishing Connectivity to an Excel File

SAS Data

Integration Studio

Workspace Server

Base SAS Code

Client SAS Application Server Files

The Excel file must be stored in a location that can be accessed by a Windows machine. This example focuses on a file that is local to a SAS server, but a Windows

UNC path such as \\datasrv\sales\firstquarter.xls is also acceptable.

Note:

Mapped drives are not accessible to SAS Application Servers.

To establish connectivity to an Excel file, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

Select Microsoft Excel Library from the Database Data list. Click Next.

Enter a value for Libref and click Next.

Enter an appropriate library name in the Name field (for example,

FirstQuarterSales). Specify a metadata folder location for the library in the Library field. You can supply an optional description. Click Next.

Select the appropriate server from the Available servers list and move it to the

Selected servers list. For this example, use SASApp. Click Next.

On the server and connection page, click New in the Server Details group box to specify a new database server.

Establishing Connectivity to a Flat File

The New Server wizard is displayed.

7 Enter a name such as FirstQuarterSalesFolder in the Name field. Click Next.

8 Click Next on the Server Properties page.

9 On the Connection Properties page, enter the path to the Excel file. Enclose the value in quotation marks (for example, "C:\sales\firstquarter.xls"). Click Next.

Examine the final page of the New Server wizard to ensure that the proper values have been entered. Click Finish to save the server settings.

The New Server wizard closes and returns you to the final page of the New Library wizard.

Examine the final page of the New Library wizard to ensure that the proper values have been entered. Click Finish to save the library settings.

The Microsoft Excel Library wizard in SAS Management Console generates the metadata to construct a LIBNAME statement for the EXCEL LIBNAME engine. For more information about the EXCEL LIBNAME engine and supported options, see the

SAS/ACCESS Interface to PC Files: Reference.

Establishing Connectivity to a Flat File

The following figure provides a logical view of using an external file as a data source.

Chapter 4 / Connecting to Common Data Sources

Figure 4.4 Establishing Connectivity to External Files

SAS Data

Integration Studio

Workspace Server

Base SAS Code

Client SAS Application Server Files

You can connect to a flat file using the External File Source Designer in SAS Data

Integration Studio.

Assume that the SAS software has already been loaded by using the standard installation wizard, and that the flat file is stored in a location that can be accessed. This example focuses on a comma-delimited flat file. A similar process is used for other types of flat files, but some steps are different.

To establish a connection to a flat file, perform the following steps:

1 Open SAS Data Integration Studio. Then, select File  New  External File 

Delimited to access the New Delimited External File wizard.

Enter a name for the external file and click Next.

Enter the fully qualified path to the file in the File name field (for example, SAS-

configuration-directory\sources\customer_data.dat). Click Next.

On the Delimiters and Parameters page of the wizard, deselect the Blank option in the Delimiters group box. Then, select the Comma option. Click Next to access the

Column Definitions page of the wizard.

To define the columns, perform the following steps:

Establishing Connectivity to a Flat File

85 a Click Refresh to view the data from the flat file in the File tab in the view pane at the bottom of the page.

b Click Auto Fill to access the Auto Fill Columns dialog box. Change the value entered in the Start record field in the Guessing records group box to 2. This setting is based on the assumption that the first data record of the flat file contains header information and that the record is unique because it holds the column names for the file. Therefore, excluding the first data record from the guessing process yields more accurate preliminary data because it is excluded when the guessing algorithm is run.

Click Import to access the Import Column Definitions dialog box. The following four methods are provided for importing column definitions: n

Get the column definitions from other existing tables or external files.

Get the column definitions from a format file.

Get column definitions from a COBOL format file.

Get the column names from column headings in the file.

In most cases, you get the column definitions from an external format file or from the column headings in the external file. Here is an example of a format file:

# Header follows

Name,SASColumnType,SASColumnName,SASColumnLength,SASInformat,SASFormat,Desc,ReadFlag

# Column definition records records follow

Make,C,Make,13,,$char13.,Manufacturer name column,y

Model,C,Model,40,,$char40.,Model name column,y

# Comma within quotation marks below is not a delimiter

Description,C,Description,32,$char32.,,'Description, Comments, Remarks',y

A sample of the output is shown in the following figure:

Chapter 4 / Connecting to Common Data Sources

For this example, select the Get the column names from column headings in the

file radio button. Keep the default settings for the fields underneath it.

Note:

If you select Get the column names from column headings in the file, the value in the Starting record field in the Data tab of the view pane in the Column

Definitions dialog box is automatically changed. The new value is one greater than the value in the The column headings are in file record field in the Import Column

Definitions dialog box.

7 Click OK to return to the Column Definitions page.

8 The preliminary data for the external file object is displayed in the columns table at the top of the page. The Informat and Format columns for the rows in the table are based on the values that are included in the sample data that is processed by the guessing function. The results are accurate for this particular set of records, but you should still examine them to make sure that they are representative of the data in the rest of the flat file. Edit the values by clicking directly on the cells in the column table and making the necessary changes.

9 Click the Data tab at the bottom of the Column Definitions page. Then, click

Refresh. The data should be properly formatted. If not, edit the cells in the column table and check the results by refreshing the Data tab. You can repeat this process until you are satisfied. You can review the SAS log for more details.

Note:

To view the code that is generated for the external file, click the Source tab.

To view the SAS log for the generated code, click the Log tab. The code that is displayed in the Source tab is the code that is generated for the current external file.

10 Click Next.

Establishing Connectivity to XML Data

11 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings. The file is ready for use.

Establishing Connectivity to XML Data

The following figure provides a logical view of using XML files as a data source.

Figure 4.5 Establishing Connectivity to XML Files

SAS Data

Integration Studio

Workspace Server

Base SAS Code

Client SAS Application Server XML Files

The following steps describe how to specify a SAS XML library in SAS Management

Console. Assume that the XML library points to an XML file that contains climate information (climate.xml). The XML file is in generic format, as defined for the SAS

XML LIBNAME engine. For more information, see the SAS XML LIBNAME Engine:

User's Guide.

To register an XML library, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

Select SAS XML library from the SAS Data list. Click Next.

Chapter 4 / Connecting to Common Data Sources

3 Enter an appropriate library name in the Name field (for example, XML Lib). Click

Next.

Select the appropriate server from the Available servers list and move it to the

Selected servers list. For this example, use SASApp. Click Next.

Enter information about the library, such as the following:

Table 4.3 Library Properties

Field

Libref

Engine

XML File Location

XML Type

Library Access

Sample Value xmllib

XML

C:\sources\xml\climate.xml

GENERIC

READONLY

Click Next.

6 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Establishing Connectivity to a SAS

Information Map

Overview of Establishing Connectivity to a

SAS Information Map

A SAS Information Map is a business metadata layer on top of another data source.

When an information map is registered as a table in a SAS Information Map library, it

Establishing Connectivity to a SAS Information Map

89 can also be used as the data source for other information maps. For more information about creating information maps, see either the SAS Information Map Studio Help or

Base SAS Guide to Information Maps. Information map tables are expected to be used primarily by SAS Information Map Studio.

Figure 4.6 Establishing Connectivity to an Information Map

SAS Information

Map Studio

Workspace Server

Information Maps

LIBNAME Engine

Metadata Server

Information Maps

Client SAS Application Server Data Server

To register a SAS Information Map library, perform the following steps:

1 In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

2 Select SAS Information Map Library from the SAS Data list. Click Next.

3 Enter an appropriate library name in the Name field (for example, InfoMapLib). Click

Next.

Select the appropriate server from the Available servers list and move it to the

Selected servers list. For this example, use SASApp. Click Next.

Enter information about the library, such as the following:

Table 4.4 Library Properties

Field

Libref

Sample Value maplib

Chapter 4 / Connecting to Common Data Sources

Field

Engine

Metadata server

Default login

Information map location

Sample Value

SASIOIME

select a metadata server from the list

(None)

/Shared Data/SASInfoMaps

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings. At this point, register tables as

explained in “Registering and Verifying Tables” on page 171

Special Considerations for Information Map

Tables

When registering the tables with SAS Management Console, ensure that the check box for the option Enable special characters within DBMS object names option is selected. The New Library wizard uses data item IDs from the source information map as column names for the table. These data item IDs sometimes contain special characters.

The data item IDs of a source information map are used as column names when the information map is registered as an information map table. If you change the data item ID or table column name after the table is registered, then you will not be able to run queries on the table.

By default, the values retrieved from an information map table are the detail values from the source information map. If you want to retrieve aggregated values, then you must set an aggregation option. You can set the AGGREGATE= options for tables and libraries in Data Library Manager in SAS Management Console. After you add a table as a data source for an information map, you can also set the aggregation option for the data source in the Table Properties dialog box in SAS Information Map

Establishing Connectivity to a SAS Information Map

91 n

Studio. Selecting the Use the detail values from the data source radio button is equivalent to setting the AGGREGATE= option to NO, and selecting the Use the

aggregated values from the data source radio button is equivalent to setting the

AGGREGATE= option to YES. This setting overrides the aggregation settings on the library or the table.

When referenced by an information map table, measure data items that reference other measure data items or that use aggregate functions in their expressions can produce aggregated values only. If a source information map contains one of these data items, then set the AGGREGATE= option to YES on the library. Otherwise, these data items are not registered as columns when you register the information map as a table.

If the source information map for an information map table has measure data items that reference other measure data items or that use aggregate functions in their expressions, then the combination of setting the AGGREGATE= option to YES on the library and setting the AGGREGATE= option to NO on the table or on the data source (within SAS Information Map Studio) causes the table data to be inaccessible. n

Normally, when an information map table is registered, its columns get their formats from the associated source data items. However, when a source data item is a measure data item and has a data type of character, then if the AGGREGATE= option is set to NO on the library, the format is not set to the format of the source data item. The format is set to the format of the column that the source data item is based on.

Because an information map acts as a reference to underlying data, ReadMetadata permission must be granted to a user for the information map table, the source information map, and the table used by the source information map. Read permission is also needed on the source information map.

Stored processes and prefilters associated with a source information map are applied to the information map table. (Filters that are not used as prefilters are not applied.) n

If a stored process is associated with a source information map and the stored process uses prompts with default values, the stored process is applied to the

Chapter 4 / Connecting to Common Data Sources

n information map table. If the prompts do not have default values, the stored process does not affect the information map table.

Information maps created from OLAP cubes cannot be registered as information map tables.

The source information map name must be 32 bytes or less.

Establishing Connectivity to an ODBC

Database Using Microsoft Windows NT

Authentication

Overview of Establishing Connectivity to an

ODBC Database Using Microsoft Windows NT

Authentication

The following figure provides a logical view of using ODBC with SAS/ACCESS software.

Figure 4.7 Establishing Connectivity to an ODBC Database

SAS Data

Integration Studio

Client

Workspace Server

SAS/ACCESS

Interface to ODBC

ODBC Driver

Manager

ODBC Driver

SAS Application Server

Microsoft Access

Database

Database Tables

Data Server

Establishing Connectivity to an ODBC Database Using Microsoft Windows NT Authentication

This example explains how to define an Open Database Connectivity (ODBC) library in

SAS Management Console using Windows authentication to access Microsoft SQL

Server data. In this section, the SAS server is running in a Windows operating environment. Once you define the ODBC library, you can use the library with SAS

Enterprise Guide and SAS Data Integration Studio.

Prerequisites

The following prerequisites are necessary before you can define an ODBC library in

SAS Management Console.

Make sure that “Login as batch” user rights are assigned for your user ID (entered in the WindowsDomain\user). For details about assigning user rights, see your

Windows operating system documentation.

SAS/ACCESS Interface to ODBC and the ODBC driver for the Microsoft SQL Server must be installed and configured on the same machine where your SAS System runs.

Setting up a connection from SAS to an ODBC data source using Microsoft Windows

NT authentication is a five-stage process.

1 Configure an ODBC data source using Microsoft Windows NT authentication.

2 Verify a library by submitting a LIBNAME statement with the ODBC engine.

3 Register a user.

4 Register the ODBC Server.

5 Register the ODBC library.

Stage 1: Configure an ODBC Data Source

Using Microsoft Windows NT Authentication

Select Start  Control Panel.

Chapter 4 / Connecting to Common Data Sources

2 In the Control Panel window, select System and Security  Administrative Tools



Data Sources (ODBC) to open the ODBC Data Source Administrator dialog box.

Click the System DSN tab. On that tab, click Add to open the Create New Data

Source dialog box.

Select SQL Server in the Create New Data Source dialog box.

Click Finish, and the Create a New Data Source to SQL Server dialog box appears.

Enter the name of your data source and the name of your server. This example uses the values SqlServerNT and BLUEFIN, respectively.

Click Next. On this page, specify the following items: n the method for verifying the login ID n the network library that is used to communicate with the SQL Server (via the

Client Configuration button) n a connection to the SQL Server

Establishing Connectivity to an ODBC Database Using Microsoft Windows NT Authentication

Click Next to make further server-configuration changes, as necessary.

Click Finish. The application displays a summary page.

At this point, you should click Test Data Source to run a test connection and ensure that your configuration is valid. If the test is successful, the Test Results page is displayed.

Click OK to exit.

Click OK again to exit the ODBC Data Source Administrator dialog box.

Stage 2: Create a Library By Submitting a

LIBNAME Statement with the ODBC Engine

1 Invoke SAS.

2 Submit a LIBNAME statement that contains the ODBC engine in the SAS Enhanced

Editor. The LIBNAME statement should be similar to the following: libname odbclib odbc noprompt="dsn=SqlServerNT;Trusted_Connection=yes" schema=DBO;

3 After you submit this LIBNAME statement, make sure that you can see your SQL

Server tables in the SAS Explorer window. You can also submit a DATASETS procedure similar to the following to display the tables in the SAS log:

Chapter 4 / Connecting to Common Data Sources

proc datasets lib=odbclib; quit;

The previous steps confirm that the ODBC data source was created correctly and that you can access the tables in the Microsoft SQL Server. If another user has trouble accessing the tables from the registered library (described in the following stages), then ask the user to try these steps or request assistance from your Windows administrator.

Stage 3: Register a User

1 Open SAS Management Console and log on with the user ID SASADM or with the

ID of any other unrestricted user. The SAS Management Console window is displayed.

2 Right-click User Manager in the left pane. Select New  User. This selection opens the New User Properties dialog box.

Click the General tab in the New User Properties dialog box, and add the user name in the Name text box. Display Name, Job Title, and Description are optional.

Click the Accounts tab. Click New to open the New Login Properties dialog box.

Add the Windows user ID (in the form WindowsDomain\user) and password in the

New Login Properties dialog box. Click OK. The user ID and password appear in the

New Users Properties dialog box.

Click OK to return to the main SAS Management Console window.

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Stage 4: Register the ODBC Server

Right-click Server Manager in the SAS Management Console window.

Select New Server from the menu. This selection invokes the New Server wizard.

Establishing Connectivity to an ODBC Database Using Microsoft Windows NT Authentication

Select ODBC Server from the Database Servers list in the New Server wizard.

4 Click Next. Specify a name for the new ODBC server, such as sql_server_ntauth. The Description field is optional.

Click Next to continue to the next page, which lists the default property values for the server.

Note:

Do not change these default values. Just click Next to continue to the next page in the wizard.

Table 4.5 Server Properties

Field

Major Version Number

Minor Version Number

Data Source Type

Software Version

Vendor

Associated Machine

Sample Value

ODBC — Other Database

6.10

Defaults to vendor name

Defaults to your machine name

6 Click Next.

7 Select the Connection String radio button.

Chapter 4 / Connecting to Common Data Sources

Enter the following string in the Connection String text box:

"dsn=SQlServerNT;Trusted_Connection=yes"

Note:

The value for the DSN= parameter is the name of the ODBC-system data source that you set up in stage 1.

Select None for Authentication type. Select DefautAuth for the Authentication

domain.

Note:

If you do not want to create a data source name, you can connect without using the DSN= parameter. Instead, submit the following LIBNAME statement: libname test odbc noprompt='server=bluefin.your-domain.com;driver=sql

Establishing Connectivity to an ODBC Database Using Microsoft Windows NT Authentication

99 server;Trusted Connection=yes';

In this case, you enter the following as the connection string in the Connection

String text box:

'server=bluefin.your-domain.com;driver=sql server;

Trusted Connection=yes'

8 Click Next.

9 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 5: Register the ODBC Library

1 Expand Data Library Manager in SAS Management Console.

2 Right-click Libraries and select New Library to open the New Library wizard.

3 Select ODBC Library from the Database Data list. Click Next.

4 Specify a name for your library (for example, sql_server_ntauth) Click the

Browse button by Location to select the metadata folder location.

Click Next. Select the appropriate server from the Available servers list and move it to the Selected servers list. For this example, use SASApp.

Click Next.

Enter a libref in the Libref text box, such as Odbclib.

Table 4.6 Library Properties

Field

Libref

Engine

Sample Value

Odbclib

ODBC

100

Chapter 4 / Connecting to Common Data Sources

8 Click Next.

9 Specify the schema name (DBO) and the database server (sql_server_ntauth).

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

At this point, your library is defined. However, to access data, you might need to perform extra steps (for example, pre-assigning the library or registering tables). See

“Registering and Verifying Tables” on page 171

Establishing Connectivity to an OLE DB

Database Using Microsoft Windows NT

Authentication

Overview of Establishing Connectivity to an

OLE DB Database Using Microsoft Windows

NT Authentication

The following figure provides a logical view of using OLE DB with SAS/ACCESS software.

Establishing Connectivity to an OLE DB Database Using Microsoft Windows NT

Authentication

101

Figure 4.8 Establishing Connectivity to an OLE DB Database

SAS Data

Integration Studio

Workspace Server

SAS/ACCESS

Interface to OLE DB

OLE DB

Data Provider

SAS Application Server

Database Server

Client Data Server

This section explains how to define an OLE DB library in SAS Management Console in order to access the Microsoft SQL Server using Microsoft Windows NT authentication.

Prerequisites

The following prerequisites are necessary before you begin defining an OLE DB library: n

Make sure that “Login as batch” rights are assigned for your user ID (entered in the

WindowsDomain\user). For details about assigning user rights, see your Windows operating system documentation.

SAS/ACCESS Interface to OLE DB and the OLE DB provider for the Microsoft SQL

Server must be installed on the same machine where SAS runs.

Before you configure the library in SAS Management Console, make sure that you can submit a LIBNAME statement successfully. Here is an example of a LIBNAME statement: libname sqlole oledb init_string="Provider=SQLOLEDB.1;

Integrated Security=SSPI;

Persist Security Info=True;

Initial Catalog=Northwind;

Data Source=bluefin.na.sas.com" schema=DBO;

102

Chapter 4 / Connecting to Common Data Sources

Note:

If you cannot see SQL Server tables in the SAS Explorer window, then you need to submit the following SQL procedure to find the table names and the corresponding schema for each table.

proc sql; connect to oledb; select table_name, table_schema from connection to oledb(OLEDB::Tables); quit;

To define a user or user group using SAS Management Console, see “Define the DBMS

For more information, see “Relational Database Sources” on page 11 .

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection from SAS to an OLE DB database using Microsoft Windows NT authentication is a four-stage process.

1 Register the OLE DB server.

2 Register the OLE DB library.

3 Verify that the SQL Server tables are listed in the SAS Explorer.

4 Register the SQL Server tables.

Stage 1: Register the OLE DB Server

To register an OLE DB server, perform the following steps:

1 From the navigation tree, right-click Server Manager and select the New Server option to access the New Server wizard.

2 Expand the Database Servers folder and select OLE DB Server.

3 Click Next.

4 Enter the server name (for example, sqlserver_oledb_ntauth) in the Name field. The Description field is optional.

Establishing Connectivity to an OLE DB Database Using Microsoft Windows NT

Authentication

103

Click Next to display the server properties. The following server properties displayed in the data entry box are default values and should not be changed.

Table 4.7 Server Properties

Field

Major Version Number

Minor Version Number

Data Source Type

Software Version

Vendor

Associated Machine

Sample Value

OLE DB — Other Database

4.0

Microsoft Corp.

Defaults to your machine

Note:

The Associated Machine property refers to the SAS Application Server - not the SQL Server machine.

Click Next.

Enter the server name "bluefin.na.sas.com" (in quotation marks) for the SQL

Server in the Datasource field. Enter the Provider.

Table 4.8 Connection Properties

Field

Datasource

Provider

Sample Value

Enter "bluefin.na.sas.com" (in quotation marks) from the example LIBNAME statement.

Enter SQLOLEDB.1 from the example LIBNAME statement.

The default is NO.

Prompt

OLE DB Connection

Information Options

104

Chapter 4 / Connecting to Common Data Sources

Field

Authentication type

Authentication Domain

Sample Value

User/Password

Specify the credentials (in this example, user/ password) that are retrieved from metadata and that correspond to the selected authentication domain,

OledbAuth.

OledbAuth

Specify the domain (in this example, OledbAuth) that is used to authenticate logon attempts to the OLE DB server. (You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Click the OLE DB Connection Information Options button to display the OLE DB

Connection Information Options dialog box.

8 Enter the following text In the Init String field. Enter the entire string in quotation marks (" "), all on one line.

"Provider=SQLOLEDB.1;

Integrated Security=SSPI;

Persist Security Info=True;

Initial Catalog=Northwind;

Establishing Connectivity to an OLE DB Database Using Microsoft Windows NT

Authentication

105

Data Source=bluefin.na.sas.com"

9 Click OK.

10 Specify Authentication Type and Authentication Domain.

11 Click Next.

12 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

13 In SAS Management Console, click the Server Manager icon.

The new OLE DB server name, sqlserver_oledb_ntauth, appears in the Name list.

Stage 2: Register the OLE DB Library

From the navigation tree in SAS Management Console, expand Data Library

Manager.

Under Data Library Manager, right-click Libraries and select New Library to start the New Library wizard.

In the wizard, expand the Libraries



Database Data folder and select OLE DB

Library. Click Next.

Enter the library name (for example, sqlserver_oledb_ntauth_lib) in the

Name field. The Description field is optional.

5 Click Next.

6 Select the appropriate server from the Available servers list and move it to the

Selected servers list on the right. For this example, use SASApp. Click Next.

7 Enter the libref name (for example, SqlOledb) in the Libref field.

106

Chapter 4 / Connecting to Common Data Sources

Table 4.9 Library Properties

Field

Libref

Engine

Sample Value

SqlOledb

OLEDB

Click Next.

In the Database Server field, select the OLE DB server

(sqlserver_oledb_ntauth).

In the Database Schema Name field, enter a name (for example, DBO) for the new

OLE DB schema.

Note:

This is the same database schema name specified in the LIBNAME statement: libname sqlole oledb init_string="Provider=SQLOLEDB.1;

Integrated Security=SSPI;

Persist Security Info=True;

Initial Catalog=Northwind;

Data Source=bluefin.na.sas.com" schema=DBO;

Note that the database schema name must be uppercase in the LIBNAME statement.

Table 4.10 Server and Connection Information

Field

Database Server

Database Schema Name

Connection

Default Login

Sample Value

Enter

sqlserver_oledb_ntauth

from the

LIBNAME statement example. (Use the database server that you created in the New Server wizard.)

Enter DBO from the LIBNAME statement example.

Use the default value.

Use the default value of

(None)

Establishing Connectivity to an OLE DB Database Using Microsoft Windows NT

Authentication

107

Click Next.

10 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings. The new library

(sqlserver_oledb_ntauth_lib) appears in the list of libraries.

Stage 3: Verify That the SQL Server Tables

Are Listed in the SAS Explorer

Perform the following steps to check the accuracy of the LIBNAME statement that was generated in the previous section:

Close SAS Management Console and restart it using the same Windows ID

(WindowsDomain\user) that you previously used.

From the navigation tree in SAS Management Console, right-click Data Library

Manager.

Under Data Library Manager, right-click the library that you just created

(sqlserver_oledb_ntauth_lib) and select Display LIBNAME Statement. The

Display LIBNAME Statement message window appears with the LIBNAME statement that is generated for your server.

4 Copy the LIBNAME statement from the Display LIBNAME Statement window and paste it into your SAS Program Editor.

5 Submit the LIBNAME statement and verify that the appropriate tables are listed in the SAS Explorer window.

Stage 4: Register the SQL Server Tables

1 From the navigation tree in SAS Management Console, expand Data Library

Manager.

108

Chapter 4 / Connecting to Common Data Sources

2 In the Data Library Manager, right-click sqlserver_oledb_ntauth_lib and select Register Tables.

In the SAS Library field, click the down arrow at the right of the field. From the resulting drop-down list, select your application server (SASApp, in this example), and click Next.

Click Next again, and the Define Tables dialog box is displayed with a list of SQL

Server tables.

In the list, click the table name for which you want to import metadata.

Click Next, and the application displays the table that you selected.

Click Finish, and you are able to use the specified table in any SAS BI client.

Establishing Connectivity to a Teradata

Database

Overview of Establishing Connectivity to a

Teradata Server

The following figure provides a logical view of using Teradata with SAS/ACCESS software.

Establishing Connectivity to a Teradata Database

109

Figure 4.9 Establishing Connectivity to a Teradata Database

SAS Data

Integration Studio

Workspace Server

SAS/ACCESS

Interface to Teradata

Teradata Client

Teradata Server

Client SAS Application Server Data Server

To define a database library in SAS Management Console with the SAS/ACCESS software, you need SAS/ACCESS Interface to Teradata software installed on your SAS server.

To define a user or user group using SAS Management Console, see “Define the DBMS

“Registering and Verifying Tables” on page

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection from SAS to a Teradata database is a two-stage process.

1 Register the Teradata server.

2 Register the Teradata library.

Stage 1: Register the Teradata Server

To register the Teradata Server, perform the following steps in SAS Management

Console:

1 Right-click the Server Manager and select New Server from the menu. This selection invokes the New Server wizard.

110

Chapter 4 / Connecting to Common Data Sources

2 Select Teradata Server (under Database Servers) in the New Server wizard. Then click Next.

3 Specify a name for the new Teradata server. The Description is optional.

4 Click Next to continue. This page lists default server properties. Do not change these default values.

Table 4.11 Server Properties

Field

Major Version Number

Minor Version Number

Software Version

Vendor

Associated Machine

Sample Value

14.0

Teradata Corporation

Defaults to your machine

Click Next to continue. On this page, enter the Teradata connection properties for your Teradata database.

Table 4.12 Connection Properties

Field

Server

Account number

Sample Value

Specify an entry in your (client) HOSTS file that provides an IP address for a database server connection. The value for this property corresponds to the value for the SERVER= option in the

SAS/ACCESS software LIBNAME statement.

Specify the account number that you want to charge for the Teradata session. Note: This property is optional.

Field

Authentication type

Authentication Domain

Establishing Connectivity to a Teradata Database

111

Sample Value

User/Password

specify the credentials (in this example, user and password) that are retrieved from metadata and that corresponds to the selected authentication domain, TeraAuth.

Specify the domain (in this example,

Teraauth

) that is used to authenticate logon attempts to the

Teradata server. (You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register the Teradata Library

This example shows the process for establishing a SAS connection to a Teradata database. After you verify the system requirements for the SAS/ACCESS engine, test the database connection using a LIBNAME statement: libname teralib teradata server=server-name user=user-ID pwd=password;

After you assign the LIBNAME statement, you can view your Teradata tables in the

TeraLib library either by viewing it from the SAS Explorer window or by submitting a

DATASETS procedure that is similar to the following: proc datasets lib=teralib; quit;

112

Chapter 4 / Connecting to Common Data Sources

Add the Teradata library using SAS Management Console Data Library Manager plugin.

1 In SAS Management Console, expand the Data Library Manager node.

2 Right-click Libraries and select New Library from the menu to open the New

Library wizard.

3 Under Database Data, select Teradata Library. Then click Next to continue to the next page of the wizard.

4 Enter a name for your library (for example, TeraLibrary) in the Name field. In the

Location field, select the folder (known as the metadata folder) in which to save this library.

Using a metadata folder to organize library and table objects in metadata (or any other metadata content that is supported by folders) is an efficient way to control access to those objects. Library and table objects inherit permissions from their respective metadata folders. Controlling access to these objects through permission inheritance is much easier when the objects are stored in the same metadata folder.

You control access to the libraries and tables by denying ReadMetadata permission to the folder in which the library and tables are stored.

For more details about metadata folders, see “Working with SAS Folders” in SAS

Intelligence Platform: System Administration Guide

5 Click Next to continue to the next page of the wizard.

6 Select the appropriate server from the Available servers list and move it to the

Selected servers list on the right. Note that even though the wizard states that this step is optional, you must select the server. For this example, use SASApp.

7 Click Next to continue to the next page of the wizard. In the Libref field, enter your libref (for example, TeraLib).

Establishing Connectivity to a Teradata Database

113

Table 4.13 Library Properties

Field

Libref

Engine

Sample Value

TeraLib

TERADATA

Click Next to move to the server and connection information page. Select the

Teradata server that you created.

Table 4.14 Server and Connection Information

Field

Database Server

Database Schema Name

Default Login

Sample Value

Teradata_server

(Use the database server that you created in the New Server wizard.)

See your database administrator for the correct value. This is optional.

Use the default value of

(None)

9 Click Next. Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

At this point, your library is defined. However, to access data, you either need to register the tables or pre-assign the library. See

information, see “Setting UNIX Environment Variables for SAS/ACCESS” on page

114

Chapter 4 / Connecting to Common Data Sources

Establishing Connectivity to an Oracle

Database

Overview of Establishing Connectivity to an

Oracle Database

The following figure provides a logical view of using Oracle as a data source.

Figure 4.10 Establishing Connectivity to an Oracle Database

SAS Data

Integration Studio

Workspace Server

SAS/ACCESS

Interface to Oracle

Oracle Client

Oracle Server

Client SAS Application Server Data Server

This example shows the process for establishing a SAS connection to an Oracle database. It assumes that the software for the database has already been loaded by using the standard installation wizard for the database client.

Prerequisites

The following prerequisites are necessary before you begin defining an Oracle library: n installation of SAS/ACCESS Interface to Oracle. For configuration information, see the Install Center at http://support.sas.com/documentation/installcenter/94 and use the operating system and SAS version to locate the appropriate SAS Foundation

Configuration Guide.

Establishing Connectivity to an Oracle Database

115 n installation of a supported Oracle Database Client.

n validation that the Oracle client can communicate with the Oracle server.

(UNIX only) configuration of SAS/ACCESS environmental variables. For more

To define a user or user group using SAS Management Console, see “Define the DBMS

Submit a LIBNAME statement, such as the following example: libname oralib oracle path=pathname user=user-name password="password" schema=database-schema-name;

Make sure you are able to see Oracle tables in the SAS Explorer window.

explained in “Registering and Verifying Tables” on page 171

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection from SAS to a database management system is a two-stage process.

1 Register the database server.

2 Register the database library.

Stage 1: Register the Oracle Server

To register the Oracle database server, perform the following steps:

1 Open SAS Management Console application.

2 Right-click Server Manager and select the New Server option to access the New

Server wizard.

3 Select Oracle Server from the Database Servers list. Then, click Next.

116

Chapter 4 / Connecting to Common Data Sources

4 Enter an appropriate server name in the Name field (for example,

oracle_server_on_alien). You can supply an optional description. Click Next.

The server properties that are displayed in the window are default values and should not be changed. To change the Associated Machine property, click the down arrow at the right of the field and select the appropriate server from the drop-down list.

Table 4.15 Server Properties

Field

Major Version Number

Minor Version Number

Software Version

Vendor

Associated Machine

Sample Value

Oracle Corporation

Defaults to your machine

Click Next.

6 Enter the following connection properties:

Table 4.16 Connection Properties

Field

Path

Authentication type

Sample Value

NEWSERVER10G

(This value is contained in the

tnsnames.ora

file generated during the Oracle installation. The file is stored in an Oracle installation directory such as

/opt/oracle/app/oracle/ product/10.2.0/db_1/network/admin/ tnsnames.ora

. The alias for the connection information is contained in this file. See the following figure.)

The default is

User/Password

. Select a value from the drop-down list.

Field

Authentication domain

Establishing Connectivity to an Oracle Database

117

Sample Value

OraAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register the Oracle Library

After you have registered the database server, register the database library. To register the Oracle database library, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

Select Oracle Library from the Database Data list. Click Next.

Enter an appropriate library name in the Name field (for example,

oracle_lib_on_alien). You can supply an optional description. Click Next.

Select a SAS server from the list and use the right arrow to assign the SAS server.

This step makes the library available to the server and makes the library visible to users of the server. This step is optional. Click Next.

Enter the following library properties:

Table 4.17 Library Properties

Field

Libref

Sample Value

ORAREF

118

Chapter 4 / Connecting to Common Data Sources

Field

Engine

Sample Value

ORACLE

You can also click Advanced Options to perform tasks such as pre-assignment and optimization. Click Next to access the next page of the wizard.

Enter the following settings:

Table 4.18 Server and Connection Information

Field

Database Server

Database Schema Name

Default Login

Sample Value oracle_server_on_alien

(Use the database server that you created in the New Server wizard.)

See your database administrator for the correct value.

Use the default value of

(None)

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings. At this point, register tables as

Establishing Connectivity to a Microsoft Access Database By Using ODBC

119

Establishing Connectivity to a Microsoft

Access Database By Using ODBC

Overview of Establishing Connectivity to a

Microsoft Access Database By Using ODBC

The following figure provides a logical view of using Microsoft Access as a data source and connecting to the database with a SAS/ACCESS ODBC interface.

Figure 4.11 Establishing Connectivity to Access Databases By Using ODBC

SAS Data

Integration Studio

Workspace Server

SAS/ACCESS

Interface to ODBC

ODBC Driver

Manager

ODBC Driver

Microsoft Access

Database

Database Tables

Client SAS Application Server Data Server

To define a user or user group using SAS Management Console, see “Define the DBMS

explained in “Registering and Verifying Tables” on page 171

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection from SAS to a Microsoft Access database by using ODBC is a three-stage process:

Define an ODBC data source.

120

Chapter 4 / Connecting to Common Data Sources

2 Register the database server.

3 Register the database library.

This example shows the process for establishing a SAS connection to an Access database. It assumes that the software for the database has already been loaded with the standard installation wizard for the database client. In addition, SAS/ACCESS

Interface to ODBC must be installed on the SAS server that accesses the Access database.

Stage 1: Define the ODBC Data Source

First, you must define the ODBC data source. To define the ODBC data source on

Windows systems, perform the following steps:

1 Open the Windows Control Panel. Click Systems and Security  Administrative

Tools



Data Sources (ODBC) to access the ODBC Data Source Administrator dialog box.

Click Add to access the Create New Data Source dialog box. Click the Microsoft

Access driver listed in the window (for example, Microsoft Access Driver [*.mdb]).

Click Finish to access the ODBC Microsoft Access Setup dialog box.

Note:

System data sources and user data sources store information about how to connect to the indicated data provider. A system data source is visible to all users with access to the system, including Windows services. A user data source is visible only to a particular user, and it can be used on the current machine only.

Enter the following configuration settings:

Table 4.19 Configuration Settings

Field

Data Source Name

Sample Value

MS Access

Field

Database

Establishing Connectivity to a Microsoft Access Database By Using ODBC

121

Sample Value

Click Select to browse for your Access database file, such as

Northwinds.mdb

in the Microsoft Office

Samples directory.

Click OK to save the configuration settings and return to the ODBC Data Source

Administrator dialog box. Then, click OK to save the data source.

Stage 2: Register the ODBC Server

To register the database server, perform the following steps:

Open the SAS Management Console application.

Right-click Server Manager and select the New Server option to access the New

Server wizard.

Select ODBC Server from the Database Servers list. Click Next.

Enter an appropriate server name in the Name field (for example, MS Access

Server). One server is required for each DSN. Note that you can supply an optional description if you want. Click Next.

5 Enter the following server properties:

Table 4.20 Server Properties

Field

Major Version Number

Minor Version Number

Data Source Type

Software Version

Sample Value

ODBC - Microsoft Access

3.7.0

122

Chapter 4 / Connecting to Common Data Sources

Field

Vendor

Associated Machine

Sample Value

Microsoft newserver.na.sas.com

This is the server where the database is running. (Select this value from the drop-down list. If the value that you need is not available, click New to access the New Machine dialog box. Then enter the appropriate value in the

Host Name field.)

Click Next.

Enter the following connection properties:

Table 4.21 Connection Properties

Field

Datasrc

Authentication type

Authentication domain

Sample Value

MS Access

(Use the value entered in the Data

Source Name field in the ODBC Data Source

Administrator dialog box.)

User/Password

ODBCAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Establishing Connectivity to a Microsoft Access Database By Using ODBC

123

Stage 3: Register the ODBC Library

After you have registered the database server, you can register the database library. To register the database library, perform the following steps:

1 In SAS Management Console, expand Data Library Manager. Then, right-click

Libraries and select the New Library option to access the New Library wizard.

2 Select ODBC Library from the Database Data list. Click Next.

3 Enter an appropriate library name in the Name field (for example, MS Access

Library). Note that you can supply an optional description if you want. Click Next.

Select an application server from the list and use the right arrow to assign the application server. Click Next.

Enter the following library properties:

Table 4.22 Library Properties

Field

Libref

Engine

Sample Value

ACCESREF

ODBC

You can also click Advanced Options to perform tasks such as pre-assignment and optimization. Click Next to access the next page of the wizard.

6 Enter the following settings:

Table 4.23 Server and Connection Information

Field

Database Server

Sample Value

MS Access Server

(Use the database server that you created in the New Server wizard.)

124

Chapter 4 / Connecting to Common Data Sources

Click Next.

7 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings. At this point, register tables as

Establishing Connectivity to a SAS

Federation Server

Overview of Establishing Connectivity to a

SAS Federation Server

The following figure provides a logical view of connecting to a SAS Federation Server and accessing tables from multiple data sources registered there, using a federated

DSN that contains multiple data source names.

Figure 4.12 Establishing Connectivity to a SAS Federation Server

SAS Data

Integration Studio

Workspace Server

FEDSVR Engine

SAS Federation

Server

DSN

Data Sources

Client SAS Application Server Data Server

To define a user or user group using SAS Management Console, see “Define the DBMS

explained in “Registering and Verifying Tables” on page 171

Establishing Connectivity to a SAS Federation Server

125

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

After defining a user or user group, setting up a connection from a SAS session to a

SAS Federation Server is a two-stage process:

1 Register the SAS Federation Server.

2 Register the SAS Federation Server library.

If you do not know the DSN or connection string to use for accessing the data, then contact the server administrator for that information.

Stage 1: Register the SAS Federation Server

To register the SAS Federation Server, perform the following steps:

1 Open the SAS Management Console application.

2 Right-click Server Manager and select the New Server option to access the New

Server wizard.

3 Select SAS Federation Server from the SAS Servers list. Click Next.

4 Enter an appropriate server name in the Name field (for example, Federation

Server). Note that you can supply an optional description if you want. Click Next.

Enter the following server properties:

Table 4.24 Server Properties

Field

Major Version Number

Minor Version Number

Software Version

Vendor

Sample Value

3.2

SAS Institute

126

Chapter 4 / Connecting to Common Data Sources

Click Next.

6 Leave the connection type set to SAS Connection.

Click Next.

Enter the following connection properties:

Table 4.25 Connection Properties

Field

Port number

Host name

Authentication type

Authentication domain

Sample Value

21032

Specify the host name for the SAS Federation

Server.

User/Password

DFAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register the SAS Federation Server

Library

After you have registered the SAS Federation Server, you can register the SAS

Federation Server library.

Establishing Connectivity to a SAS Federation Server

127

To register the library, perform the following steps:

1 In SAS Management Console, expand Data Library Manager. Then, right-click

Libraries and select the New Library option to access the New Library wizard.

2 Select SAS Federation Server Library from the SAS Data list. Click Next.

3 Enter an appropriate library name in the Name field (for example, Federated Data

Library). Click Browse and select a metadata folder location for the library. Note that you can supply an optional description if you want.

Click Next.

Select an application server from the list and use the right arrow to assign the application server.

Click Next.

Enter the following library properties:

Table 4.26 Library Properties

Field

Libref

Sample Value

FEDREF

Engine FEDSVR

Identify Connection Information Select the radio button for Data Source Name and specify the DSN.

If you prefer to specify a connection string, then select the radio button for Connection String. For information about SAS Federation Server connection strings, see SAS Federation Server: Administrator's

Guide.

You can also click Advanced Options to perform tasks such as pre-assignment and optimization. Click Next to access the next page of the wizard.

6 Enter the following settings:

128

Chapter 4 / Connecting to Common Data Sources

Table 4.27 Server and Connection Information

Field

Database Server

Database Schema Name

Connection

Default Login

Sample Value

Federation Server

(Use the server that you created in the New Server wizard.)

See your administrator for the correct value.

Use the default value of Connection: server_name.

Use the default value of

(None)

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings. At this point, register tables as

Special Considerations for SAS Federation

Server Libraries

A federated DSN can be configured with several schemas so that data from several data sources can be federated under a single DSN. However, when you register tables for a library that uses a federated DSN, you can register the tables from the first schema only.

For more information about how the LIBNAME engine for SAS Federation Server supports access to one data source at a time, see “Data Source Connection” in SAS

LIBNAME Engine for SAS Federation Server: User's Guide

Establishing Connectivity to a SAS Scalable Performance Data Server

129

Establishing Connectivity to a SAS

Scalable Performance Data Server

Overview of Establishing Connectivity to a

SAS Scalable Performance Data Server

The following figure provides a logical view of using SAS Scalable Performance Data

(SPD) Server tables as a data source.

Figure 4.13 Establishing Connectivity to an SPD Server

SAS Data

Integration Studio

Workspace Server

SPDS Engine

SAS Scalable

Performance Data

Server

Client SAS Application Server

SPDS Tables

Data Server

To define a user or user group using SAS Management Console, see “Define the DBMS

At this point, register tables as explained in “Registering and Verifying Tables” on page

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

After defining a user or user group, configuring a connection from SAS to an SPD

Server is a three-stage process:

1 Configure the libnames.parm file.

130

Chapter 4 / Connecting to Common Data Sources

3 Register the SPD Server library.

This example shows the process for establishing a SAS connection to SPD Server. It assumes that the software for the database has already been loaded by using the standard installation wizard for the database client. The SPD Server client and server software must be installed before the connection can be established.

Stage 1: Configure the libnames.parm File

When you install the SPD Server software on Windows, a libnames.parm file is created in the C:\Program Files\SAS Institute Inc\SPDS-version\Site directory. You must specify at least a LIBNAME and a pathname for the directory to use for the SPD

Server tables (for example, C:\SPDSTables). For the LIBNAME, use the LIBNAME domain that you created earlier for the library (in this case, spdsrv).

A sample libnames.parm file is shown in the following figure:

Stage 2: Register the SAS Scalable

Performance Data Server

To register the database server, perform the following steps:

1 Open the SAS Management Console application.

Establishing Connectivity to a SAS Scalable Performance Data Server

131

2 Right-click Server Manager and select the New Server option to access the New

Server wizard.

3 Select SAS Scalable Performance Data Server from the SAS Servers list. Then, click Next.

4 Enter an appropriate server name in the Name field (for example, SPDServer). You can supply an optional description. Click Next.

Enter the following server properties:

Table 4.28 Server Properties

Field

Major Version Number

Minor Version Number

Vendor

SAS Compatibility

Sample Value

SAS Institute

SAS 9

Click Next.

Enter the following connection properties:

Table 4.29 Connection Properties

Field

Host

Port Number or Name

Communication Protocol

Sample Value

D1234

5200

(Enter the port number for the SPD Server name server.)

TCP

132

Chapter 4 / Connecting to Common Data Sources

Field

Authentication Domain

Sample Value

SPDSAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 3: Register the SAS Scalable

Performance Data Server Library

After you have registered the server, you can register the library. To register the library, perform the following steps:

1 In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

2 Select SAS Scalable Performance Data Server Library from the SAS Data list.

Click Next.

3 Enter an appropriate library name in the Name field (for example,

SPDServerLibrary). You can supply an optional description. Click Next.

Select a SAS server from the list and use the right arrow to assign the SAS server.

This step makes the library available to the server and makes the library visible to users of the server. Click Next.

Enter the following library properties:

Establishing Connectivity to a SAS Scalable Performance Data Server

133

Table 4.30 Library Properties

Field

Libref

Engine

Sample Value spdsrv

SASSPDS

You can also click Advanced Options to perform tasks such as pre-assignment and optimization. Click Next to access the next page of the wizard.

Enter the following settings:

Table 4.31 Server and Connection Information

Field

SAS SPD Server

LIBNAME Domain

Default Login

Sample Value

SPDSServer

(Use the database server that you selected in the New Server wizard.)

spdsrv

(Select the domain name that you entered in the

libname.parms

file.)

(None)

(Keep this default value.)

Click Next.

7 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings.

To define a user or user group using SAS Management Console, see “Define the DBMS

134

Chapter 4 / Connecting to Common Data Sources

Establishing Connectivity to an SAP

Server

Overview to Establishing Connectivity to an

SAP Server

The following figure provides a logical view of connecting to an SAP Server as a data source.

Figure 4.14 Establishing Connectivity to an SAP Server

SAS Data

Integration Studio

SAS Data

Surveyor for SAP

Workspace Server

SAS/ACCESS

Interface to R/3

SAP Application

Server

Client SAS Application Server

SAP Data Tables

Data Server

To define a user or user group using SAS Management Console, see “Define the DBMS

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection from SAS to an SAP server is a three-stage process:

1 Register the server.

2 Register the library.

3 Extract SAP metadata, if SAS Data Surveyor for SAP is installed.

Establishing Connectivity to an SAP Server

135

This example shows the process for establishing a SAS connection to SAP. It assumes that the following software has already been loaded by using the standard installation wizard: n

SAP RFC library. This is required for communication with SAP.

SAS/ACCESS Interface to R/3. For z/OS hosts, this installs the SAS RFC server.

For these z/OS hosts, this server must be started each time you start the SAS servers such as the Object Spawner.

Stage 1: Register the SAP Server

To register the SAP server, perform the following steps:

1 Open the SAS Management Console application.

2 Right-click Server Manager and select the New Server option to access the New

Server wizard.

3 Select SAP Server from the Enterprise Applications Servers list. Then, click Next.

4 Enter an appropriate server name in the Name field (for example, SAPServer). Note that you can supply an optional description if you want. Click Next.

Enter the following server properties. An SAP 4.6 installation is used as the example:

Table 4.32 Server Properties

Field

Major Version Number

Minor Version Number

Software Version

Vendor

Sample Value

4.6

SAP AG

136

Chapter 4 / Connecting to Common Data Sources

Click Next.

6 Enter the following connection properties:

Table 4.33 Connection Properties

Field

Authentication Domain

Client

Language

Sample Value

SAPAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

800

(This value is obtained from your SAP administrator.)

Note:

An embedded RFC server is not available for z/OS. For z/OS, click the

Advanced Options button and enter “host=rfc-server port=rfc-port” in the Other

option(s) to be appended text field. Also, select the Batch Mode check box.

Select Application Server and click Options to access the Application Server Host dialog box.

TIP Instead of the application server, you might choose other options, as well, including: SAPGUI Logical Name, SAPRFC.INI Logical Name, and Message

Servers

Enter the fully qualified name of the server host that was supplied by the SAP administrator (for example, sapsrv.na.sas.com) in the Application Server Host field. Enter the system number that was supplied by the SAP administrator (for example, 12) in the System Number field. The default access mode is direct access. In order to run in batch mode, click the Advanced Options tab. Select the

Batch Mode check box. In the Other options field, enter a value for destgroup

Establishing Connectivity to an SAP Server

137 such as destgroup="SDSTEST". For batch mode on z/OS, follow the instructions in

Installation Instructions for SAS/ACCESS Interface to R/3 Software. Then, click OK to return to the New Server wizard.

9 Click Next.

10 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register the SAP Library

After you have registered the server, you can register the library. To register the library, perform the following steps:

1 In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

2 Select SAP Library from the Enterprise Applications Data list. Click Next.

3 Enter an appropriate library name in the Name field (for example, SAP Library).

You can supply an optional description. Click Next.

Select an application server from the list and use the right arrow to assign the application server. This step makes the library available to the server and makes the library visible to users of the server. Click Next.

Enter the following library properties:

Table 4.34 Library Properties

Field

Libref

Engine

Sample Value

SAPLib

SASIOSR3

(Accept the value that is populated automatically.)

Click Next.

138

Chapter 4 / Connecting to Common Data Sources

6 Select the SAP server that you entered in the Name field of the New Server wizard

(for example, SAP Server) by using the Database Server drop-down list. Then, click

Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings.

Stage 3: Extract SAP Metadata

If SAS Data Surveyor for SAP is installed, then you can extract metadata about your

SAP objects to SAS data sets. Once you have created the SAS data sets, the tables in your SAP System are available for use in jobs with clients like SAS Data Integration

Studio and SAS Enterprise Guide.

The tools for extracting the SAP metadata are provided as a plug-in to SAS

Management Console and access to the tool is controlled with role-based access. To enable the extraction tool for role-based access and to extract the SAP metadata, perform the following steps:

Using an unrestricted account such as sasadm@saspw, select Tools



Plug-in

Manager From the SAS Management Console.

On the Plug-in Manager window, select the ExtractionTool check box. Click OK.

3 Assign the ExtractionTool capability to a role with the User Manager plug-in to SAS

Management Console, and then associate users or groups with the role. The following list provides two choices: n

Assign the ExtractionTool capability to an existing role such as Management

Console: Advanced.

Create a new role, assign the ExtractTool capability to it, and then associate users and groups with the new role.

For more information about roles, see “Change a Role's Capabilities” in SAS

Management Console: Guide to Users and Permissions

Establishing Connectivity to an SAP HANA Server

139

4 Important: Log on to SAS Management Console with an account that has access to the Foundation repository and that is not an unrestricted account.

5 Select Tools  Extract from BW or Tools  Extract from R/3. For information about using the tools, click Help.

Special Considerations for SAP

For z/OS operating environments, when you specify the language value on the New

Server wizard, use uppercase letters and enclose the value in quotation marks (for example, “EN”).

Establishing Connectivity to an SAP

HANA Server

Overview to Establishing Connectivity to an

SAP HANA Server

The following figure provides a logical view of connecting to an SAP HANA Server as a data source.

140

Chapter 4 / Connecting to Common Data Sources

Figure 4.15 Establishing Connectivity to an SAP HANA Server

SAS Data

Integration Studio

Workspace Server

SAS/ACCESS

Interface to

SAP HANA

ODBC Driver

Manager

ODBC Driver for SAP HANA

SAS Application Server

SAP HANA

Server

Database Tables

Client Data Server

To define a database library in SAS Management Console with the SAS/ACCESS software, you need SAS/ACCESS Interface to SAP HANA software installed on your

SAS server. After you verify the system requirements for the SAS/ACCESS Interface to

SAP HANA , test the database connection using a LIBNAME statement: libname A1 sasiohna server=server-name port=number user=user-id password=password;

This example does not specify a DSN style. SERVER=, DATABASE=, USER=, and

PASSWORD= are connection options. This is the default method, which is recommended.

libname A1 sasiohna server=mysrv1 port=30015 user=myusr1 password='mypwd1';

This example requires that you specify a DSN style.

libname B1 sasiohna dsn=hnatest user=myusr1 password=mypwd1;

After you assign the LIBNAME statement, you can view your SAP HANA tables in the

A1 library either by viewing it from the SAS Explorer window or by submitting a

DATASETS procedure that is similar to the following: proc datasets lib=A1; quit;

Server Information, then click Options. See Server

Establishing Connectivity to an SAP HANA Server

141

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection from SAS to an SAP HANA server is a two-stage process:

1 Register the server.

2 Register the library.

This example shows the process for establishing a SAS connection to an SAP HANA data source. It assumes that SAS/ACCESS Interface to SAP HANA software has already been installed.

Stage 1: Register the SAP HANA Server

To register the SAP HANA server, perform the following steps:

1 Open SAS Management Console application.

2 Right-click Server Manager and select the New Server option to access the New

Server wizard.

3 Select SAP HANA Server from the Database Servers list. Then, click Next.

4 Click Next. Select the appropriate server from the Available servers list and move it to the Selected servers list. For this example, use SASApp.

5 Enter the following server properties. An SAPHANA 1.0 installation is used as the example:

Table 4.35 Server Properties

Field

Major Version Number

Minor Version Number

Software Version

Sample Value

1.0

142

Chapter 4 / Connecting to Common Data Sources

Field

Vendor

Associated Machine

Sample Value

SAP AG

Defaults to your machine, Click New to specify a different machine.

Click Next.

Enter the following connection properties:

Table 4.36 Connection Properties

Field

Server Information

ODBC Datasource

Connection String

Authentication Type

Authentication Domain

Sample Value

You are required to select at least one field. Enter the appropriate information if you choose ODBC

Datasource or Connection String. If you choose

Information Options on page 143 .

Enter the connection information for your SAP HANA instance. There are several ways of specifying the connection information. In the Server information window, you can specify server and port, or the server and instance information. Or you can enter the

ODBC data source, or a connection string. Click OK.

The default is

User/Password

. Select a value from the drop-down list.

DefaultAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Establishing Connectivity to an SAP HANA Server

143

Enter mysvr1 in the Server field. The Driver field is optional. Click OK.

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register the SAP HANA Library

After you have registered the server, you can register the library.

To register the library, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

Select SAP HANA Library from the Database Data list. Click Next.

Enter an appropriate library name in the Name field (for example, SAP HANA

Library). You can supply an optional description. Click Next.

144

Chapter 4 / Connecting to Common Data Sources

5 Enter the following library properties:

Table 4.37 Library Properties

Field

Libref

Engine

Sample Value

SHLibref

SASIOHNA

(Accept the value that is populated automatically.)

Click Next.

Select the SAP HANA server that you entered in the Name field of the New Server wizard (for example, SAS HANA Server) by using the Database Server drop-down list. Then, click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings.

Establishing Connectivity to an Impala

Server

Overview of Establishing Connectivity to

Impala

The following figure provides a logical view of using the SAS/ACCESS Interface to

Impala.

Establishing Connectivity to an Impala Server

145

SAS Data

Integration Studio

Workspace Server

SAS/ACCESS

Interface to Impala

Impala Client

Impala Server

Client SAS Application Server Data Server

To define a user or user group using SAS Management Console, see “Define the DBMS

To define a user or user group using SAS Management Console, see “Define the DBMS

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection from SAS to an Impala Server is a two-stage process:

Stage 1: Register the Impala Server

To register the Impala server, perform the following steps:

Open SAS Management Console application.

Right-click Server Manager and select the New Server option to access the New

Server wizard.

Select Impala Server from the Database Servers list. Then, click Next.

Specify a name for the new Impala server. The Description is optional.

146

Chapter 4 / Connecting to Common Data Sources

5 Enter the following server properties. An Impala 1.0 installation is used as the example:

Table 4.38 Server Properties

Field

Major Version Number

Minor Version Number

Software Version

Vendor

Associated Machine

Sample Value

1.0

Cloudera Inc.

Defaults to your machine, Click New to specify a different machine.

Click Next.

On this page, enter the connection properties. Click the Server Information button.

Click Options. For this example, enter the following connection properties:

Click OK.

Table 4.39 Connection Properties

Field

Server Information:

ODBC datasource Information:

Sample Value

Field

Authentication Type

Authentication Domain

Establishing Connectivity to an Impala Server

147

Sample Value

The default is

User/Password

. Select a value from the drop-down list.

DefaultAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register the Impala Library

After you have registered the server, you can register the library. To register the library, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

Select Impala Library from the Database Data list. Click Next.

Enter an appropriate library name in the Name field (for example, Impala Library).

You can supply an optional description. Enter the Location if different from the default. Click Next.

Enter the following library properties:

148

Chapter 4 / Connecting to Common Data Sources

Table 4.40 Library Properties

Field

Libref

Engine

Sample Value

ImpLib

SASIOIMP

(Accept the value that is populated automatically.)

Click Next.

Select the Impala server that you entered in the Database Server field of the New

Server wizard (for example, ImpalaServer) by using the Database Server dropdown list. Then, click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings.

Establishing Connectivity to Hadoop

Overview of Establishing Connectivity to

Hadoop

The following figure provides a logical view of using the SAS/ACCESS Interface to

Hadoop to access a Hive Server. The Hive Server is shown running on the same machine as the Hadoop NameNode.

Figure 4.16 Establishing Connectivity to Hadoop Servers

Establishing Connectivity to Hadoop

149

SAS Data

Integration Studio

Workspace Server

SAS/ACCESS

Interface to Hadoop

Hadoop JAR Files

HiveServer2

Tables

Client SAS Application Server Hadoop NameNode

The example shows the process for establishing a SAS connection to a Hive Server. In order for the SAS/ACCESS interface to connect with the Hive Server, the machine that is used for the SAS Workspace Server must be configured with several JAR files. These

JAR files are used to make a JDBC connection to the Hive Server. The following prerequisites have been satisfied: n installation of SAS/ACCESS Interface to Hadoop. For more information, see the configuration guide for your operating system and SAS version at http:// support.sas.com/documentation/installcenter/94 .

n installation of the Hadoop JAR files required by SAS. For more information, see the

“Hadoop JAR Files” in SAS Hadoop Configuration Guide for Base SAS and SAS/

ACCESS or the configuration guide for your operating system and SAS version at http://support.sas.com/documentation/installcenter/94 .

n setting the SAS_HADOOP_JAR_PATH environment variable. See the “SAS

Environment Variables for Hadoop” appendix in SAS Hadoop Configuration Guide for Base SAS and SAS/ACCESS .

explained in “Registering and Verifying Tables” on page 171

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

150

Chapter 4 / Connecting to Common Data Sources

Setting up a connection from SAS to a Hadoop Server is a two-stage process:

1 Register the Hadoop Server.

2 Register the Hadoop via Hive library.

This section describes the steps that are used to access data in Hadoop as tables through a Hive Server. SAS Data Integration Studio offers a series of transformations that can be used to access the Hadoop Distributed File System (HDFS), submit Pig code, and submit MapReduce jobs.

Hadoop Configuration Resources

Starting in the second maintenance release of SAS 9.4, a new support site for Hadoop has been added to the SAS Third-Party Software Reference site: http://support.sas.com/resources/thirdpartysupport/v94/hadoop/ . This site includes a new guide, SAS Hadoop Configuration Guide for Base SAS and SAS/ACCESS , which covers pre-installation and post-installation information for a number of SAS components that access Hadoop. The guide lists vendor-specific Hadoop JAR files and describes SAS environment variables for Hadoop. This site also lists additional resources for Hadoop support.

Stage 1: Register the Hadoop Server

To register the Hadoop Server, perform the following steps:

1 Open SAS Management Console application.

2 Right-click Server Manager and select the New Server option to access the New

Server wizard.

3 Select Hadoop Server from the Cloud Servers list. Then, click Next.

4 Enter an appropriate server name in the Name field (for example, HadoopServer).

You can supply an optional description. Click Next.

Establishing Connectivity to Hadoop

151

5 In the second quarter of 2015, an Encryption Options section was added to SAS

Management Console.

Enter the following server properties:

Table 4.41 Server Properties

Field

Major Version Number

Minor Version Number

Software Version

Vendor

Associated Machine

Enable Encryption

New Encrypt Key:

Confirm Encrypt Key:

Sample Value

5.3

Cloudera

Select the host name for the HiveService node from the menu.

Yes or No. Specifies whether to enable AES encryption for the libraries on the server.

Note:

Enabling encryption does not affect existing non-encrypted tables. Move any non-encrypted tables to a backup location before enabling encryption on an existing server definition. After you enable encryption, move the table back to the server.

The table will be encrypted as they are written to the server.

If you enabled encryption, specify the encryption key.

Confirm the encryption key.

152

Chapter 4 / Connecting to Common Data Sources

Click Next.

Enter the following connection properties:

Table 4.42 Connection Properties

Field

HiveService Node

Port Number

Sample Value

Specify the host name of the machine that is running the HiveServer2. For this example, use

hdp21d1

Specify the network port number for the Hive Service.

For this example, use the default

10000

Field

Environment Install Location

LASR Authorization Service

Authentication type

Authentication domain

Configuration

NameNode HTTP Address

Secondary NameNode HTTP

Address

Job Tracker HTTP Address

Establishing Connectivity to Hadoop

153

Sample Value

/opt/TKGrid

(For deployments that use SAS Visual

Analytics with Hadoop, specify the path to

TKGrid

on the machines in the cluster.)

Choose whether to select the Use LASR

authorization service check box. If you select this check box, you must also specify the location of the authorization service. This option applies only to

SASHDAT libraries that use this server. This check box is automatically selected and cannot be cleared if you enabled on-disk AES encryption for libraries on this server.

Use the default value of

(none)

for this example.

DefaultAuth

(You might need to create a new authentication domain. For more information, see

“How to Store Passwords for a Third-Party Server” in

SAS Intelligence Platform: Security Administration

Guide

.) Click New to access the New Authentication

Domain dialog box. Then enter the appropriate value in the Name field and click OK to save the setting.

For this example, use the default.

154

Chapter 4 / Connecting to Common Data Sources

Click Next. Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register the Hadoop via Hive

Library

After you have registered the Hadoop Server, register the library. To register the

Hadoop via Hive Library, perform the following steps:

In SAS Management Console, expand Data Library Manager. Right-click Libraries.

Then, select the New Library option to access the New Library wizard.

Establishing Connectivity to Hadoop

155

2 Select Hadoop via Hive Library from the Database Data list. Click Next.

3 Enter an appropriate library name in the Name field (for example, Hive Library).

You can supply an optional description. Click Next.

Select a SAS server from the list and use the right arrow to assign the SAS server.

This step makes the library available to the server and makes the library visible to users of the server. Click Next.

Enter the following library properties:

Table 4.43 Library Properties

Field

Libref

Engine

Sample Value

HIVEREF

HADOOP

Click Advanced Options. Then, click the Connection tab.

Enter the following library properties:

Table 4.44 Library Properties

Field

Hive Service

Hive Properties

Hive Kerberos Principal

Sample Value

For this example, use the default

HIVE2

Leave blank for this example.

For this example, use

hive/

[email protected]

. See the following figure.

156

Chapter 4 / Connecting to Common Data Sources

Click OK. Click Next to access the next page of the wizard.

Enter the following settings:

Table 4.45 Server and Connection Information

Field

Database Server

Database Schema Name

Connection

Default Login

Sample Value

HadoopServer

(Use the Hadoop Server that you created in the New Server wizard.)

See your Hadoop administrator for the correct value.

Use the default value of Connection: server_name.

Use the default value of

(None)

Establishing Connectivity to a SAS LASR Analytic Server

157

Click Next.

10 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the library settings. At this point, register tables as

Special Considerations for Hadoop via Hive

Tables

Hadoop via Hive tables can be registered in metadata with clients such as SAS

Management Console and SAS Data Integration Studio. However, table metadata cannot be updated after the table is registered in metadata.

Establishing Connectivity to a SAS

LASR Analytic Server

Overview of Establishing Connectivity to a

SAS LASR Analytic Server

The following figure provides a logical view of connecting to a SAS LASR Analytic

Server as a data source.

158

Chapter 4 / Connecting to Common Data Sources

Figure 4.17 Establishing Connectivity to a SAS LASR Analytic Server

SAS Data

Integration Studio

Workspace Server

SAS LASR Analytic

Server Engine

SAS LASR

Analytic Server

In-Memory Tables

Client SAS Application Server Data Server

To define a user or user group using SAS Management Console, see “Define the DBMS

instructions, see “Stage 1: Register a SAS LASR Analytic Server Using SAS

To define a user or user group using SAS Environment Manager, see “Managing User

Access” in SAS Environment Manager Administration: User's Guide.

Setting up a connection to a SAS LASR Analytic Server is a two-stage process that can be accomplished in SAS Management Console or SAS Environment Manager:

1 Register the SAS LASR Analytic Server.

2 Register the SAS LASR Analytic library.

Note:

If you are creating these objects for use in SAS Visual Analytics, see the SAS

Visual Analytics: Administration Guide.

Note:

Beginning in the third maintenance release for SAS 9.4, if SAS Visual Analytics is part of your deployment, you can create and maintain SAS LASR Analytic Servers and SAS LASR Analytic Server libraries using the SAS Environment Manager. For

Environment Manager” on page 162

and “Stage 2: Register a SAS LASR Analytic

Server Library Using SAS Environment Manager” on page 165

Establishing Connectivity to a SAS LASR Analytic Server

159

Stage 1: Register a SAS LASR Analytic

Server Using SAS Management Console

On the Plug-ins tab in SAS Management Console, expand Environment

Management. Right-click Server Manager, and select New Server.

In the New Server wizard, select SAS Servers  SAS LASR Analytic Server. Click

Next.

Enter a name for the server. Click Next.

Enter the following server properties:

Table 4.46 Server Properties

Field

Single machine server

Sample Value

For a distributed server, select No.

For a non-distributed server, select Yes.

High-Performance

Analytics environment install location

Specify the host path where files that define the cluster are located

(for example,

/opt/TKGrid

). This field is applicable to a distributed server only.

Number of machines to use

Accept the default value (

ALL

). This field is applicable to a distributed server only.

Click the Advanced Options button.

In the Advanced Options window, click the Additional Options tab. Make sure that

Signature files location on server field references a directory that has appropriate host protection.

When you are finished setting advanced options, click OK in the Advanced Options window. In the wizard, click Next.

Enter the following connection properties:

160

Chapter 4 / Connecting to Common Data Sources

Table 4.47 Connection Properties

Field

Port number

Sample Value

Enter a unique port number.

High-Performance

Analytics environment host

Enter the fully qualified machine name of the host (for example,

va.abc.com

Use LASR authorization service

Leave this check box selected.

Click Next.

If you want to add explicit grants of the Administer permission on the server, then move identities from one list to the other. Click Next.

Note:

Only users who have the Administer permission for the server can stop the server. The server inherits settings from the repository ACT (default ACT), so it might not always be essential to add explicit grants.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 2: Register a SAS LASR Analytic

Server Library Using SAS Management

Console

To register a SAS LASR Analytic Server library, perform the following steps:

On the Plug-ins tab in SAS Management Console, expand Data Library Manager.

Right-click Libraries, and select New Library.

In the New Library wizard, select High-Performance Analytics  SAS LASR

Analytic Server Library. Click Next.

Establishing Connectivity to a SAS LASR Analytic Server

161

3 Enter a name (for example, Sales LASR). If necessary, adjust the location. Click

Next.

(Optional) Assign the library to one or more SAS Application Servers. Click Next.

Enter the following library properties:

Table 4.48 Library Properties

Field

Libref

Engine

Server tag

Data Provider

Library

Sample Value

Enter an identifier of your choice (for example,

SALESLIB

This field is not editable. The value

SASIOLA

is the engine name for a

SAS LASR Analytic Server Library.

If the data for the SAS LASR Analytic Server Library is from co-located

HDFS or NFS-mounted MapR, the server tag must be the source path in dot-delimited format.

Note:

Each server tag must be unique.

Use the default value (None).

Click Next.

Assign the library to a SAS LASR Analytic Server by entering the following settings:

Table 4.49 Connection Properties

Field

Database

Server

Connection

Sample Value

Select a server from the drop-down list.

Default Login

Use the pre-selected value (which prepends the selected server name with the string

Connection:)

This field is not editable. The value is (None) .

162

Chapter 4 / Connecting to Common Data Sources

8 Click Next.

9 If you want explicit grants of the Administer permission on the library, move identities from one list to the other. Click Next.

Note:

Only users who have the Administer permission for the library can load new tables to memory. The library inherits settings from its parent folder, so it might not be essential to add any explicit grants.

10 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Stage 1: Register a SAS LASR Analytic

Server Using SAS Environment Manager

To create a new server definition in metadata, perform the following steps:

Click the Administration tab.

Click the Side Menu icon in the upper left corner of the window.

Click Servers.

In the Servers module, click the New Server icon to display the New Server window.

Specify the appropriate information in the New Server window. The window contains only the minimum fields required to define the server. When you select the server type, the Options section of the window automatically expands to display any required options for the selected server type.

Table 4.50 Server Properties

Field

Name

Sample Value

Name the server (for example, LASRServer).

Establishing Connectivity to a SAS LASR Analytic Server

163

Field

High-Performance

Analytics Host

Sample Value

Enter the host pathname (for example, va.abc.com

Port Number

Enter a unique port number (for example, 20150).

High-Performance

Analytics Install

Location

Associated

Machine

Enter the install location pathname (for example, /opt/TKGrid ).

Enter the machine name (for example, bluefin

Click OK.

The following screen appears:

164

Chapter 4 / Connecting to Common Data Sources

Click Basic Properties to specify options.

7 The following screen appears:

Establishing Connectivity to a SAS LASR Analytic Server

165

Click Options. For a distributed server, select No. For a non-distributed server, select Yes. Click the Save icon .

Note:

Only users who have the Administer permission for the server can stop the server or set its tables limit. The server inherits settings from the repository ACT

(default ACT), so it might not always be essential to add explicit grants.

Enter the Description. Click the Save icon to save the new server.

Note:

When a SAS LASR Analytic Server is created using the SAS Environment

Manager, the Visual Analytics Data Administrators group is NOT added by default.

To add the group, you must perform the following steps: a

Click the Basic Properties drop-down arrow.

Click Authorization.

Click the Add Identities icon .

Enter Visual Analytics Data Administrators and click the Search icon .

Move this group to the right using the Add arrow icon . Click OK.

Note that the Administer has a Deny icon . Click the Deny icon and click

Grant.

To save the properties, click the Save icon .

Stage 2: Register a SAS LASR Analytic

Server Library Using SAS Environment

Manager

To register a SAS LASR Analytic Server library, perform the following steps:

Click the Administration tab.

Click the Side Menu icon in the upper left corner of the window.

166

Chapter 4 / Connecting to Common Data Sources

3 Click Libraries.

4 Click the New Library icon .

5 Enter a library Name (for example, Sales LASR). If necessary, change the Location.

Click SAS LASR Analytic Server Library. The Options dialog box appears.

In the Options dialog box, enter the Libref.

Field

Libref

Engine

Sample Value

Enter an identifier of your choice (for example,

SalesLib

This field is not editable. The value

SASIOLA

is the engine name for a

SAS LASR Analytic Server Librarys.

Close Options.

7 Open Data Server if it is closed.

Field

Database server

Sample Value

Enter the Database server. If the LASR library’s data is loaded from co-located HDFS or NFS-mounted MapR, the server tag must be the source path in dot-delimited format.

Note:

Each server tag must be unique.

Close Data Server.

Click OK.

Examine the page to ensure that the proper values have been entered. Review and adjust permissions as needed. Enter the description. Click the Save icon to save the new library.

Establishing Connectivity to a SASHDAT Library

167

Special Considerations for SAS LASR

Analytic Server

If your deployment includes SAS Visual Analytics, there are additional features that you might want to configure. See SAS Visual Analytics: Administration Guide for more information.

For details about working with the server, see SAS LASR Analytic Server: Reference

Guide.

For non-distributed servers, log files are written to the directory specified in the

Signature files location on server field, if logging is enabled. The path on the

Logging Options tab is ignored by non-distributed servers.

Establishing Connectivity to a SASHDAT

Library

Overview of Establishing Connectivity to a

SASHDAT Library

The following figure provides a logical view of connecting to a SASHDAT library

(sometimes referred to as SAS Data in HDFS library).

168

Chapter 4 / Connecting to Common Data Sources

Figure 4.18 Establishing Connectivity to an HDFS Library

SAS Data

Integration Studio

Workspace Server

SASHDAT Engine Hadoop Server

SASHDAT Tables

Client SAS Application Server Hadoop NameNode

This library only works with SASHDAT files that are created with the OLIPHANT procedure or with the SASHDAT Engine. SASHDAT is the data format used for SAS tables that are added to HDFS.

The main reason for creating a new library of the type SASHDAT is to support an additional HDFS directory. For each HDFS directory, you need a designated HDFS library (and a corresponding LASR library).

Register a SASHDAT Library

To register a SASHDAT library, perform the following steps:

1 On the Plug-ins tab in SAS Management Console, expand Data Library Manager.

Right-click Libraries, and select New Library.

2 In the New Library wizard, select High-Performance Analytics  SASHDAT

Library. Click Next.

Enter a name. If necessary, adjust the location. Click Next.

Select the appropriate server from the Available servers list and move it to the

Selected servers list. For this example, use SASApp. Click Next.

Establishing Connectivity to a SASHDAT Library

169

5 In the second quarter 2015, the Encryption Options section was added to SAS

Management Console.

Enter the following library properties:

Table 4.51 Library Properties

Field

Libref

Engine

HDFS path

Sample Value

Enter an identifier of your choice (for example,

SALESLIB

This field is not editable. The value, for libraries of the type SASHDAT.

SASHDAT

, is the engine name

Enter the HDFS source path (for example,

/dept/sales

In the LASR library that is paired with this library, the server tag must be the HDFS source path in dot-delimited format. For example, if the path is /dept/sales, then the server tag is

dept.sales

Note:

To take advantage of the parallel loading features in SAS

Visual Analytics clients, limit the path to eight characters or less and do not use a subdirectory. For example, use of

/sales

/dept/sales

. The value of the server tag, which is based on the path, is used as a libref and must meet SAS naming requirements.

instead

Enable Encryption: Specifies whether to enable on-disk AES encryption for the library.

Select Inherit from data server to use the encryption setting from the associated Hadoop server definition. Enabling encryption does not immediately encrypt existing non-encrypted data. Select Yes to enable on-disk AES encryption for the library.

New Encrypt Key:

If you selected Yes, enter an encryption key.

Confirm Encrypt

Key:

Confirm the encryption key.

170

Chapter 4 / Connecting to Common Data Sources

6 Assign the library to a Hadoop server by entering the following settings:

Table 4.52 Connection Properties

Field

Database

Server

Connection

Default Login

Sample Value

Select a server from the drop-down list. Select the server that uses the same host as the SAS LASR Analytic Server to use with this library.

Use the pre-selected value (which prepends the selected server name with the string

Connection:)

This field is not editable. The value is

(None)

Registering and Verifying Tables

171

Click Next.

7 Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Next, create a corresponding LASR library. See

“Stage 2: Register a SAS LASR

Analytic Server Library Using SAS Management Console” on page 160

Registering and Verifying Tables

Overview to Registering Tables

You need to make sure that the end users of your SAS applications can gain access to tables in your data libraries. The exact steps and authorization requirements vary across applications and data types. You must always log on to the application, register the needed metadata, and verify the existence of the tables. This example focuses on the process used to verify SAS tables in SAS Management Console.

This user account that is used for registering tables must have these permissions: n

ReadMetadata and WriteMetadata permission in the DefaultACT for the repository.

ReadMetadata and WriteMetadata permission on the library.

WriteMemberMetadata permission to the folder where the table metadata is to be stored.

Permission to the data source to read the tables. This is not a SAS metadata permission.

When you register tables in metadata, you choose the metadata folder location to use for storing the table metadata. Be aware that the table metadata inherits the metadata permissions that are granted on the folder. Select or create a folder with the metadata permissions that meet your business needs. You can also use an existing folder and change the metadata permissions.

Verifying your access to tables in SAS Management Console is a two-stage process:

172

Chapter 4 / Connecting to Common Data Sources

1 Register the tables.

2 Verify Access to the Data in a SAS Application.

Stage 1: Register the Tables

To register the tables, perform the following steps:

1 Open the SAS Management Console, if necessary.

2 Select Data Library Manager  Libraries to see the list of libraries.

Right-click the library that contains the tables that you need to import and select

Register Tables.

Verify that the values shown in the fields in the Library details group box are correct. Click Next.

Click the tables that you need to select. (Hold down the Ctrl key and click to select more than one table.)

Check the metadata folder path in the Location field. Navigate to a folder or create a folder that has metadata permissions for user and group access that meets your business needs.

Click Next.

Examine the final page of the wizard to ensure that the proper values have been entered. Click Finish to save the wizard settings.

Note:

You can also register tables by using SAS Data Integration Studio or by using the METALIB procedure. For information about using the METALIB procedure, see

Chapter 2, “Managing Table Metadata,” on page 23

Read-only Access for Reporting Libraries

173

Stage 2: Verify Access to the Data in a SAS

Application

Open an application that can view SAS data in order to view the data in the imported tables and review the data. For example, you can use SAS Data Integration Studio. To use SAS Data Integration Studio to view a registered table, perform the following steps:

Navigate to the Inventory tree and expand the Table node.

Right-click a table that you need to verify and select the Open option. Examine the data contained in the table in the View Data dialog box.

Close the View Data window.

(Optional) You can also examine the table's Properties field. Right-click the table and select the Properties option.

Click the Columns tab to see column data for the table. Close the Properties dialog box.

Read-only Access for Reporting

Libraries

If your site uses libraries for reporting, or for access exclusively by report generating applications such as SAS Information Map Studio and SAS Web Report Studio, then consider setting Read-Only access for the library. If the library is not set for Read-Only access, then even when reporting applications raise a query against the library, the underlying SAS session opens the data in read-write mode. In this case, simultaneous queries against the same library might be prevented. Simply put, if clients access the information in Read-Only mode, then set the library to read the data source in Read-

Only mode.

174

Chapter 4 / Connecting to Common Data Sources

Table 4.53 Setting a Library for Read-Only Access

Library Type

All Database Data Libraries

Base SAS Library

SAS Information Map Library

SAS XML Library

Where to Set Read-only Access

Advanced Options dialog box, Input/Output tab, option

Data access level for connection

Advanced Options dialog box, Options for any host tab

Always read-only, no configuration needed

Library properties page of the wizard, Library Access option

SAS Scalable

PerformanceData Engine

Library

Advanced Options dialog box, Options for any host tab

SAS/SHARE REMOTE Engine

Library

Advanced Options dialog box, LIBNAME Options tab

Setting UNIX Environment Variables for

SAS/ACCESS

If you are attempting to connect to data sources located on UNIX by using

SAS/ACCESS, you must set environmental variables so that SAS servers can access the database. Each database vendor and operating system vendor requires specific environment variables to be set. A typical value is LD_LIBRARY_PATH. When using

ODBC, two typical values are ODBCINI and ODBCINSTINI. For more information about the correct environment variables, go to the Install Center at http://support.sas.com/ documentation/installcenter/94 , and use the operating system and SAS version to locate the appropriate SAS Foundation Configuration Guide.

To set the appropriate environment variables in the !SASROOT/bin/sasenv_local file, perform the following steps:

Troubleshooting SAS/ACCESS Connections to Relational Databases

175

1 Edit the sasenv_local file and add the variables. This example uses sample values, substitute the proper paths:

ODBCINI=/opt/drivers/odbc/odbc.ini

export ODBCINI

ODBCINSTINI=/opt/drivers/odbc/odbcinst.ini

export ODBCINSTINI

LD_LIBRARY_PATH=/opt/drivers/odbc/lib:\

/opt/oracle/app/oracle/product/12.1.0/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH

ORACLE_HOME=/opt/oracle/app/oracle/product/12.1.0

EXPORT ORACLE_HOME

In SAS Management Console, right-click the Workspace Server connection and select Validate to verify that the workspace server starts correctly with the new environment variables.

Restart the SAS/SHARE and SAS/CONNECT servers, if they are present in the deployment and reference the SAS/ACCESS library.

Troubleshooting SAS/ACCESS

Connections to Relational Databases

This section provides information about troubleshooting a SAS/ACCESS library configuration when registering tables fails. To troubleshoot the SAS/ACCESS library, perform the following steps:

From the SAS Management Console, right-click the library icon and select Display

LIBNAME Statement.

Start SAS on the SAS server host and issue the LIBNAME statement displayed from the SAS Management Console.

If the SAS log indicates failure, check the following items:

176

Chapter 4 / Connecting to Common Data Sources

If this is UNIX environment, check “Setting UNIX Environment Variables for

SAS/ACCESS” on page 174

b Check and revise the LIBNAME statement. For more information about

LIBNAME statements for SAS/ACCESS engines, see SAS/ACCESS for

Relational Databases: Reference. If you are successful at this stage, then use the Properties tab of the library to reconfigure the library.

c Confirm that SAS/ACCESS is installed correctly. For installation information, go to the Install Center at http://support.sas.com/documentation/installcenter/94 and use the operating system and SAS version to locate the appropriate SAS

Foundation Configuration Guide.

4 If the connection succeeds, run the DATASETS procedure: proc datasets library=libref; quit;

If no members are returned, then check the schema value by performing the next step or contacting your database administrator.

5 Log on with the user account to the host where the SAS server is running, and use the native database client to connect to the database. If this fails, confirm the user account has file system privileges to the database client binaries and libraries.

177

Optimizing Data Storage

Overview of Optimizing Data Storage

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

178

Compressing Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

179

Indexing Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

182

Sorting Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

184

Overview to Sorting Data

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

184

Multi-Threaded Sorting

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Sorting a Database Table

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

warehouses, all four data storage structures (explained in Chapter 1, “Overview of

Buffering Data for Base SAS Tables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

187

Buffering Data for SAS/ACCESS Databases

. . . . . . . . . . . . . . . . . . . . . . .

189

Using Threaded Reads

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

190

Validating SAS Scalable Performance Data

Engine Hardware Configuration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

191

Setting SAS LIBNAME Options That Affect

Performance of SAS Tables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

191

Setting SAS LIBNAME Options That Affect

Performance of SAS/ACCESS Databases

. . . . . . . . . . . . . . . . . . . . . . . . . .

193

Setting SAS LIBNAME Options That Affect

Performance of SAS SPD Engine Tables

. . . . . . . . . . . . . . . . . . . . . . . . . . .

197

SAS Grid Computing Data Considerations

. . . . . . . . . . . . . . . . . . . . . . . .

200

178

Chapter 5 / Optimizing Data Storage

Application Response Monitoring

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

201

Overview of Optimizing Data Storage

For the purposes of querying, cube loading, and creating data marts and data

Common Data Sources,” on page 1

) can be optimized to improve performance. Some optimization can be achieved by specifying transformation options in SAS Data

Integration Studio. Some optimization requires hardware configuration, as in the case of

SAS Scalable Performance Data (SPD) Engine tables. Cubes can be optimized for querying and loading during the cube loading process. For SAS tables, database tables, and SPD Engine tables, libraries can be defined in the metadata with options that enhance performance.

For more information, see these sections: n

“Compressing Data” on page 179

“Indexing Data” on page 182

“Sorting Data” on page 184

“Buffering Data for Base SAS Tables” on page 187

“Buffering Data for SAS/ACCESS Databases” on page 189

“Using Threaded Reads” on page 190

“Validating SAS Scalable Performance Data Engine Hardware Configuration” on page 191

“SAS Grid Computing Data Considerations” on page 200

Compressing Data

179

Compressing Data

Compression is a process that reduces the number of bytes that are required to represent each table row. In a compressed file, each row is a variable-length record. In an uncompressed file, each row is a fixed-length record. Compressed tables contain an internal index that maps each row number to a disk address so that the application can access data by row number. This internal index is transparent to the user. Compressed tables have the same access capabilities as uncompressed tables. Here are some advantages of compressing a file: n reduced storage requirements for the file n fewer I/O operations necessary to read from or write to the data during processing

Here are some disadvantages of compressing a file: n

More CPU resources are required to read a compressed file because of the overhead of uncompressing each observation.

There are situations when the resulting file size might increase rather than decrease.

These are the types of compression that you can specify: n

CHAR to use the RLE (Run Length Encoding) compression algorithm, which works best for character data.

BINARY to use the RDC (Ross Data Compression) algorithm, which is highly effective for compressing medium to large (several hundred bytes or larger) blocks of binary data.

You can compress these types of tables: n all tables that are created during a SAS session. Besides specifying SAS system options on the command line or inside a SAS program with the OPTIONS statement, you can use SAS Data Integration Studio to set system options. For example, you can use the System Options field to set the COMPRESS= system option on a table loader transformation. (A table loader transformation generates or retrieves code that puts data into a specified target table.)

180

Chapter 5 / Optimizing Data Storage

Figure 5.1 The Options Tab in a Table Loader Properties Dialog Box in SAS Data Integration

Studio

n all tables for a particular library. For example, when you register a Base SAS engine library in the metadata, you can specify the COMPRESS= option in the Other

options to be appended field on the Options for any host tab. For more

information, see “Setting SAS LIBNAME Options That Affect Performance of SAS

Tables” on page 191

). For third-party relational database tables, you can use the

Options to be appended field on the Other Options tab. For more information, see

“Setting SAS LIBNAME Options That Affect Performance of SAS/ACCESS

Databases” on page 193

Note:

You cannot specify compression for an SPD Engine data library.

an individual table. In SAS Data Integration Studio, SAS tables have a Compressed option that is available from the table properties dialog box. To use CHAR compression, you select YES. To use BINARY compression, you select Binary.

Figure 5.2 The Table Options Dialog Box in SAS Data Integration Studio

Compressing Data

181

For SPD Engine tables and third-party relational database tables, you can use the

Table Options field in the table properties dialog box to specify the COMPRESS= option.

Note:

The SPD Engine compresses the data component (DPF) file by blocks as the engine is creating the file. (The data component file stores partitions for an SPD Engine table.) To specify the number of observations that you want to store in a compressed block, you use the IOBLOCKSIZE= table option in addition to the COMPRESS= table option. For example, in the Table Options field in the table properties dialog box, you might enter COMPRESS=YES IOBLOCKSIZE=10000. The default blocksize is 4096 (4k).

When you create a compressed table, SAS records in the log the percentage of reduction that is obtained by compressing the file. SAS obtains the compression percentage by comparing the size of the compressed file with the size of an uncompressed file of the same page size and record count. After a file is compressed, the setting is a permanent attribute of the file, which means that to change the setting, you must re-create the file. For example, to uncompress a file, in SAS Data Integration

Studio, select Default (NO) for the Compressed option in the table properties dialog box for a SAS table.

For more information about compression, see SAS Data Set Options: Reference.

182

Chapter 5 / Optimizing Data Storage

Indexing Data

An index is an optional file that you can create to provide direct access to specific rows.

The index stores values in ascending value order for a specific column or columns and includes information about the location of those values within rows in the table. In other words, an index enables you to locate a row by value. For example, if you use SAS to find a specific Social Security number (123-45-6789), SAS performs the search differently depending on whether there is an index on the column that contains the

Social Security numbers: n

Without an index, SAS accesses rows sequentially in the order in which they are stored in the table. SAS reads each row, looking for SSN=123-45-6789 until the value is found, or all observations are read.

With an index on column SSN, SAS accesses the row directly. SAS satisfies the condition by using the index and going straight to the row that contains the value.

SAS does not have to read each row.

When you create an index, you designate which columns to index. You can create two types of indexes: n a simple index, which consists of the values of one column.

n a composite index, which consists of the values of more than one column. The values are concatenated to form a single value

For each indexed column, you can also perform these tasks: n declare unique values. A unique index guarantees that values for one column or the combination of a composite group of columns remain unique for every row in the table. If an update tries to add a duplicate value to that column, then the update is rejected.

n keep missing values from using space in the index by specifying that missing values are not maintained by the index.

Indexing Data

183

In addition to writing SAS code to create indexes, you can create indexes on target tables by using SAS Data Integration Studio. In SAS Data Integration Studio, you use the properties window for the table to index individual columns. When you create the index, you can also specify Unique values and No missing values. Note that any indexes registered in metadata for a target table are physically created when the job is run. Simply editing the properties for an existing table and adding indexes does not update the physical table. The SAS Data Integration Studio properties dialog box for a table is shown below:

Figure 5.3 The Indexes Tab in the Properties Dialog Box for a Table Named STORE_ID

In general, SAS can use an index to improve performance in these situations: n

For cube loading, a composite index on the columns that make up the cube's hierarchies might provide best results.

For WHERE processing, an index can provide faster and more efficient access to a subset of data. Note that to process a WHERE expression, SAS decides whether to use an index, or to read the table sequentially.

184

Chapter 5 / Optimizing Data Storage

Note:

For WHERE processing, the Base SAS engine uses a maximum of one index. The SPD Engine can use multiple indexes.

Even though an index can reduce the time that is required to locate a set of rows, especially for a large table, there are costs that are associated with creating, storing, and maintaining the index. When deciding whether to create an index, you must consider increased resource usage, along with the performance improvement.

Once an index exists, SAS treats it as part of the table. That is, if you add or delete columns or modify values, the index is automatically updated.

For more information about indexes, see SAS Language Reference: Concepts.

Sorting Data

Overview to Sorting Data

You can sort table rows by the values of one or more character or numeric columns. For

Base SAS tables and third-party relational database tables, the process either replaces the original table or creates a new table. You can perform sorting in two ways: n using the SAS SORT procedure n setting properties for a SAS sort template in SAS Data Integration Studio, as shown below:

Figure 5.4 The Sort by Columns Tab in the Sort Properties Dialog Box

Sorting Data

185

To manage the memory that is used for the sorting process, you can specify the maximum amount of memory that is available to the sort. Generally, the sort size should be less than the physical memory available to the process. If the sorting requires more memory than you specify, then SAS creates a temporary utility file on disk. To specify a sort size in SAS Data Integration Studio, access the Options tab in the properties window for the sort template and enter a value in the Sortsize field, as shown below:

186

Chapter 5 / Optimizing Data Storage

Figure 5.5 The Options Tab in the SAS Sort Properties Dialog Box

The SPD Engine(SPD Engine) has implicit sorting capabilities, which saves time and resources for SAS applications that process large tables. When the SPD Engine encounters a BY clause, if the data is not already sorted or indexed on the BY column, then the SPD Engine automatically sorts the data without affecting the permanent table or producing a new table. You can change the implicit sorting options when you define

an SPD Engine library in the metadata. See “Setting SAS LIBNAME Options That Affect

Performance of SAS SPD Engine Tables” on page 197

For more information about the SORT procedure, see “SORT” in Base SAS Procedures

Guide

Multi-Threaded Sorting

The SAS system option THREADS activates multi-threaded sorting, which achieves a degree of parallelism in the sorting operations. This parallelism is intended to reduce the real time to completion for a given operation. However, the parallelism comes at the possible cost of additional CPU resources. For more information, see see “Support for

Parallel Processing” in SAS Language Reference: Concepts .

Buffering Data for Base SAS Tables

187

The performance of the multi-threaded sort is affected by the value of the SAS system option CPUCOUNT=. CPUCOUNT= indicates how many system CPUs are available for use by the multi-threaded sort. The multi-threaded sort supports concurrent input from the partitions of a partitioned table.

Note:

For information about the support of partitioned tables in your operating environment, see the SAS documentation for your operating environment.

For more information about THREADS and CPUCOUNT=, see the chapter about SAS system options in SAS System Options: Reference.

Sorting a Database Table

When you use a third-party database table, the column ordering that is produced by the

SORT procedure depends on whether the DBMS or SAS performs the sorting. If you use the BEST value of the SAS system option SORTPGM=, then either the DBMS or

SAS performs the sort. If the DBMS performs the sort, then the configuration and characteristics of the DBMS sorting program affect the resulting data order. Most database management systems do not guarantee sort stability, and the sort might be performed by the database table regardless of the state of the SORTEQUALS or

NOSORTEQUALS system options and the EQUALS or NOEQUALS procedure options.

If you set the SAS system option SORTPGM= to SAS, then unordered data is delivered from the DBMS to SAS and SAS performs the sorting. However, consistency in the delivery order of columns from a database table is not guaranteed. Therefore, even though SAS can perform a stable sort on the DBMS data, SAS cannot guarantee that the ordering of columns within output BY groups will be the same, run after run. To achieve consistency in the ordering of columns within BY groups, first populate a SAS table with the database table and then use the EQUALS or SORTEQUALS option to perform a stable sort.

Buffering Data for Base SAS Tables

For Base SAS tables, you might be able to make performance improvements by performing these tasks:

188

Chapter 5 / Optimizing Data Storage

n tuning the size of table pages on disk by using the BUFSIZE= system option. SAS uses the BUFSIZE= option to set the permanent page size for the SAS table. The page size is the amount of data that can be transferred for an I/O operation to one buffer. If you know that the total amount of data is going to be small, you can set a small page size, so that the total table size remains small and you minimize the amount of wasted space on a page. Large tables that are accessed sequentially benefit from larger page sizes because sequential access reduces the number of system calls that are required to read the table. n adjusting the number of open page buffers when the SAS table is processed.

Increasing the value of the BUFNO= option can improve performance by enabling applications to read more data with fewer passes; however, your memory usage increases. You must determine the optimal value for your needs.

Besides specifying SAS system options on the command line or inside a SAS program with the OPTIONS statement, you can set the BUFSIZE= and BUFNO= system options in SAS Data Integration Studio. For example, you can set these System Options in the properties window for a table loader transformation.

Figure 5.6 Table Loader Properties Dialog Box

For more information about the BUFSIZE= and BUFNO= options, see the SAS Data Set

Options: Reference and the documentation for your operating environment.

Buffering Data for SAS/ACCESS Databases

189

Note:

In addition, the SASFILE statement enables you to store the entire Base SAS table in memory. The table remains open until you close it because SASFILE caches the data and the open request. For more information about the SASFILE statement, see the SAS Statements: Reference.

Buffering Data for SAS/ACCESS

Databases

For DB2 (UNIX and PC), ODBC, OLE DB, Oracle, SQL Server, and Sybase, you can adjust page buffers by setting the INSERTBUFF= and READBUFF= options on the

library (see “Setting SAS LIBNAME Options That Affect Performance of SAS/ACCESS

Databases” on page 193

) or on the individual table. The options are described as follows: n

The INSERTBUFF= option specifies the number of rows to insert. SAS allows the maximum that is supported by the DBMS. The optimal value for this option varies with factors such as network type and available memory. You might need to experiment with different values in order to determine the best value for your site.

The READBUFF= option specifies the number of rows to hold in memory. SAS allows the maximum number that is supported by the DBMS. Buffering data reads can decrease network activities and increase performance. However, because SAS stores the rows in memory, higher values for READBUFF= use more memory. In addition, if too many rows are selected at once, then the rows that are returned to the SAS application might be out of date. For example, if someone else modifies the rows, you might not see the changes.

For more information about the INSERTBUFF= and READBUFF= options, see

SAS/ACCESS for Relational Databases: Reference.

190

Chapter 5 / Optimizing Data Storage

Using Threaded Reads

Most SAS/ACCESS interfaces support threaded Reads. With a threaded Read, the table read time can be reduced by retrieving the result set on multiple connections between SAS and a DBMS. To perform a threaded Read, SAS performs these tasks:

1 It creates threads, which are standard operating system tasks that are controlled by

SAS, within the SAS session.

2 It establishes a DBMS connection on each thread.

3 It causes the DBMS to partition the result set and reads one partition per thread. To cause the partitioning, SAS appends a WHERE clause to the SQL so that a single

SQL statement becomes multiple SQL statements, one for each thread.

Threaded Reads only increase performance when the DBMS result set is large.

Performance is optimal when the partitions are similar in size. In most cases, threaded

Reads should reduce the elapsed time of the SAS job. However, threaded Reads generally increase the workload on the DBMS. For example, threaded Reads for DB2 under z/OS involve a trade-off, generally reducing job elapsed time but increasing DB2 workload and CPU utilization.

Threaded Reads are most effective on new, faster computer hardware running SAS, and with a powerful parallel edition of the DBMS. For example, if SAS runs on a fast uniprocessor or on a multiprocessor machine and your DBMS runs on a high-end SMP server, you receive substantial performance gains.

For information about how to turn the threaded Read function on or off for a DBMS library, see

“Setting SAS LIBNAME Options That Affect Performance of SAS/ACCESS

Databases” on page 193

For information about threaded Reads, see SAS/ACCESS for Relational Databases:

Reference.

Setting SAS LIBNAME Options That Affect Performance of SAS Tables

191

Validating SAS Scalable Performance

Data Engine Hardware Configuration

The SAS Scalable Performance Data Engine (SPD Engine) automatically determines the optimal process to use to evaluate observations for qualifying criteria specified in a

WHERE statement. WHERE statement efficiency depends on such factors as whether the columns in the expression are indexed. A SAS configuration validation program that measures I/O scalability with respect to WHERE processing can help you determine whether your system is properly configured for performing WHERE processing with the

SPD Engine. The program performs these tasks:

It creates a table with two numeric columns.

It repeatedly reads the entire table, each time doubling the number of threads used until the maximum number is reached. The maximum number of threads is determined by the CPUCOUNT= SAS system option and is specified when SAS is started.

The resulting log file shows timing statistics for each cycle. You can examine this information to determine whether your system is configured correctly. The program is available at http://support.sas.com/rnd/scalability/spde/valid.html

Setting SAS LIBNAME Options That

Affect Performance of SAS Tables

You can set SAS LIBNAME options that might affect performance of the Base SAS engine. You set these options when you use the New Library wizard to register a Base

SAS engine library in the metadata repository. The LIBNAME options are available on the Options for any host tab and the Host-specific options tab in the Advanced

Options dialog box. To access the Advanced Options dialog box, click the Advanced

Options button on the Library Options page of the New Library wizard.

192

Chapter 5 / Optimizing Data Storage

Figure 5.7 The Options for Any Host Tab in the Advanced Options Dialog Box for a Base SAS

Library

Here are some examples of options that might affect performance:

Data representation for the output file (OUTREP=)

For all operating environments, you can specify the data representation for the output file. Specifying this option enables you to create files within the native environment by using a foreign environment data representation. For example, an administrator who works in a z/OS operating environment might want to create a file on an HFS system so that the file can be processed in an HP UNIX environment.

Specifying HP_UX_64 as the value for this option forces the data representation to match the data representation of the UNIX operating environment that will process the file. This method of creating the file can enhance system performance because the file does not require data conversion when being read by an HP UNIX machine.

Input/output block size (BLKSIZE=)

For Windows, UNIX, and z/OS environments, you can specify the number of bytes that are physically read during an I/O operation. The default is 8 kilobytes, and the maximum value is 1 megabyte.

Setting SAS LIBNAME Options That Affect Performance of SAS/ACCESS Databases

193

Number of page caches to use for each open member (CACHENUM=)

For VMS, you can specify the number of page caches to use during I/O operations.

The number of caches can potentially reduce the number of I/Os that are required to access the data. You can also set the size of each cache (CACHESIZE= option).

The Other option(s) to be appended field can be used to specify LIBNAME options such as COMPRESS=. (See

“Compressing Data” on page 179 .)

For information about each of the LIBNAME options in the Advanced Options dialog box, click the Help button.

Setting SAS LIBNAME Options That

Affect Performance of SAS/ACCESS

Databases

The following SAS LIBNAME options can be used to tune performance of the

SAS/ACCESS engines. You can set these options when you use the New Library wizard to register the database libraries in the metadata repository. To access the

Advanced Options dialog box, click the Advanced Options button on the Library

Options page of the New Library wizard.

194

Chapter 5 / Optimizing Data Storage

Figure 5.8 The Optimization Tab in the Advanced Options Dialog Box for a DB2 Library for

UNIX and PC

The tabs that are available in the Advanced Options dialog box, as well as the options on each of the tabs, vary between database management systems. The following list provides a description of the options on Optimization tab for DB2 libraries for UNIX and

PC:

Block insert buffer size (INSERTBUFF=)

specifies the number of rows in a single Insert operation. See “Buffering Data for

SAS/ACCESS Databases” on page 189

Setting SAS LIBNAME Options That Affect Performance of SAS/ACCESS Databases

195

Block read buffer size (READBUFF=) specifies the number of rows of DBMS data to read into the buffer. See

“Buffering

Data for SAS/ACCESS Databases” on page 189

Pass functions to the DBMS that match those supported by SAS (SQL_ FUNCTIONS=) when set to ALL, specifies that functions that match functions supported by SAS should be passed to the DBMS. The functions that are passed are: DATE,

DATEPART, DATETIME, TIME, TIMEPART, TODAY, QRT, COMPRESS, SUBSTR,

DAY, SECOND, INDEX, TRANWRD, HOUR, WEEKDAY, LENGTH, TRIMN,

MINUTE, YEAR, REPEAT, MOD, MONTH, BYTE, and SOUNDEX. Use of this option can cause unexpected results, especially if used for NULL processing and date, time, and timestamp handling. Exercise care when using this option.

Pass DELETE to the DBMS (DIRECT_EXE=) specifies that an SQL delete statement is passed directly to the DBMS for processing. Selecting this option improves performance because SAS does not have to read the entire result set and delete one row at a time.

Whether to use indexes (DBINDEX=) specifies whether SAS uses indexes that are defined on DBMS columns to process a join. Valid values are YES or NO. For more information about indexes, see

“Indexing Data” on page 182

Whether to check for null keys when generating WHERE clauses (DBNULLKEYS=) specifies whether the WHERE clause should detect NULL values in columns. Valid values are YES or NO. YES is the default for most interfaces and enables SAS to prepare the statement once and use it for any value (NULL or NOT NULL) in the column.

Multiple data source optimization (MULTI_ DATASRC_OPT=) when processing a join between two tables, specifies whether an IN clause should be created to optimize the join. Valid values are NONE and IN_CLAUSE.

IN_CLAUSE specifies that an IN clause containing the values read from a smaller table are used to retrieve the matching values in a larger table based on a key column designated in an equijoin.

When processing a join between a SAS table and a DBMS table, the SAS table should be smaller than the DBMS table for optimal performance.

196

Chapter 5 / Optimizing Data Storage

Whether to create a spool file for two-pass processing (SPOOL=) specifies whether to create a utility spool file during transactions that read data more than once. In some cases, SAS processes data in more than one pass through the same set of rows. Spooling is the process of writing rows that have been retrieved during the first pass of a data Read to a spool file. In the second pass, rows can be re-read without performing I/O to the DBMS a second time. In cases where the data needs to be read more than once, spooling improves performance. Spooling also guarantees that the data remains the same between passes. Valid values are YES or NO.

Threaded DBMS access (DBSLICEPARM=) specifies the scope of DBMS threaded Reads and the number of threads. If this option is set to the default, then PROC SQL does not use threading to read data for a web report. To force a specified number of threads for a threaded Read from the

DBMS server, change the default to (ALL,number-of-threads).

Note:

If PROC SQL attempts implicit pass-through, then threading is disabled, regardless of the Threaded DBMS access setting. To disable implicit pass-through, set the Pass generated SELECT SQL to the DBMS - DBMS processing option to

NO.

For more information about threaded Reads, see “Using Threaded Reads” on page

190

Pass generated SELECT SQL to the DBMS - DBMS processing (DIRECT_SQL=) specifies whether generated SQL is passed to the DBMS for processing. Valid values are YES or NO.

Pass generated SELECT SQL to the DBMS - exceptions to DBMS processing

(DIRECT_SQL=) if the value for the previous option is YES, then this option specifies how generated

SQL is passed to the DBMS for processing. For example, NOWHERE prevents

WHERE clauses from being passed to the DBMS for processing.

The Other Options tab, which is available for all database management systems, can be used to specify LIBNAME options such as the COMPRESS= option. For more

information, see “Compressing Data” on page 179

Setting SAS LIBNAME Options That Affect Performance of SAS SPD Engine Tables

197

For information about each of the LIBNAME options in the Advanced Options dialog box, click the Help button. For information about all SAS/ACCESS LIBNAME options, see SAS/ACCESS for Relational Databases: Reference.

Setting SAS LIBNAME Options That

Affect Performance of SAS SPD Engine

Tables

The following SAS LIBNAME options can be used to tune performance of the SAS

Scalable Performance Data Engine (SPD Engine). You can set these options when you use the New Library wizard to register an SPD Engine library in the metadata repository.

The LIBNAME options are available on the Options for any host tab in the Advanced

Options dialog box. To access the Advanced Options dialog box, click the Advanced

Options button on the Library Options page of the New Library wizard. The Advanced

Options dialog box is shown below:

198

Chapter 5 / Optimizing Data Storage

Figure 5.9 The Options for Any Host Tab in the Advanced Options Dialog Box for an SPD

Engine Library

Data path (DATAPATH=) specifies a list of paths in which to store partitions (DPF) files for an SPD Engine table. The engine creates as many partitions as are needed to store all the data. The size of the partitions is set using the PARTSIZE= option. Partitions are created in the specified paths in a cyclic fashion. The data path area is best configured as multiple paths. Allot one I/O controller per data path to provide high I/O throughput, which is the rate at which requests for work are serviced by a computer system. The data path area is best configured for redundancy (RAID 1).

Index path (INDEXPATH=) specifies a path or a list of paths in which to store the two index component files

(HBX and IDX) that are associated with an SPD Engine table. Additional specified

Setting SAS LIBNAME Options That Affect Performance of SAS SPD Engine Tables

199 paths accept the overflow from the immediately preceding path. The index path area is best configured as multiple paths. Use a volume manager file system that is striped across multiple disks (RAID 0) to enable adequate index performance, both when evaluating WHERE clauses and creating indexes in parallel. Redundancy

(RAID 5 or RAID 10) is also recommended.

Meta path (METAPATH=) specifies a list of overflow paths in which to store metadata component (MDF) files for an SPD Engine table. The metadata component file for each table must begin in the primary path. When that primary path is full, the overflow is sent to the specified

METAPATH= location. The metadata path area is best configured for redundancy

(RAID 1) so that metadata about the data and its indexes is not lost.

Partition size (PARTSIZE=) specifies the size (in megabytes) of the data component partitions when an SPD

Engine table is created. By splitting the data portion of an SPD Engine table at fixedsize intervals, you can gain a high degree of scalability for some operations. For example, the SPD Engine can spawn threads in parallel, up to one thread per partition for WHERE evaluations.

Temp (TEMP=) specifies whether to create a temporary subdirectory of the directory specified in the

Path field on the Library Properties window. The directory is used to temporarily store the metadata component files associated with table creation. It is deleted at the end of the SAS session.

By sort (BYSORT=) specifies that the SPD Engine should perform an automatic implicit sort when it finds a BY statement for processing data in the library (unless the data is indexed on the

BY column). Valid values are YES (perform the sort) and NO (do not perform the sort). The default is YES.

Starting observation number (STARTOBS=) specifies the number of the starting observation in a user-defined range of observations that are qualified with a WHERE expression. By default the SPD

Engine processes all observations in the table.

200

Chapter 5 / Optimizing Data Storage

Ending observation number (ENDOBS=) specifies the number of the ending observation in a user-defined range of observations that are qualified with a WHERE expression. By default the SPD

Engine processes all observations in the table.

In addition to the LIBNAME options, there are also table and system options that can be used to tune SPD Engine performance. For example, the SPDEUTILLOC= system option allots space for temporary files that are generated during SPD Engine operations. This area is best configured as multiple paths. Use a volume manager file system that is striped across multiple disks (RAID 0) to reduce out-of-space conditions and improve performance. Redundancy (RAID 5 or RAID 10) is also recommended because losing the work area could stop the SPD Engine from functioning.

The “Quick Guide to the SPD Engine Disk-I/O Set-Up” available at http:// support.sas.com/rnd/scalability/spde/spde_setup.pdf helps you do the following: n determine the amount of space that needs to be allocated to the data, metadata, index, and work areas n evaluate the advantages and disadvantages of different RAID groups for each of the different types of areas

For more information about table and other system options for the SPD Engine, see http://support.sas.com/rnd/scalability/spde/syntax.html. For more information about each of the LIBNAME options in the Advanced Options dialog box, click the Help button.

SAS Grid Computing Data

Considerations

SAS Grid computing has become an important technology for organizations that do the following: n have long-running applications that can benefit from parallel execution n want to leverage existing IT infrastructure to optimize computing resources and manage data and computing workloads

Application Response Monitoring

201

The function of a grid is to distribute tasks. Each of the tasks that are distributed across the grid must have access to all the required input data. Computing tasks that require substantial data movement generally do not perform well in a grid. To achieve the highest efficiency, the nodes should spend the majority of the time computing rather than communicating. With grid computing using SAS Grid Manager, the speed at which the grid operates is related more to the storage of the input data than to the size of the data.

Data must either be distributed to the nodes before running the application or— much more commonly—made available through shared network libraries. Storage on local nodes is discouraged. The data storage must scale to maintain high performance while serving concurrent data requests.

The parallel data load is monitored throughout.

Application Response Monitoring

SAS implements the Application Response Monitoring 4.0 (ARM) specification. SAS offers macros, system options, and logging facility as an ARM agent for collecting application availability, performance, usage, and transaction response time. For more information about the ARM implementation, see the SAS Interface to Application

Response Measurement (ARM): Reference.

SAS Data Integration Studio can report the following measures for jobs: n number of records processed n duration of step in the job n

I/O statistics

To view the metrics within SAS Data Integration Studio, right-click the diagram background for the job and select Collect Runtime Statistics. When the job is run, view the Statistics tab in the Details area of the window.

202

Chapter 5 / Optimizing Data Storage

203

Managing OLAP Cube Data

Introduction to Managing OLAP Cube Data

. . . . . . . . . . . . . . . . . . . . . . .

204

Data Storage and Access

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

204

Exporting and Importing Cubes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

205

About OLAP Schemas

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

206

Create or Assign an OLAP Schema

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

206

Building a Cube

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

207

Overview of Building a Cube

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

207

Preparations for Building a Cube

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

208

Storage Location Requirements for Cube

Metadata and Related Objects

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Making Detail Data Available to a Cube for Drill-Through

. . . . . .

210

Making Detail Data Available to an OLAP Server for Drill-Through

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

212

Making Detail Data Available to an Information

Map for Drill-Through

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

214

Display Detail Data for a Large Cube

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

215

204

Chapter 6 / Managing OLAP Cube Data

Introduction to Managing OLAP Cube

Data

Online Analytical Processing (OLAP) is a technology that is used to create decision support software. OLAP enables application users to quickly analyze information that has been summarized into multidimensional views and hierarchies. By summarizing predicted queries into multidimensional views before run time, OLAP tools provide the benefit of increased performance over traditional database access tools. Most of the resource-intensive calculation that is required to summarize the data is done before a query is submitted. One of the advantages of OLAP is how data and its relationships are stored and accessed. OLAP systems house data in structures that are readily available for detailed queries and analytics.

Data Storage and Access

Organizations usually have databases and data stores that maintain repeated and frequent business transaction data. This provides simple yet detailed storage and retrieval of specific data events. However, these data storage systems are not well suited for analytical summaries and queries that are typically generated by decision makers. For decision makers to reveal hidden trends, inconsistencies, and risks in a business, they must be able to maintain a certain degree of momentum when querying the data. An answer to one question usually leads to additional questions and review of the data. Simple data stores do not generally suffice.

The data warehouse is a structure better suited for this type of querying. In a data warehouse, data is maintained and organized so that complicated queries and summaries can be run. OLAP further organizes and summarizes specific categories and subsets of data from the data warehouse. One particular type of data structure derived from a data warehouse is the cube. A cube is a set of data that is organized and structured in a hierarchical, multidimensional arrangement. Such an arrangement results in a robust and detailed level of data storage with efficient and fast query returns.

Exporting and Importing Cubes

205

Stored, precalculated summarizations called aggregations can be added to the cube to improve cube access performance.

Exporting and Importing Cubes

Cubes are exported and imported as part of a SAS package. SAS Management

Console is one of the user interfaces that can perform the import and export of packages. For more information about creating SAS packages, see “Promotion Tools

Overview” in SAS Intelligence Platform: System Administration Guide .

The data administrator impact of exporting and importing cubes is that when cubes are imported, the tables used in the cube must be available. Building the aggregations for the cube is also computationally intensive. The following list highlights some best practices: n

It is impractical to package the detail tables and summary data for large cubes. Do not export them in the package.

If the cube is being imported to a new metadata server (as opposed to being moved to a new folder on the same metadata server), then make sure the same data sources for the detail tables used by the original cube are available and registered.

Accomplish this by registering the same data servers and data libraries on the destination metadata server. If the cube uses a drill-through table, ensure that the library is pre-assigned.

When importing the cubes, be prepared to associate the cube with an OLAP schema. Consider that the OLAP schema determines the group of cubes that an

OLAP server can access.

Once the cube is imported, the cube and its job are registered in metadata with relationships to an OLAP schema, tables, and folders. By default, the aggregations for the cube must be built after the cube is imported. Due to the computational intensity, consider rebuilding the cube during a period of low activity.

206

Chapter 6 / Managing OLAP Cube Data

About OLAP Schemas

OLAP schemas provide an organizational function. An OLAP schema is a list of cubes that are grouped together so that they can be accessed by one or more SAS OLAP

Servers. Each cube is listed in one and only one OLAP schema. Each SAS OLAP

Server is required to use one OLAP schema. Multiple servers can use the same schema. To assign cubes to specific servers, you create new OLAP schemas. This might be necessary if you have multiple large cubes. In that case, you might want to assign one cube to one host, to one SAS OLAP Server, and to one OLAP schema.

New OLAP schemas are created with the Create OLAP Schema wizard in SAS OLAP

Cube Studio or SAS Management Console. SAS OLAP Servers are assigned to new

OLAP schemas by changing server properties in SAS Management Console. To create a new OLAP schema or assign an OLAP schema to a SAS OLAP Server using SAS

Management Console, see “Create or Assign an OLAP Schema” on page 206

. A SAS

OLAP Server reads its assigned OLAP schema from metadata only as the server starts.

Assigning a new OLAP schema to a server requires that you restart the SAS OLAP

Server.

When building, updating, or deleting cubes, you can specify OLAP schemas in the Cube

Designer wizard of SAS OLAP Cube Studio. Alternatively, if you choose to write SAS code for PROC OLAP, the schema is specified in the OLAP_SCHEMA= option of the

METASVR statement.

Create or Assign an OLAP Schema

To create a new OLAP schema or assign an OLAP schema to a SAS OLAP Server, perform the following steps:

1 Open SAS Management Console.

2 In the left pane, expand Server Manager.

Building a Cube

207

3 Under Server Manager, locate the SAS Application Server that contains the SAS

OLAP Server. The name of one such SAS Application Server might be SASApp, for example.

4 Right-click the top-level SAS Application Server and select Properties.

5 In the Properties window, click the OLAP Schema tab.

6 Click New to create a new OLAP schema, or select the down arrow to choose an existing OLAP schema.

7 Click OK to save changes and close the Properties window.

8 Restart the SAS OLAP Server using the SAS OLAP Server Monitor.

Building a Cube

Overview of Building a Cube

The following is a summary of the cube-building process. For additional information about building and modifying SAS OLAP cubes, see the SAS OLAP Server: User's

Guide.

Before building a cube, you should collect and scrub your data in addition to planning a dimensional design. When you define the cube, you define the dimensions and measures for the cube along with information about how aggregations should be created and stored. There are two methods of creating a cube: n

You can submit PROC OLAP code by using either the SAS Program Editor or a batch job. If you use PROC OLAP, the cube is created, and then the cube definition is stored in a metadata repository. This is referred to as the long form of PROC

OLAP.

You can use the Cube Designer interface in SAS OLAP Cube Studio to define and create the cube. The Cube Designer first stores the cube definition in a metadata

208

Chapter 6 / Managing OLAP Cube Data

repository, and then submits a shorter form of PROC OLAP code to create the cube.

This is referred to as the short form of PROC OLAP.

Note:

The Cube Designer can also be launched from SAS Data Integration Studio.

Preparations for Building a Cube

To build a cube by using either PROC OLAP or SAS OLAP Cube Studio, you must perform several preliminary tasks: n

Configure a metadata server. n

Define an OLAP server in the metadata. The server does not need to be running to create cubes, but it must be defined in the metadata.

Analyze the data to determine the location of the table or tables to use for building your cubes and what dimensions and measures will be created.

Register the table or tables to use for creating the cube in the metadata. You do this by using SAS Data Integration Studio or by using SAS OLAP Cube Studio and SAS

Management Console as follows: o

Use SAS Management Console to register the metadata for the server to use for accessing the tables. This is a SAS Application Server with a workspace server component.

Use SAS Management Console to register metadata for the library that contains the table.

In SAS OLAP Cube Studio, specify the server to use for accessing the tables. To set the server, select Tools  Options. Or, if the shortcut bar is displayed, select

Options to set the server. o

In SAS OLAP Cube Studio, select Source Designer to load the table definitions

(or other information source) as follows: n n

From the shortcut bar, select Tools



Source Designer or select Source

Designer .

Select a Source Type (SAS, ODBC, and so on), and then select Next.

Building a Cube

209 n n

If you have not specified a server, or if the server that is specified is not valid, then you are prompted again for a server.

Select the library that contains the tables that you want to use, and then select Next.

n n

Select the tables to register and then select Next.

Select Finish. The table definitions are register in metadata.

If you start to create a cube and do not see the table that you need to continue, then you can click the Define Table button in any of the windows that prompt for tables.

In the Finish window of the cube designer, you are given the option to create the physical cube. The metadata definition is always stored as you leave the Finish window. However, you can defer creation of the physical cube because it might be a resource and time intensive process. If you choose to create the cube as you leave the Finish window, then a SAS Workspace Server must be defined so that you can submit PROC OLAP code to it. This server is defined in SAS Management Console.

For more information about the different data types that you can use to load cubes from, see “Planning for SAS OLAP Cubes” in SAS OLAP Server: User's Guide .

Note:

The SAS Metadata Server enables duplicate librefs to be defined in the metadata. To ensure that the correct library definition is found on the metadata server, you should assign the libref by using the LIBNAME statement for the metadata engine before submitting the PROC OLAP code. Otherwise, PROC OLAP selects the first library definition that it finds with your specified libref, and it associates your cube metadata with that definition. The selected library definition might or might not contain a description of the data that was actually used to build your cube. For more information about using the LIBNAME statement for the metadata engine, see “Metadata LIBNAME

Engine” in SAS Language Interfaces to Metadata.

When a SAS OLAP cube is created, a directory for that cube is also created. This directory is assigned the same name as the cube, but in uppercase letters. For example, if you save a cube in c:\olapcubes and name the cube Campaigns, the cube is saved in the directory c:\olapcubes\CAMPAIGNS.

210

Chapter 6 / Managing OLAP Cube Data

Storage Location Requirements for Cube

Metadata and Related Objects

When storing metadata that describes a cube, the metadata objects that describe the cube and the cube's associated libraries and source tables must be stored in the same repository, or the metadata that describes the cube must be in a custom repository that is dependent on the repository that contains the library and table objects. Otherwise, you will not be able to create the cube. In addition, the library and table objects that are referenced by a cube must always be in the same repository. The following options illustrate these conditions: n

The library, table, and cube objects can be in a Foundation repository. n

The library, table, and cube objects can be in Project A, which is dependent on the

Foundation repository.

The library and table objects can be in the Foundation repository, and the cube object can be in Project A. n

The cube object cannot be in the Foundation repository, and the library and table objects cannot be in Project A. n

The table object cannot be in the Foundation repository, and the library and cube objects cannot be in Project A.

The library object cannot be in the Foundation repository, and the table and cube objects cannot be in Project A.

Making Detail Data Available to a Cube for Drill-Through

You can drill through an OLAP report to the underlying detail data only after you make the detail data available to the cube. You can use either SAS OLAP Cube Studio or the

OLAP procedure to make detail data available to the cube:

Making Detail Data Available to a Cube for Drill-Through

211 n

In SAS OLAP Cube Studio, you can specify a table for drill-through when you create or edit the cube using the Cube Designer wizard. On the Drill-Through page of the wizard, either select a table and click the right-arrow and then Next to specify the drill-through table, or just click Next if drill-through is not needed. The following figure shows the Cube Designer - Drill Through page of the Cube Designer wizard:

Figure 6.1 Cube Designer

For more information about the Cube Designer wizard, see the SAS OLAP Cube

Studio Help. Note that for star schema tables, a view that fully joins the fact and dimension tables is the drill-through table.

In the PROC OLAP statement, use the DRILLTHROUGH_TABLE option to specify the name of the drill-through table to use. For more information about the

DRILLTHROUGH_TABLE option, see “The OLAP Procedure” in SAS OLAP Server:

User's Guide

212

Chapter 6 / Managing OLAP Cube Data

Making Detail Data Available to an

OLAP Server for Drill-Through

You can drill through an OLAP report to the underlying detail data only after you make the detail data available to the OLAP Server. In order for the OLAP server to make detail data available for a cube, the library for the table that contains the detail data must be registered so that the OLAP server can identify the library to use. Also, the library permissions must allow ReadMetadata permission. The simplest way to register the library to the server is to pre-assign it and store the library in a folder that grants

ReadMetadata permission to PUBLIC.

To specify a library as pre-assigned for an OLAP server, perform the following steps:

In Data Library Manager (in SAS Management Console), find the Libraries folder and perform one of the following tasks to get to the dialog box that lets you select advanced options: n

For a new library, right-click the Libraries folder and select New Library to start the New Library wizard. Then navigate to the page that enables you to specify the libref.

For an existing library, open the Libraries folder and right-click the desired library. Select Properties from the drop-down menu, and then select the Options tab in the properties dialog box.

Figure 6.2 Library Properties

Making Detail Data Available to an OLAP Server for Drill-Through

213

Click Advanced Options.

Select the Library is pre-assigned check box on the Pre-Assign tab in the

Advanced Options dialog box.

On the Assign tab of the properties dialog box or the server selection page of the

New Library wizard, ensure that the selected application server is the server container that contains your OLAP server.

Figure 6.3 Specifying an Assigned Server

214

Chapter 6 / Managing OLAP Cube Data

5 Click OK in the properties dialog box, or finish entering information in the wizard.

6 Restart the OLAP server.

The selected library is assigned after the selected OLAP server starts. After the OLAP server starts, ensure that the library is pre-assigned to the correct SAS OLAP server.

The OLAP server also generates a record in the log file stored at SAS-

configuration-directory\Lev1\SASApp\OLAPServer\Logs\.

The following example shows how pre-assigned libraries are identified in the log file:

2008-08-04T13:00:13,068 WARN [00000010] :SYSTEM@host - NOTE: Libref odbc successfully assigned from logical server.

2008-08-04T13:00:13,068 WARN [00000010] :SYSTEM@host - NOTE: Libref wrstemp successfully assigned from logical server.

2008-08-04T13:00:13,068 WARN [00000010] :SYSTEM@host - NOTE: Libref wrsdist successfully assigned from logical server.

2008-08-04T13:00:13,068 WARN [00000010] :SYSTEM@host - NOTE: Libref stpsamp successfully assigned from logical server.

2008-08-04T13:00:13,068 WARN [00000010] :SYSTEM@host - NOTE: Libref SASDATA successfully assigned from logical server.

Making Detail Data Available to an

Information Map for Drill-Through

You can drill through an OLAP report to the underlying detail data only after you make the detail data available to the information map. In order for an information map to produce a report that has drill-through capabilities, an option must first be set in the information map.

For an existing information map, open the information map, right-click it, and then select

Properties from its drop-down menu. Select the Allow drill-through to detail data check box on the Definition tab in the Information Map Properties dialog box. This check box is displayed only when a drill-through table is specified for the cube that the

OLAP information map is using as its data source.

Figure 6.4 Information Map Properties

Display Detail Data for a Large Cube

215

Display Detail Data for a Large Cube

If your cube contains an extremely large amount of detail data, then in order to view that data from within SAS Information Map Studio, you might need to increase the Java heap size for SAS Information Map Studio or increase the maximum number of drillthrough rows that your SAS OLAP Server can handle. The default number of drill– through rows that can be displayed by a query is 300,000 rows.

You can increase the number of drill-through rows that your OLAP server can handle by changing the OLAP server definition with the Server Manager plug-in to SAS

Management Console. To increase the number of drill-through rows, perform the following steps:

In the navigation tree for Server Manager, find the node that represents your physical OLAP server.

216

Chapter 6 / Managing OLAP Cube Data

2 Right-click the icon and select Properties

3 In the properties dialog box, select the Options tab, and then click Advanced

Options.

4 In the Advanced Options dialog box, select the Server tab, and then enter the desired value for the Maximum number of flattened rows field.

Figure 6.5 SAS OLAP Server Advanced Options

Click OK to save the setting.

217

Glossary

aggregation

a summary of detail data that is stored with or referred to by a cube.

application server

a server that is used for storing applications. Users can access and use these server applications instead of loading the applications on their client machines. The application that the client runs is stored on the client. Requests are sent to the server for processing, and the results are returned to the client. In this way, little information is processed by the client, and nearly everything is done by the server.

authentication domain

a SAS internal category that pairs logins with the servers for which they are valid.

For example, an Oracle server and the SAS copies of Oracle credentials might all be classified as belonging to an OracleAuth authentication domain.

client application

an application that runs on a client machine.

cube

See OLAP cube

data mart

a subset of the data in a data warehouse. A data mart is optimized for a specific set of users who need a particular set of queries and reports.

data warehouse (warehouse)

a collection of pre-categorized data that is extracted from one or more sources for the purpose of query, reporting, and analysis. Data warehouses are generally used

220

Glossary

for storing large amounts of data that originates in other corporate applications or that is extracted from external data sources.

database management system (DBMS)

a software application that enables you to create and manipulate data that is stored in the form of databases.

DBMS

See database management system

Extensible Markup Language (XML)

a markup language that structures information by tagging it for content, meaning, or use. Structured information contains both content (for example, words or numbers) and an indication of what role the content plays. For example, content in a section heading has a different meaning from content in a database table.

library reference

See libref

libref (library reference)

a SAS name that is associated with the location of a SAS library. For example, in the name MYLIB.MYFILE, MYLIB is the libref, and MYFILE is a file in the SAS library.

metadata LIBNAME engine

the SAS engine that processes and augments data that is identified by metadata.

The metadata engine retrieves information about a target SAS library from metadata objects in a specified metadata repository.

metadata promotion (promotion)

in the SAS Open Metadata Architecture, a feature that enables you to copy the contents of a metadata repository to another repository, and to specify changes in the metadata that will be stored in the target repository. For example, you can use this feature to move metadata from a development environment to a testing environment. In such a scenario, you would probably have to change some ports,

Glossary

221 hosts, and/or schema names as part of the process of moving metadata from one environment to another.

OLAP

See online analytical processing

OLAP cube (cube)

a logical set of data that is organized and structured in a hierarchical, multidimensional arrangement to enable quick analysis of data. A cube includes measures, and it can have numerous dimensions and levels of data.

OLAP schema

a container for OLAP cubes. A cube is assigned to an OLAP schema when it is created, and an OLAP schema is assigned to a SAS OLAP Server when the server is defined in the metadata. A SAS OLAP Server can access only the cubes that are in its assigned OLAP schema.

online analytical processing (OLAP)

a software technology that enables users to dynamically analyze data that is stored in multidimensional database tables (cubes).

promotion

See metadata promotion

resource template

an XML file that specifies the information that is needed for creating a metadata definition for a SAS resource.

SAS Metadata Repository

a container for metadata that is managed by the SAS Metadata Server.

SAS OLAP Cube Studio

a Java interface for defining and building OLAP cubes in SAS System 9 or later. Its main feature is the Cube Designer wizard, which guides you through the process of registering and creating cubes.

222

Glossary

SAS Open Metadata Architecture

a general-purpose metadata management facility that provides metadata services to

SAS applications. The SAS Open Metadata Architecture enables applications to exchange metadata, which makes it easier for these applications to work together.

SAS Scalable Performance Data Engine (SPD Engine)

a SAS engine that organizes data into a streamlined file format, enabling rapid delivery of data to applications.

SAS Scalable Performance Data Server (SPD Server)

a server that restructures data in order to enable multiple threads, running in parallel, to read and write massive amounts of data efficiently.

schema

a map or model of the overall data structure of a database. A schema consists of schema records that are organized in a hierarchical tree structure. Schema records contain schema items.

SPD Engine

See SAS Scalable Performance Data Engine

SPD Server

See SAS Scalable Performance Data Server

warehouse

See data warehouse

XML

See Extensible Markup Language

A access defining ODBC data sources

120

ODBC connectivity to databases

registering database libraries

registering database server

registering SAS Federation

Server

125

registering SAS Federation

Server libraries

Access

ODBC connectivity to databases

ADD command

SPDO procedure

aggregations

APIs (application programming interfaces)

ARM (application response monitoring)

201

asynchronous communication

Attunity

authorization facility

Index

autoexec files pre-assigning libraries using information in

Base SAS engine metadata engine invocation of

Base SAS library registering

Base SAS tables buffering data

BLKSIZE= LIBNAME option

block insert buffer size

194

block read buffer size

block size

buffer size for block insert

for block read

buffering table data

BYSORT= LIBNAME option

223

224

Index

C cache page caches

CACHENUM= LIBNAME option

change data capture (CDC)

CLUSTER CREATE command

SPDO procedure

cluster tables, dynamic

CLUSTER UNDO command

SPDO procedure

clustered data tables

columns defining for flat files

compression

179

configuration libnames.parm file

SPD Engine hardware

configuration files editing for pre-assigned libraries

for user-defined formats

connectivity

ODBC

ODBC, to Access databases

ODBC, to Microsoft Access

ODBC, to Oracle databases

SAS LASR Analytic Server

SAS LASR libraries

160

SASHDAT

to data sets

to Excel files

to external files

to flat files

to Hadoop Server

148

to Impala Server

144

to information maps

to library of data sets

to ODBC databases using

Microsoft Windows NT

Authenication

to OLE DB databases

to Oracle databases

to SAP HANA servers

to SAP servers

to SAS Federation Server

124

to SPD Server

16 ,

129

to Teradata databases

to XML data

to XML files

cube metadata storage location requirements cubes

See

OLAP cubes

D data access local and remote

OLAP cubes

read-only for reporting libraries

verifying in SAS applications

data component partitions

data compression

179

data extraction

data registration

data representation for output files

data sets

connectivity to

connectivity to library of

shared access to

4 ,

data source optimization, multi

data sources

change data capture

connecting to

data sets

Excel files

external files

local and remote data access

message queues

ODBC

relational database sources

SAP HANA servers

SAP servers

134

shared access to data sets

SPD Server and SPD Engine

XML data

data storage

OLAP cubes

data storage optimization

178

Index

225 application response monitoring (ARM)

201

buffering data for Base SAS tables

buffering data for other tables

compressing data

grid computing

indexing data

LIBNAME options affecting

SAS table performance

LIBNAME options affecting

SAS/ACCESS database performance

LIBNAME options affecting

SPD Engine table performance

multi-threaded sorting

sorting data

184

sorting database tables

threaded reads

190

validating SPD Engine hardware configuration

Data Surveyor for SAP

data synchronicity

data tables, clustered

data warehouses cubes and

data-access engines

database libraries registering for Hadoop Hive

226

Index

registering for Microsoft

Access

registering for Oracle

database servers registering for access

registering for Oracle

registering SPD Server

database tables sorting

databases connectivity to ODBC using

Microsoft Windows NT

Authenication

connectivity to OLE DB

connectivity to Oracle

, 114

connectivity to Teradata

LIBNAME options affecting

SAS/ACCESS performance

ODBC connectivity to Access

ODBC connectivity to

Microsoft Access

ODBC connectivity to Oracle

relational

third-party

DataFlux Data Management

Server

DATAPATH= LIBNAME option

DB2 buffering table data

DBINDEX= LIBNAME option

DBMS passing DELETE statement

(SQL) to

passing functions to

passing generated SQL to

registering libraries

registering server

70 ,

102

threaded access

DBNULLKEYS= LIBNAME option

DBSLICEPARM= LIBNAME option

DELETE statement (SQL) passing to DBMS

delimited external file wizard

detail data displaying for large cubes

215

making available to cubes for drill-through

making available to information map for drillthrough

making available to OLAP server for drill-through

DIRECT_EXE= LIBNAME option

DIRECT_SQL= LIBNAME option

drill-through making detail data available to cubes for

making detail data available to information map for

Index

227 making detail data available to

OLAP server for

dynamic cluster tables

flat files

extracting data

extracting SAP metadata

E ending observation number

ENDOBS= LIBNAME option

engines

Base SAS engine

data-access engines

metadata engine

49 ,

pre-assigning libraries

environment variables for SAS/ACCESS on UNIX

Excel files as data source

connectivity to

EXCLUDE statement

METALIB procedure

exporting cubes

205

External File Source Designer connecting to flat files

external files

connectivity to

creating metadata objects for

defining columns

delimited

fixed-width

F file system path

fixed-width external file wizard

flagging pre-assigned libraries

flat files connecting to

connectivity to

defining columns for

format catalog

formats user-defined

functions passing to DBMS

G generated SQL passing to DBMS

grid computing data considerations

Hadoop registering server

Hadoop data

228

Index

Hadoop Hive registering database library

Hadoop Server connectivity to

148

hardware configuration validating for SPD Engine

I/O block size

Impala Server connectivity to

144

Impala servers registering

145

implicit sort

importing cubes

205

index component files

indexes

182 ,

INDEXPATH= LIBNAME option

information map tables

information maps connectivity to

making detail data available for drill-through

194

INSERTBUFF= LIBNAME option

LIBNAME options affecting SAS table performance

affecting SAS/ACCESS database performance

affecting SPD Engine table performance

libnames.parm file configuring

libraries

See also

pre-assigning libraries

assigning

connectivity to

creating table metadata for

data-access engines and

default assignment for

metadata engine and

platform client assignments

read-only access for reporting libraries

registering

registering Base SAS library

registering database libraries for Microsoft Access

registering DBMS libraries

registering for SAP HANA servers

143

registering for SAP servers

137

registering for SPD Server

132

registering Hadoop Hive database library

registering Oracle database library

registering SAS Federation

Server libraries

stored processes and assigning

libraries using SAS

Environment Manager

SAS/SHARE Remote Engine library

libraries using SAS

Management Console

SAS/SHARE Remote Engine library

librefs assigning libraries

for XML data

limit access to libraries

LIST command

SPDO procedure

local data access

localize table batch tool

lockdown state

locked-down servers

logs reviewing to verify preassigned libraries

Index

229 component files

extracting SAP metadata

storage location requirements for cube metadata

metadata engine

pre-assigning libraries to

metadata objects creating for external files

METALIB procedure 24

assessing potential table metadata changes

changing the update rule

creating table metadata for new library

EXCLUDE statement

NOEXEC statement

pre-assigned libraries and

REPORT statement

SELECT statement

specifying which tables are affected

UPDATE_RULE statement

updating table metadata to match physical tables

METAPATH= LIBNAME option

multi data source optimization

multi-threaded sorting

MULTI_DATASRC_OPT=

LIBNAME option

M message queues

metadata

See also

table metadata

230

Index

NOEXEC statement

METALIB procedure

null keys when generating WHERE clauses

number of ending observation

number of starting observation

O observations ending observation number

starting observation number

ODBC buffering table data

components and features

connectivity to databases using Microsoft Windows

NT Authenication

connectivity to Microsoft

Access

ODBC sources

defining for Microsoft Access

OLAP cubes

aggregations

building

creating or assigning OLAP schemas

data storage and access

detail data for drill-through

detail data for information map drill-through

detail data for OLAP server drill-through

displaying detail data for large cubes

215

exporting and importing

205

OLAP schemas and

storage location for metadata and related objects

OLAP schemas

creating or assigning

OLAP server detail data for drill-through

OLE DB buffering table data

connectivity to databases

data storage optimization

optimizing data storage

See

Oracle buffering table data

connectivity to databases

114

connectivity to databases, using ODBC

registering database library

registering database server

output files data representation for

OUTREP= LIBNAME option

overflow paths

to use metadata engine file

Index

231

using information in autoexec verifying by reviewing logs

P page caches

partitions paths for storing

size of

PARTSIZE= LIBNAME option

data storage optimization

performance

See also

SAS tables

SAS/ACCESS databases

SPD Engine tables

physical tables updating table metadata to match

platform clients assigning libraries

pooled workspace server assigning libraries

pre-assigning libraries

44 ,

editing configuration files

externally

flagging libraries as preassigned

large number of libraries

METALIB procedure and

RDBMS

SAS/ACCESS connections to

troubleshooting SAS/ACCESS connections to

175

read-only access for reporting libraries

READBUFF= LIBNAME option

registering access SAS Federation

Server library

Base SAS library

data

DBMS library

DBMS server

70 ,

102

Hadoop Hive database library

Hadoop server

Impala servers

145

libraries

Microsoft Access database

Microsoft Access database library

Oracle database library

Oracle database server

232

Index

SAP HANA library

SAP HANA servers

SAP server library

SAP servers

SAS Federation Server

SPD Server

SPD Server library

tables

relational database sources

ODBC

SAS/ACCESS

remote data access

Remote Engine library, SAS/

79 ,

REPORT statement

METALIB procedure

reporting libraries read-only access for

SAP

Data Surveyor

extracting metadata

on z/OS

SAP HANA registering libraries for

143

SAP HANA servers as data source

connectivity to

registering

141

SAP servers as data source

connectivity to

registering

registering libraries for

137

SAS applications verifying data access in

SAS Data Quality Server

SAS Data Surveyor

SAS Federation Server connectivity to

124

registering

125

SAS Federation Server libraries registering for access

SAS LASR Analytic library connectivity

160

SAS LASR Analytic Server connectivity

SAS Open Metadata

Architecture authorization facility

SAS tables

LIBNAME options affecting performance

SAS XML Mapper

sas-localize-table

SAS/ACCESS

connections to RDBMS

environment variables on

UNIX

LIBNAME options affecting database performance

troubleshooting RDBMS connections

175

SAS/SHARE

Remote Engine library

79 ,

shared access to data sets

SASHDAT

connectivity

Scalable Performance Data

Engine

SPD Engine

Scalable Performance Data

Server

See

SPD Server

SELECT statement

METALIB procedure

servers registering for Hadoop

shared access to data sets

shared access to sets

SMP (symmetric multiprocessing)

sorting data

184

automatic implicit sort

database tables

multi-threaded sorting

source designer wizards

SPD Engine

LIBNAME options affecting table performance

validating hardware configuration

SPD Server

connectivity to

16 ,

129

dynamic clustering

registering

registering library for

132

symmetric multiprocessing

SPDO procedure

ADD command

CLUSTER CREATE command

T table metadata

Index

233

CLUSTER UNDO command

LIST command

spool files

SPOOL= LIBNAME option

SQL passing DELETE statement to

DBMS

passing generated SQL to

DBMS

SQL Server buffering table data

SQL_FUNCTIONS= LIBNAME option

sql_server_ntauth

starting observation number

STARTOBS= LIBNAME option

data storage optimization

storage optimization

See

stored processes assigning libraries and

subdirectories temporary

Sybase buffering table data

symmetric multiprocessing

(SMP)

synchronicity

234

Index

adding

assessing potential changes

changing the update rule

creating for new library

excluding tables

selecting tables

specifying which tables are affected

updating

updating to match data in physical tables

tables buffering table data

, 189

clustered data tables

dynamic cluster tables

information map tables

LIBNAME options affecting

SAS table performance

LIBNAME options affecting

SPD Engine table performance

registering and verifying

sorting database tables

TEMP= LIBNAME option

temporary subdirectories

Teradata connectivity to databases

third-party databases

threaded DBMS access

threaded reads

190

troubleshooting

SAS/ACCESS connections to

RDBMS

175

UNIX environment variables for

SAS/ACCESS

update rule

UPDATE_RULE statement

METALIB procedure

user-defined formats configuration file

connectivity to library of data sets

user-written external file wizard

WHERE clauses null keys when generating

XML data

connectivity to

9 ,

libref for

XML LIBNAME engine

XML Writer transformation

XMLMaps

Z z/OS

SAP on