Usage Notes for SAS LASR Analytic Server and Related Software

The SAS Data in HDFS engine stores data as SASHDAT files. SASHDAT is the name of a specialized file type for distributing data, such as Oracle data, with the SAS High-Performance Deployment of Hadoop. It is also the name of the SAS library engine that is used to access those files. The View Data feature in SAS Data Integration Studio cannot be used to view tables in a SASHDAT library. You cannot create a SAS Data Integration Studio job that uses the Table Loader transformation to load a target table in a SASHDAT library. Although you can add data to HDFS, you cannot load a table from HDFS. You can, however, specify a table in a SASHDAT library as the target of the following transformations: Extract, Sort, Append, Splitter, Frequency, Compare Tables, SQL Create Table, SQL Join, SQL Set Operators.

The SAS® LASR™ Analytic Server is a direct-access server that is engineered for maximum analytic performance through multithreading. The SAS LASR Analytic Server can run within the Hadoop environment. For deployments that need to work with large data volumes, distributed SAS LASR Analytic Server can be co-located with SAS High-Performance Deployment of Hadoop. In these deployments, the server can read and write data to storage rapidly due to multi-threading and massively parallel processing. The SASIOLA library engine moves data between a SAS session and a SAS LASR Analytic Server. There are some special considerations for SASIOLA tables in SAS Data Integration Studio.

The View Data feature cannot be used to view tables in a SASIOLA library.

You cannot create a SAS Data Integration Studio job that uses the Table Loader transformation to load a target table in a SASIOLA library. You can, however, specify a table in a SASIOLA library as the target of the following transformations: Extract, Sort, Append, Splitter, Frequency, Compare Tables, SQL Create Table, SQL Join, SQL Set Operators.