Using SAS Engines to Process External Data

Explanation :
This example uses the FILENAME statement to assign the 'chol' fileref to a temporary file. The HTTP procedure is then used to download a CSV file from a specified URL and save it to the 'chol' fileref. The IMPORT procedure reads the CSV data and creates the SAS dataset 'work.mycholesterol'. Finally, PROC PRINT displays the content of the dataset to verify the import.

Explanation :
This example imports data from a Microsoft Excel (.xlsx) file using the IMPORT procedure and the XLSX engine. For this example to be self-contained, you must first create an Excel file named 'cholesterol.xlsx' (e.g., by saving the 'cholesterol.csv' file from the previous example in .xlsx format). The 'VALIDVARNAME=V7' option is used to convert Excel column names into valid SAS variable names (replacing spaces with underscores). The XLSX engine requires the SAS/ACCESS to PC Files interface to be configured. The REPLACE option allows replacing an existing SAS dataset.

Explanation :
This example shows how to create a table directly in an external database management system (DBMS), here Teradata. The LIBNAME statement 'mytddata' is defined to establish a connection to the Teradata server, including authentication information. A DATA step is then used to create a table named 'grades' in this DBMS using 'datalines' to provide the data. The DATASETS procedure is used to display information about the 'mytddata' library, confirming that the table has been created in the DBMS.

Explanation :
This example illustrates the creation of a SAS view (mygrades in the viewlib library) that embeds a LIBNAME statement for a connection to a Teradata database. The libref 'viewlib' is assigned to the location where the SAS view will be stored, using the V9 engine. The 'USING' clause of the 'CREATE VIEW' statement allows embedding the DBMS connection details, making the view self-sufficient for accessing the 'mytddata.grades' table. Finally, PROC PRINT executes this view and displays its content.

Explanation :
This example uses the SQL Pass-Through facility within PROC SQL to send SQL queries directly to an external database (Teradata). The 'CONNECT TO' statement establishes a named connection 'myconn' to the Teradata server with the specified credentials. Then, a 'SELECT * FROM CONNECTION TO myconn (...)' clause allows executing a native SQL query (filtering 'grades' with 'final gt 90') directly on the DBMS. The 'DISCONNECT FROM' statement is used to terminate the database connection after the query execution.

Explanation :
This example imports data from an XML file using the XMLV2 engine. To make this example self-contained, create a file named 'nhl.xml' with the following XML content, and replace 'file-path' with the actual path:
```xml
<?xml version="1.0" encoding="iso-8859-1" ?>
<NHL>
<CONFERENCE> Eastern
<DIVISION> Southeast
<TEAM name="Thrashers" abbrev="ATL" />
<TEAM name="Hurricanes" abbrev="CAR" />
<TEAM name="Panthers" abbrev="FLA" />
<TEAM name="Lightning" abbrev="TB" />
<TEAM name="Capitals" abbrev="WSH" />
</DIVISION>
</CONFERENCE>

<CONFERENCE> Western
<DIVISION> Pacific
<TEAM name="Stars" abbrev="DAL" />
<TEAM name="Kings" abbrev="LA" />
<TEAM name="Ducks" abbrev="ANA" />
<TEAM name="Coyotes" abbrev="PHX" />
<TEAM name="Sharks" abbrev="SJ" />
</DIVISION>
</CONFERENCE>
</NHL>
```
The FILENAME statement assigns the 'nhl' fileref to the XML file. A second FILENAME statement assigns the 'map' fileref to a file that will store the generated XMLMap. The LIBNAME statement, with the XMLV2 engine and options 'AUTOMAP=REPLACE' and 'XMLMAP=map', reads the XML file and generates an XMLMap. PROC PRINT then displays the 'TEAM_name' and 'TEAM_abbrev' variables from the 'nhl.team' dataset created in memory.

Explanation :
This example imports JSON data using the JSON engine. To make this example self-contained, create a file named 'example.json' with valid JSON content (e.g., a simple JSON object with a few fields and values) and replace 'file-path' with the actual path. The LIBNAME statement 'mydata' is assigned to the JSON engine and points to the 'example.json' file. The DATASETS procedure is then used to list the SAS datasets created in memory from this JSON file, thereby verifying the import.